On Fri, Sep 23, 2011 at 9:32 AM, Charles Campbell
<[email protected]> wrote:
> Donald Allen wrote:
>>
>> In netrw, the mf command does not work with 'syntax off' in my .vimrc
>> file. In gvim, s-leftmouse does work. mf does work without the 'syntax
>> off' in the .vimrc file. If I eliminate the 'syntax off' in my .vimrc
>> file, bring up vim and do a :syntax off, then mf works!
>>
>> /Don
>>
>
> Oh, its working -- its just that since you have syntax off, vim's :match and
> :2match etc don't work (you'll get an E28), as you have specified that you
> don't want such visual highlighting.
My apologies, you are right, at least in the sense that the file does
get marked. I just attempted to mc a file to /tmp and the copy did
work, though the highlighting of the marked file did not. In previous
encounters with this, I have seen the copy *not* work, but I was not
aware that there was an issue with this at that point, so I wasn't in
careful debugging mode and didn't re-check it, as I should have,
before sending my message (I have no idea why the copy failed in that
previous attempt).
I also found the reason why mf produced highlighting when I eliminated
the 'syntax off' from my .vimrc and did a ':syntax off' manually: if
you start vim, then do a ':E' to start netrw, then do ':syntax off',
the xmas-tree coloring goes away in the netrw window, but highlighting
does work in response to 'mf'. But if you start vim and turn off
syntax before starting netrw, the highlighting does not work.
>
> Try using mf to select a file, and press "D" to delete the file
> (obviously, don't do this with a Valuable File) -- and you'll see a
> confirmation request message with the selected file.
>
> There's a lot of dependency in netrw with filetype testing, which you get
> with syntax highlighting. I'm sure that you will find that some things do
> break.
As I've observed before in discussions of other issues with vim, if
netrw depends on 'syntax on' for correct behavior, then if syntax is
off, it shouldn't just fail silently (and I consider not providing any
visible feedback that a file is marked a failure. Suppose you mark
multiple files? How do you later go back and verify which ones are
marked?). If syntax off means highlighting doesn't work, then netrw
should provide some other form of visible feedback, perhaps appending
a character ('M'?) similar to the * that indicates a file with execute
permission. I would also note that the confusing behavior of
highlighting depending on the order in which you start netrw/turn off
syntax (as I described above) also should be fixed.
/Don
>
> Regards,
> Chip Campbell
>
>
>
> --
> You received this message from the "vim_dev" 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 from the "vim_dev" 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
