If you launch vim the following way:
vim -u NONE --cmd 'set nocompatible conceallevel=2' --cmd $'syn keyword
Ctest cchar=\t conceal abc' -c $'normal! aabc\n'
then you will see only two empty lines on the terminal. If you then
press j and k, then you will first see ``abc'' on the first line
On Mon, Aug 23, 2010 at 03:44:12PM +0300, Kirill A. Shutemov wrote:
link.sh tries to avoid overlinking in a hackish way.
At least GNU ld supports --as-needed which provides the same functionality
at linker level. Let's use it.
Any comments?
Signed-off-by: Kirill A. Shutemov
Forwarded from vim_use...potentially the changeset mentioned below
missed a change or two.
-- Forwarded message --
From: Stahlman Family brettstahl...@comcast.net
Date: Aug 24, 7:35 pm
Subject: Possible bug: cchar not applied to region start token when
cole=2
To: vim_use
Ben
From: Ben Fritz [mailto:fritzophre...@gmail.com]
Forwarded from vim_use...potentially the changeset mentioned below
missed a change or two.
Chip Campbell noticed this, although in his case it turned out there was an
easier way to do what he was trying to do. Nothing got missed out from
the
Is anyone working on one yet? would love to take a peek at the code :p
--
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
Hi Tom,
I wrote a Vim plug-in [1] that uses LuaInspect [2] to perform semantic
highlighting of different variable types in Lua source code. The plug-in
can use the Lua interface for Vim but also works without the interface,
by running Lua as an external process using Vim's system() function.
I think this will be more reasonable than before.
If the encoding of edited text file differ form the system/vim encoding, it's
inconvenient to set default HTML charset to be 'encoding'. Thus, after
':TOhtml', we should modify the generated HTML file to make the file encoding
the same as HTML
