Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Special case normalization of help--symbol-completion-table #321

Conversation

clemera
Copy link
Collaborator

@clemera clemera commented Jan 5, 2021

See #320

@clemera clemera force-pushed the special-case-help--symbol-completion-table branch from b20fe7d to 24ef641 Compare January 5, 2021 11:33
@minad
Copy link
Contributor

minad commented Jan 5, 2021

@clemera Thanks for the quick fix!

@clemera
Copy link
Collaborator Author

clemera commented Jan 5, 2021

I had a bad feeling to generally switch the buffer, as you said it doesn't match with the general assumption so errors are likely to happen

@minad
Copy link
Contributor

minad commented Jan 5, 2021

I somehow had a bad feeling to generally switch the buffer, as you said it doesn't match with the general assumption so errors are likely to happen

Yes, I was worried too, also since you merged this very quickly. We are more safe now, I guess :)

@clemera clemera changed the title Special case help--symbol-completion-table Special case normalization of help--symbol-completion-table Jan 5, 2021
@clemera
Copy link
Collaborator Author

clemera commented Jan 5, 2021

Yes, I also think this is less likely to get us into trouble

@clemera clemera merged commit 6ba5f11 into radian-software:master Jan 5, 2021
@clemera
Copy link
Collaborator Author

clemera commented Jan 8, 2021

This won't work for recursive session where the last buffer can't be obtained by minibuffer-selected-window we would need the buffer from the previous minibuffer session. Doing the computation before entering the next session for the descrbe symbol table would work but then this would produce slowdowns for embark with describe-variable + selectrum.

@minad
Copy link
Contributor

minad commented Jan 8, 2021

@clemera please explain. Ist ist necessary to revert this?

@clemera
Copy link
Collaborator Author

clemera commented Jan 8, 2021

No revert but can be improved. describe-variable is still slow for recursive sessions. We would need to obtain the last minibuffer session for recursive sessions or compute the candidates before the next session is entered (with the downside that this would slowdown embark interaction for describe-variable as described above).

@minad
Copy link
Contributor

minad commented Jan 8, 2021

Shall we open a new issue to keep the improvement in mind?

@clemera
Copy link
Collaborator Author

clemera commented Jan 8, 2021

I wanted to experiement if/how I can get the last session and fix it with some next PR but if I fail to do that I will open one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants