-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Feature Request: Insert function definition (at point) into the buffer #2560
Comments
I'm not sure to understand the feature, can you provide more info on the feature and a use case to be sure there is no missunderstanding ? |
E.g. Without the feature I get a list of faces (defined by I would use the feature even just for exploring for the convenience of not leaving the current buffer (and not creating a new one). |
If you add |
@tuhdo Isn't that too much of a visual noise and a performance penalty to have it all the time? But I would prob use it as a toggle when heavy exploring. |
@xged nope. It is because if a symbol is shown, it is already loaded into Emacs, and is only triggered when you place point on a symbol. I don't think it's a visual noise since it's only shown at the bottom and only when you place point on a symbol. This is Emacs, not Vim :) |
@tuhdo The point can be moved very fast :-), but it probably waits a second or a half for the definition to show up as most of the similar tools do, so that solves my silly 'concerns'. Still a very different problem then pasting. |
For your problem, I think it's easier to create a window that is clone of the current window (by simply splitting with |
@tuhdo I did it fast enough with macros. Nonetheless, I think the feature is important (because function definitions in general are super important). |
Take a look at lispy. Specifically these features, as well as |
That's nice :-) |
This issue appears to have been resolved. |
I don't agree that the initial feature request was satisfied. But I don't see much traction here. So I am not sure what to do. 😸 😿 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid! |
No description provided.
The text was updated successfully, but these errors were encountered: