I've played few hours with netrw today.
I've opened files, directories, created/removed/moved some. After some time I've stared to receive strange errors when doing many different things. Like running a shell command. I haven't seen those errors before, and nerdtree -> netrw is the only thing I've changed today, so it must be related. I've increased verbosity, and did `:!ls` to gather a log.
http://pastebin.com/wCKqDfsW
I suspect, that my `set hidden` is somehow responsible. I also tried reproducing this on fresh vim, but couldn't do it - so either I've set something or a plugin collision occurs.
Any ideas what could be wrong, or other tracking techniques then `vbs` to narrow this down?
--
--
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.
Tuesday, July 2, 2013
Vim netrw - Explore when modified without split
I've opened a file and modified it - now I want to do `:Explore` without splitting.
It splits - because I have an unsaved buffer. By default this is nice, becasuse Vim generally doesn't allow to switch files, until you do something with the modified buffer (save or discard changes).
But I have set `hidden` option, so I can jump from buffer to buffer, switch files and everything - and save or not when I feel I want to. It seems Netrw doesn't follow this policy. How could I help it?
One way I know of is to map netrw `explore` to `save & explore`, but I'm not sure if autowriting is a good way of doing things... I am actually using other autowriting settings now, but I was just rethinking to maybe get rid of them.
I've posted this question on stackoverflow first, over here:
http://stackoverflow.com/questions/17430423/vim-netrw-explore-when-modified-without-split/17431618?noredirect=1#17431618
--
--
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.
It splits - because I have an unsaved buffer. By default this is nice, becasuse Vim generally doesn't allow to switch files, until you do something with the modified buffer (save or discard changes).
But I have set `hidden` option, so I can jump from buffer to buffer, switch files and everything - and save or not when I feel I want to. It seems Netrw doesn't follow this policy. How could I help it?
One way I know of is to map netrw `explore` to `save & explore`, but I'm not sure if autowriting is a good way of doing things... I am actually using other autowriting settings now, but I was just rethinking to maybe get rid of them.
I've posted this question on stackoverflow first, over here:
http://stackoverflow.com/questions/17430423/vim-netrw-explore-when-modified-without-split/17431618?noredirect=1#17431618
--
--
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.
Default IME mode when entering Vim insert mode (Windows)
I'm using Vim on Windows[1] with Microsoft's Japanese IME "enabled" all the time and when I enter insert mode the default input mode (the IME's input mode, not Vim's) changes to Japanese. I took two pictures to illustrate what I see before I enter insert mode[2] (notice the capital 'A' beside the red thingy on the tray) and after I've entered insert mode[3] (notice that the 'A' changed into a Japanese character). After the input mode has changed to Hiragana then when I type full-width Japanese characters are 'printed'.
So, basically, when I open up Vim and I want to enter some text then first I have to switch back to the default IME input mode (half-width alphanumeric) which is all good (I can do this with a Windows shortcut), but sometimes I forget this and ... well, sometimes it's frustrating. What's worse is that if I load a new file into a buffer and switch over to that and enter insert mode I have to switch the IME's input mode again, which is really-really frustrating when I try to work with multiple files.
My question is: can I instruct Vim so that it won't change the IME input mode when I enter insert mode? (It's not option for me to switch Windows's keyboard language/layout to another language when I work with Vim because I have to type Japanese text sometimes and switching between languages is more frustrating than this whole shebang :).
Thanks for the input in advance.
Regards,
Kohányi Róbert
[1] http://tuxproject.de/projects/vim/
[2] http://img163.imageshack.us/img163/8808/dht8.png
[3] http://img577.imageshack.us/img577/8066/nzpr.png
--
--
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.
So, basically, when I open up Vim and I want to enter some text then first I have to switch back to the default IME input mode (half-width alphanumeric) which is all good (I can do this with a Windows shortcut), but sometimes I forget this and ... well, sometimes it's frustrating. What's worse is that if I load a new file into a buffer and switch over to that and enter insert mode I have to switch the IME's input mode again, which is really-really frustrating when I try to work with multiple files.
My question is: can I instruct Vim so that it won't change the IME input mode when I enter insert mode? (It's not option for me to switch Windows's keyboard language/layout to another language when I work with Vim because I have to type Japanese text sometimes and switching between languages is more frustrating than this whole shebang :).
Thanks for the input in advance.
Regards,
Kohányi Róbert
[1] http://tuxproject.de/projects/vim/
[2] http://img163.imageshack.us/img163/8808/dht8.png
[3] http://img577.imageshack.us/img577/8066/nzpr.png
--
--
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.
Re: how to integrate distributed tags files generated by "make ctags"
On Tuesday, July 2, 2013 8:03:46 AM UTC-5, gesf wrote:
> I found the tags files generated by "make ctags" are usually distributed in the sub-directories of the package. Is there any convenient way to load these distributed tags files into vim?
>
Look at :help 'tags'. It tells you about wildcards that can be used to search an entire directory tree for any tags files.
--
--
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.
> I found the tags files generated by "make ctags" are usually distributed in the sub-directories of the package. Is there any convenient way to load these distributed tags files into vim?
>
Look at :help 'tags'. It tells you about wildcards that can be used to search an entire directory tree for any tags files.
--
--
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.
how to integrate distributed tags files generated by "make ctags"
I found the tags files generated by "make ctags" are usually distributed in the sub-directories of the package. Is there any convenient way to load these distributed tags files into vim?
Or I shall put it in a more general way: how to parse a list of files to :set in vim?
--
--
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.
Or I shall put it in a more general way: how to parse a list of files to :set in vim?
--
--
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.
Monday, July 1, 2013
Re: netrw and the 'list' option
Aaron Bohannon wrote:
> Why does netrw clobber it? I have been experiencing mysterious behavior with my 'list' option for years, and only recently was I finally able to track it down to netrw.
>
> There is no reason to clobber it. BufExplorer seems to handle the 'list' option in a totally clean way, saving and restoring it with BufWinEnter and BufWinLeave autocommand, respectively. Actually, based on my own experimentation, I'm not even sure if saving and restoring it is necessary if the plugin were to just do `:setlocal nolist` instead of `:set nolist`. However, that behavior may be a recently added feature since the documentation doesn't seem to account for that scenario.
>
> I can't be the first one to have noticed this, right?
>
> ...Aaron
>
Have you tried the latest netrw? Its up to v150b
(http://www.drchip.org/astronaut/vim/index.html#NETRW).
Regards,
C Campbell
--
--
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.
> Why does netrw clobber it? I have been experiencing mysterious behavior with my 'list' option for years, and only recently was I finally able to track it down to netrw.
>
> There is no reason to clobber it. BufExplorer seems to handle the 'list' option in a totally clean way, saving and restoring it with BufWinEnter and BufWinLeave autocommand, respectively. Actually, based on my own experimentation, I'm not even sure if saving and restoring it is necessary if the plugin were to just do `:setlocal nolist` instead of `:set nolist`. However, that behavior may be a recently added feature since the documentation doesn't seem to account for that scenario.
>
> I can't be the first one to have noticed this, right?
>
> ...Aaron
>
Have you tried the latest netrw? Its up to v150b
(http://www.drchip.org/astronaut/vim/index.html#NETRW).
Regards,
C Campbell
--
--
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.
netrw and the 'list' option
Why does netrw clobber it? I have been experiencing mysterious behavior with my 'list' option for years, and only recently was I finally able to track it down to netrw.
There is no reason to clobber it. BufExplorer seems to handle the 'list' option in a totally clean way, saving and restoring it with BufWinEnter and BufWinLeave autocommand, respectively. Actually, based on my own experimentation, I'm not even sure if saving and restoring it is necessary if the plugin were to just do `:setlocal nolist` instead of `:set nolist`. However, that behavior may be a recently added feature since the documentation doesn't seem to account for that scenario.
I can't be the first one to have noticed this, right?
...Aaron
--
--
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.
There is no reason to clobber it. BufExplorer seems to handle the 'list' option in a totally clean way, saving and restoring it with BufWinEnter and BufWinLeave autocommand, respectively. Actually, based on my own experimentation, I'm not even sure if saving and restoring it is necessary if the plugin were to just do `:setlocal nolist` instead of `:set nolist`. However, that behavior may be a recently added feature since the documentation doesn't seem to account for that scenario.
I can't be the first one to have noticed this, right?
...Aaron
--
--
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.
Subscribe to:
Posts (Atom)