Visit files and run shell commands from chat#250
Merged
Conversation
local-set-key mutates the shared mode map when the buffer's local map is the mode map, and (kbd "C-c RET") is C-c C-m. Give the test buffer its own keymap copy so C-c C-m keeps its select-model binding for later tests.
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.
Files mentioned in chat are now one keystroke away.
RET on a file target opens it:
src/app.el:12:3, at that line and columnBy default the file opens in the other window;
C-u RETflips that for one visit.! runs a Dired-inspired shell command on the file at point. Simple commands like
wc -lorfileget the file appended automatically and safely quoted; anything fancier uses an explicit*placeholder, e.g.wc -c * | cat.Everything fails closed: prose, tool headers, and ambiguous text simply don't resolve, so RET never opens something you didn't mean.
Full details in the README section on file targets.