WIP improved emacsclient launch function#13
Draft
ajjackson wants to merge 1 commit into
Draft
Conversation
The main requirement for this is to avoid messy situations if I instintively "em" while inside an emacs vterm. Nested emacs instances are not nice, instead this should jump to existing (outer) emacs. Currently there are some rough corners: - if TUI and GUI are both open, sometimes vterm->em from TUI opens in GUI instead - other programs using EDITOR don't expect/like this to be a fish function.
Owner
Author
|
We can see in the test failure here the regression in emacs package setup. These functions didn't previously need explicit loading into namespace... Somehow autoload broke? #12 fixes this but not very nicely. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The main requirement for this is to avoid messy situations if I instintively "em" while inside an emacs vterm. Nested emacs instances are not nice, instead this should jump to existing (outer) emacs.
Currently there are some rough corners:
if TUI and GUI are both open, sometimes vterm->em from TUI opens in GUI instead
other programs using EDITOR don't expect/like this to be a fish function.