On 11:26 Wed 27 May , Gene Kwiecinski wrote:
> Or alt-F4. :D
Strangely, this doesn't quit vim at all. ;-)
Kind regards from my fourth workspace,
Kai
--
All mail clients suck. This one just sucks less.
--~--~-~--~~~---~--~~
You received this messag
>>Does anyone know the proper / quick and dirty way to "just quit, darn
it"?
>I use this:
>:qa
Or alt-F4. :D
--~--~-~--~~~---~--~~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~
On 2009-05-26, smu johnson wrote:
> How do you get rid of the "# files to edit" message that always scatters my
> terminal whenever I do this?
Using the ! after :q or :qa will fix that, too.
Regards,
Gary
--~--~-~--~~~---~--~~
You received this message from th
I suppose it's time to donate to Uganda in order to vote for this trivial
feature :)
2009/5/26 Tim Chase
>
> > Hello Tim, you are a good man! You solved my problem. Since you knew
> the
> > answer to that, perhaps you could help me with this even easier question:
> >
> > How do you get rid o
On 2009-05-26, smu johnson wrote:
> Hi,
>
> If anyone has known the bliss of vimdiff, I'm sure you realize that probably
> in most cases, you will vimdiff file1 and file2. The problem with that I
> have found, is that when I want to quit after seeing what I need to see, it
> treats the args as s
> Hello Tim, you are a good man! You solved my problem. Since you knew the
> answer to that, perhaps you could help me with this even easier question:
>
> How do you get rid of the "# files to edit" message that always scatters my
> terminal whenever I do this?
I'm not sure this is an easier q
Hello Tim, you are a good man! You solved my problem. Since you knew the
answer to that, perhaps you could help me with this even easier question:
How do you get rid of the "# files to edit" message that always scatters my
terminal whenever I do this?
Many thanks in advance!
2009/5/26 Tim Chas
> If anyone has known the bliss of vimdiff, I'm sure you realize that probably
> in most cases, you will vimdiff file1 and file2. The problem with that I
> have found, is that when I want to quit after seeing what I need to see, it
> treats the args as still a list of files "to edit", so I have t
Hi,
If anyone has known the bliss of vimdiff, I'm sure you realize that probably
in most cases, you will vimdiff file1 and file2. The problem with that I
have found, is that when I want to quit after seeing what I need to see, it
treats the args as still a list of files "to edit", so I have to qu
