Monday, September 30, 2013

Re: Scrolling (diffing) through VCS revisions


On Sep 30, 2013 6:21 PM, "Ben Fritz" <fritzophrenic@gmail.com> wrote:
>
> On Monday, September 30, 2013 5:13:45 AM UTC-5, ZyX wrote:
> > On Sep 30, 2013 1:20 PM, "Paul" <googl...@rainslide.net> wrote:
> >
> > >> Note: gJ and gK should be typed in the buffer with repository version, not
> >
> > >> in the buffer with version from current working directory. J and K are for
> >
> > >> just next/previous revision. If you are diffing two revisions they should
> >
> > >> work for both (in fact it is aurum://file mapping, not the
> >
> > >> AuVimDiff-specific one).
> >
> > >
> >
> > >
> >
> > > When I do gJ / gK, I get "E21: Cannot make changes, 'modifiable' is off". I tried making this an issue on bitbucket but I got a 403.
> >
> > Do you have any mappings to gJ/gK? These commands do not do any changes, they open a new buffer.
> >
> > : what does ":verbose nmap gJ" show?
> >
>
> Hi, ZyX and Jan!
>
> I've encountered similar problems in the past, because I have a BufRead/BufWinEnter autocmd which sets 'nomodifiable' if 'readonly' is set. At one point I was doing a global "set nomodifiable" but now I do "setlocal" instead. Otherwise, any new buffers created also have 'nomodifiable' set.
>
> Jan, if you've got a similar autocmd, you should make the same fix.
>
> ZyX, if the new buffer your plugin is creating should always be modifiable, it would be smart to set 'modifiable' explicitly just in case it inherits a bad value.

As I said, gJ does not modify current buffer: it instead opens a new one. 'nomodifiable' is set by aurum for all aurum://file buffers. Thus I assume he has similar problem with conflicting mappings as I have (I have remapped J for vim files though and not gJ, thus I am not much willing to resolve conflict).

If what you mentioned here is the case he must be doing gJ in the wrong buffer (this must be done in the buffer with the committed version).

> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
 
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment