Thursday, December 1, 2011

Re: suppress error?

On Dec 1, 12:01 am, "Christian Brabandt" <cbli...@256bit.org> wrote:
> On Thu, December 1, 2011 8:57 am, Bee wrote:
> > This function and its friend PrevDQ() work.
>
> > If I am diffing goes to next change, or if doing helpgrep will go to
> > the next.
>
> > When at the end of the helpgrep, it presents:
> > Error detected while processing function NextDQ:
> > line    4:
> > E553: No more items
> > Press ENTER or type command to continue
>
> > Can I suppress that message completely?
>
> >   function! NextDQ()
> >     if &diff
> >       normal! ]c
> >     else
> >       cn
> >       if v:version >= 700
> >         setlocal cursorline
> >       endif
> >     endif
> >   endfun
> >   nmap <F8> :call NextDQ()<cr>
>
> :h sil
>
> regards,
> Christian

Thank you Christian.
Not quite what I was looking for.
But this is:

function! CurLin()
if v:version >= 700 | setlocal cursorline
else | normal! zz
endif
endfun

function! PrevDQ() " Prev Diff or Quickfix
if &diff
normal! [c
else
try | cN
catch | clast
endtry | call CurLin()
endif
endfun
nmap <silent> <F7> :call PrevDQ()<cr>

function! NextDQ() " Next Diff or Quickfix
if &diff
normal! ]c
else
try | cn
catch | cfirst
endtry | call CurLin()
endif
endfun
nmap <silent> <F8> :call NextDQ()<cr>

-Bill

--
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

Re: Copy entire existing directory to another one

On Thursday, December 01, 2011 14:38:13 niva wrote:

> Hi,

> There is the func rename( to rename a file.

> Is there a native func to copy entire directory recursively to
> another directory destination.

uber-cool utility recently mentioned on this list:

https://github.com/trapd00r/vidir

gives you the power of vim in a file manager

sc

--
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

Re: Copy entire existing directory to another one

Hi niva!

On Do, 01 Dez 2011, niva wrote:

> Hi,
>
> There is the func rename( to rename a file.
>
> Is there a native func to copy entire directory recursively to another
> directory destination.

No. Remember, vim is an editor, not a file manager. You can easily use
:!move on windows or :!mv on unix

regards,
Christian
--

--
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

Copy entire existing directory to another one

Hi,

There is the func rename( to rename a file.

Is there a native func to copy entire directory recursively to another
directory destination.

Thanks

--
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

Re: Delay on opening new file

Thanks Tim

Problem solved by modifying viminfo file

Alireza

On Thu, Dec 1, 2011 at 10:44, Tim Chase <vim@tim.thechases.com> wrote:
> On 12/01/11 10:15, Alireza Haghdoost wrote:
>>
>> More updates about problem: vim command without mentioning any file in
>> command line takes that much time to open. However, by pressing Ctrl+c
>> it opens immediately...
>
>
> My first guess is that there's something massive stashed in your viminfo
> file.  You can try renaming your viminfo so that Vim doesn't find it.  If
> that speeds things up, then you can try hand-editing the viminfo so that the
> big stuff is removed.
>
> Alternatively, you might be loading some script that is causing trouble.
>  Including the output of
>
>  :scriptnames
>
> might help track down a rogue plugin.
>
> Other possibilities include Vim attempting to connect to X which you can try
> by launching Vim with the -X command parameter.
>
> Lastly, if you're pulling down some file (content, script, syntax file, etc)
> over a slow (low-bandwidth or high-latency) network link, it might stall out
> indefinitely.
>
> -tim
>
>
>

--
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

Re: Split Saving

On Dec 1, 6:33 am, Karthick Gururaj <karthick.guru...@gmail.com>
wrote:
> On Thu, Dec 1, 2011 at 5:59 PM, Tim Chase <v...@tim.thechases.com> wrote:
> > On 12/01/11 06:20, George Papanikolaou wrote:
>
> >> Is there any way I can save all the splits with one command?
>
> > You may be looking for either
>
> >  :help :mkview
> >  :h :loadview
>
> > or more likely
>
> >  :h :mksession
> >  :h :source
> >  :h 'sessionoptions'
>
> I understood the question differently.. as to save contents of all split
> windows.. if that is the case,
> :windo w
> will work.

Or, unless you have hidden buffers/windows in other tabs which you do
not also want to save,

:wa

is faster to type.

--
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

Re: Delay on opening new file

On 12/01/11 10:15, Alireza Haghdoost wrote:
> More updates about problem: vim command without mentioning any file in
> command line takes that much time to open. However, by pressing Ctrl+c
> it opens immediately...

My first guess is that there's something massive stashed in your
viminfo file. You can try renaming your viminfo so that Vim
doesn't find it. If that speeds things up, then you can try
hand-editing the viminfo so that the big stuff is removed.

Alternatively, you might be loading some script that is causing
trouble. Including the output of

:scriptnames

might help track down a rogue plugin.

Other possibilities include Vim attempting to connect to X which
you can try by launching Vim with the -X command parameter.

Lastly, if you're pulling down some file (content, script, syntax
file, etc) over a slow (low-bandwidth or high-latency) network
link, it might stall out indefinitely.

-tim

--
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