This is how to reproduce:
vim -Nu NORC
:help|wincmd w|1quit
I expect to quit the HELP window, but two windows are both quit and vim exits.
If I leave out "wincmd w", it works as expected.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the t
This is how to reproduce:
vim -Nu NORC
:help|wincmd w|1quit
I expect to quit the HELP window, but two windows are both quit and vim exits.
If I leave out "wincmd w", it works as expected.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the t
It's distracting to remember the direction of a previous motion or search
command(e.g. f F * # g* g# etc.), which makes it difficult to choose a proper
repeat command(; , n N), especially not immediately after the motion or search
command.
Thus I think the state of direction of a previous motio
solution to simply remapping "F":
NXnoremap F :call Ff()
function! Ff()
let n = getchar()
if n == 27 " though not necessary
return
endif
let c = nr2char(n)
execute 'silent! normal! F'.c.'hf'.c
endfunction
--
Regards, Bohr Shaw
--
--
You rec
With this mapping `nnoremap F f*,` and the cursor on `b` in the text `foo*bar`,
after pressing `F`, the cursor wouldn't be moved to `*`.
--
--
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
Thanks! Can't wait the updated runtime.
On Thu, Mar 20, 2014 at 11:55 PM, Charles Campbell <
charles.e.campb...@nasa.gov> wrote:
> Bohr Shaw wrote:
>
>> ehttps://raw.github.com/tpope/vim-sensible/master/plugin/sensible.vim
>>
> Hello!
>
> Please try netrw
"HTTPS" in a URL is substituted with "HTTP" by the plugin "netrw".
But some files are not accessible via "HTTP".
I got a empty file with this command:
"e https://raw.github.com/tpope/vim-sensible/master/plugin/sensible.vim";
In addition, it would be more convenient if "follow URL redirecting" is
Sorry for another misreport. I was in a careless mood early on.
On Sun, Jan 19, 2014 at 8:53 PM, Christian Brabandt wrote:
> On Sa, 18 Jan 2014, Bohr Shaw wrote:
>
> > As a global mark may either reside in a loaded file or an unloaded file,
> I
> > think the motion to it s
ou are subscribed to a topic in the
> Google Groups "vim_dev" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/vim_dev/tRZHtlEkwxM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> vim_dev+unsubscr...@
--
--
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 because you are subscribed to the Google Groups
"vim_dev" group.
To unsubs
As a global mark may either reside in a loaded file or an unloaded file, I
think the motion to it should not always skip triggering the "BufRead" event.
--
--
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 inf
ting on the intended syntax".
If so, I think I would just avoid indenting on the whole file(actually the
only file).
On Mon, Jan 13, 2014 at 3:19 AM, Gary Johnson wrote:
> On 2014-01-12, Bohr Shaw wrote:
> > Sometimes I define an "augroup" at a file beginning and END it
Sometimes I define an "augroup" at a file beginning and END it at the file end.
Thus, with the default 'indentexpr' settings, I would indent almost the whole
files one more level, which is not expected.
And because that arbitrary commands can come after an "augroup" definition and
there not nec
On Friday, December 20, 2013 11:02:11 PM UTC+8, James McCoy wrote:
> The strange part is that 'fileformat' is only used for the initial empty
> buffer and not every new buffer.
I find the initial unnamed buffer have no differences with other unnamed
buffers. Inconsistency exists here.
--
--
Y
On Saturday, December 21, 2013 1:39:43 AM UTC+8, Andy Wokula wrote:
> Am 20.12.2013 04:35, schrieb Bohr Shaw:
>
> > Misbehavior:
>
> > set statusline=%{','.1}=> 1
>
> >
>
> > Normal behavior:
>
> > set statusline=%{'.'
I have 'fileformats' set to 'unix,dos'. But I get 'dos' file format for the
first buffer created when Vim starts. It seems only the 'fileformat' option
is checked because I'm on Windows and 'fileformat' defaults to 'dos'.
--
Regard
Misbehavior:
set statusline=%{','.1}=> 1
Normal behavior:
set statusline=%{'.'.1} => .1
--
Regards, Bohr Shaw
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying
When the cursor is just after "py3d", to complete is not working. But the
completion to "py3" works.
" My command line completion settings
set wildmenu
set wildmode=longest:full,full
set wildignorecase
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your rep
On Wednesday, September 18, 2013 9:45:00 PM UTC+8, Ben Fritz wrote:
> On Wednesday, September 18, 2013 4:54:57 AM UTC-5, Bohr Shaw wrote:
> > On Wednesday, September 18, 2013 3:14:09 PM UTC+8, Bohr Shaw wrote:
> > > I have tested the problem with this command:
> > >
&
On Wednesday, September 18, 2013 3:14:09 PM UTC+8, Bohr Shaw wrote:
> I have tested the problem with this command:
>
>vim -Nu NONE --cmd 'filetype plugin indent on' --cmd 'syntax enable'
> --startuptime t +h
>
> `cat t` and I got:
>
>
I have tested the problem with this command:
vim -Nu NONE --cmd 'filetype plugin indent on' --cmd 'syntax enable'
--startuptime t +h
`cat t` and I got:
...
201.000 001.000 001.000: sourcing D:\ProgramsPortable\Vim\vim74\scripts.vim
206.000 000.000 000.000: sourcing
D:\ProgramsPortable\
The pattern
\v(^.+\n)\1
matches three lines when applying to the text:
dog dog
dog dog
dog dog
dog dog
dog
--
--
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://
However, the document says the register 1 always hold the text deleted by the
delete operator with these movement commands:|%|, |(|, |)|, |`|, |/|, |?|, |n|,
|N|, |{| and |}|.
I guess this is a document error.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type y
However, the document says the register "1 always hold the text deleted by the
delete operator with these movement commands:|%|, |(|, |)|, |`|, |/|, |?|, |n|,
|N|, |{| and |}|.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are
On Sunday, August 4, 2013 8:34:05 AM UTC+8, Andrei Olsen wrote:
> On Sunday, August 4, 2013 2:12:28 AM UTC+2, Bohr Shaw wrote:
> > This is a the left and bottom part of the whole screen picture.
>
> This is probably related to this discussion:
> https://groups.google.c
This is a the left and bottom part of the whole screen picture.
--
--
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 because yo
On Friday, June 14, 2013 11:52:23 AM UTC+8, ZyX wrote:
> On Jun 14, 2013 7:41 AM, "Bohr Shaw" wrote:
>
> >
>
> > I compile vim against two system python versions without any problem. But I
> > get the "E370:Could not load library libpython2.7.a"
I compile vim against two system python versions without any problem. But I get
the "E370:Could not load library libpython2.7.a" when I compile vim against
self compiled python versions.
I just change my environment path to point to the correct python versions
before I compile vim. Although I c
On Friday, June 14, 2013 9:36:44 AM UTC+8, Zulox4 wrote:
> Hello,
>
> When Vim 7.3.1189 win32 console start it display this error (the next five
> lines) :
>
> C:\Vim_20130614_1189\vim\src>vim
> Error detected while processing C:\Users\vim7user_win7sp1\.vimrc:
> line1:
> E518: Unknown option
On Friday, June 14, 2013 1:14:59 AM UTC+8, ZyX wrote:
> On Thursday, June 13, 2013 7:22:20 PM UTC+4, Bohr Shaw wrote:
>
> > I have added the exact python library DLL to the shell's search
> > path($PATH). But I still get the error: "E370, Could not loa
I have added the exact python library DLL to the shell's search path($PATH).
But I still get the error: "E370, Could not load the library libpython*."
I have check the related document which says: In a console window type "path"
to see what directories are used. What does this mean?
--
--
Yo
I just ask this question at stackoverflow.com. I was so confused.
http://stackoverflow.com/questions/17041782/vim-startup-with-importerror-no-module-named-ultisnips
On Tuesday, June 11, 2013 3:41:00 PM UTC+8, Davido wrote:
> Bram Moolenaar wrote, on lun 10 jun 21:27 :
>
>
>
> >
>
> > Patch 7
32 matches
Mail list logo
