-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Provide ways to open pop ups in a new buffer / split #8748
Comments
I was looking a bit into the code; it looks like the popup class is available at: https://github.com/helix-editor/helix/blob/master/helix-term/src/ui/popup.rs and in particular, the handling of incoming keys is done by: helix/helix-term/src/ui/popup.rs Lines 196 to 221 in a6ed104
Then I guess that it would be enough, to implement this, to:
Would this make sense / be feasible as described here? If so, I think the main block for me to implement it is to understand how to perform the actions (i), (ii), (iii). Any pointer to locations in the code that illustrate how to do this? Is this as simple as (a) grabbing the |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Actually, it may be easier to create a new buffer and paste the content in it; probably something inspired from:
helix/helix-term/src/commands/typed.rs Lines 432 to 444 in 7e389b6
helix/helix-term/src/commands.rs Lines 4072 to 4149 in 7e389b6
need to understand / explore how to set the name of the buffer to doc_NAME instead of scratch. |
Starting to work on a drag PR, help and comments welcome :) . |
Actually, I do not think that grabbing the content of a popup to display it in a new buffer is doable at present; I am discussing a bit some ideas of how this could be done in the PR drag #9311 . Any input there welcome :) . |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Pop ups are very convenient for small items (a few lines), however I found them a bit inconvenient for large items (for example, a long manual page for a function in numpy or scipy).
Some examples in my workflow when pop ups are not so convenient:
When using pop ups to get access to long documentation that I have to read through in details, I end up spending quite a lot of time reading and moving from inside the pop up itself to read it, which is not very convenient as the possibilities for moving around are much more limited than on a normal buffer: I would much better enjoy to move around in the pop up with the full power of helix commands.
When displaying the documentation for a slightly advanced function through a pop up, I may want to be able to look both, at the same time, at my code and the pop up documentation, as I may need to think a bit, compare my use with the different documentation examples, etc. I may also want to copy paste some lines from the pop up examples to my code and to tweak it in my code. This is not achievable as far as I know with the pop ups as these are now.
So after a bit of use, it feels like the pop ups are not too adapted to display more than a few lines of information: when more information is displayed, such as a long manpage with a lot of explanations and examples, I would really prefer to have the possibility to get the pop up content into a (temporary) buffer for moving around / copying examples to my code, etc.
Do you think / any idea how a good UX could be for that? For example, when inside a pop up, should we add a new pop up mode, with a few "popup mode commands" that would allow to, for example:
Could something like this make sense? I do not think something like this is available at the moment, or am I missing something? :)
The text was updated successfully, but these errors were encountered: