No, it's just the regular cmd.exe.
Greetings
Axel
--
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
Can you reproduce on following?
C:\gvim -u NONE -N
--
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
Yes!
--
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
I don't quite understand the problem. Up is supposed to go one
directory up. Is the problem that you get the ^I?
Yes.
http://go-gyazo.appspot.com/cd6100c7941e149b.png
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
On 28/10/11 07:07, Jürgen Krämer wrote:
Hi,
Ben Fritz :
On Oct 27, 2:45 pm, Axelaxel.ben...@cip-kommunal.de wrote:
The following command :!start !! is evaluated as :!start start start start
start start ..., which doesn't seem to be right to me (Windows Server 2003
32bit, GVim 7.3 353). Can
Hi Tony!
On Fr, 28 Okt 2011, Tony Mechelynck wrote:
See :help :! and :help :!!
As explained under :help :! a ! (not backslash-escaped) anywhere in
the line is replaced by the previous command: in this case, start
explorer.
As explained under :help :!! if you type !! _immediately after
Hello Tony,
I typed the !! not right after the colon (where the repetition would make
sense - if we compare this with bash's behaviour) but in the middle of a
command line - which starts with !start in this case. Here only two
successive !s were entered (no colon before the first).
I'd
Hi,
Axel wrote:
I typed the !! not right after the colon (where the repetition would
make sense - if we compare this with bash's behaviour) but in the
middle of a command line - which starts with !start in this case.
Here only two successive !s were entered (no colon before the
first).
@Jürgen, Tony
thanks for the answers. Seems I read over the second line of Jürgen's quote
in the docs (though having been pointed to it by Tony).
Obviously the exposed behavior goes with the specs (and is also consistent
with bash's behavior...).
Sorry for the noise.
Axel
--
You received
I use loadview and mkview with autocommands. It happens quite often
that upon returning to a buffer, a fold becomes unexpectedly closed.
In that case, whatever fold I attempt to open in this buffer next, it
will be closed after I leave the buffer and on returning to it again.
Attached are a test
10 matches
Mail list logo
