-
-
Notifications
You must be signed in to change notification settings - Fork 1k
Commit
- Loading branch information
There are no files selected for viewing
4 comments
on commit a510b3a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't get this change. Personally I've never had the need to use macros in fugitive windows, they're read only anyways. Is it at least possible to make this optional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Macros can still have uses in read-only buffers. Plus there's q:
, etc. Not gonna make an option - rig up an autocommand to define it yourself if you need it. (Possibly Fugitive could use some better autocommand events to make this easier.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case someone else interested, I ended up with
nnoremap <buffer> q <c-w>q
in ~/.vim/after/ftplugin/fugitive.vim
and ~/.vim/after/ftplugin/fugitiveblame.vim
.
I was initially trying to find a function to map to, but it seems there is no "public interface" for that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nmap <buffer> q gq
is a quasi-public interface, but what you have is probably fine.
This shows me the garbled message