I often use the :digraph command to find foreign language characters.
But looking for a certain character sometines is like finding a needle
in the haystack. Would it be possible to color-code the three colums
of :dig's output?
Axel
--
You received this message from the vim_dev maillist.
Do not
Hi Axel!
On Do, 26 Aug 2010, Axel wrote:
I often use the :digraph command to find foreign language characters.
But looking for a certain character sometines is like finding a needle
in the haystack. Would it be possible to color-code the three colums
of :dig's output?
I have written a
Axel wrote:
I often use the :digraph command to find foreign language characters.
But looking for a certain character sometines is like finding
a needle in the haystack. Would it be possible to color-code
the three colums of :dig's output?
Finding a character is hard. I suppose some clever
I have written a plugin, unicode.vim
(http://www.vim.org/scripts/script.php?script_id=2822) that ought to
make that easier by providing a completion function for digraphs and
Unicode Glyphs.
Hi Christian.
This sounds interesting but I still have not found how to work with your
script. It
On Aug 25, 11:11 pm, JiaYanwei jia...@126.com wrote:
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
On Aug 26, 9:40 am, Ben Fritz fritzophre...@gmail.com wrote:
From my understanding, 'fileencoding' is the encoding Vim is supposed
to use to read/write the file. So, it does make sense that we should
use this instead of just 'encoding' for the charset of the generated
html. Does anyone know
Thanks for the answers so far!
However, I'd like to see a functionality that can be used out of the
box.
This is due to the fact that I - quite often - just copy over gvim.exe
to a newly installed box and work there for a while.
I think it should be possible to have some small patch doing this.
Steps to reproduce:
- Open any three 3 buffers.
- :python import vim
- :python for b in vim.buffers: print b.name+' '+b[0]
Expected output:
[Filename of buffer A] - [first line of buffer A]
[Filename of buffer B] - [first line of buffer B]
[Filename of buffer C] - [first line of buffer C]
My
Dear Vim-Dev,
I wrote my first omni completion function today and I quickly noticed
that the basic completion function of 20 lines has about 16 static
lines that are usually reused in every basic completion function.
In the most basic function, where provided matchings are shown in the
list as
On Thu, 26 Aug 2010, perrytrinier wrote:
Is there some reason that I can only access the lines of buffers
which are visible in a window?
It may be that you can only access the lines in a buffer when the
buffer is actually loaded, and by default it is not unless it's
displayed in a window.
bump...
any feedback from a core committer as to whether this patch is
acceptable to be merged into default?
--
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
Thanks for your reply, Christian. I tried :set hidden, but it behaved
the same way.
If it's only possible to access loaded buffers, there is no mention of
that in the docs at
http://vimdoc.sourceforge.net/htmldoc/if_pyth.html#python-vim
.
On Aug 26, 4:29 pm, Christian J. Robinson
On Thu, 26 Aug 2010, perrytrinier wrote:
Thanks for your reply, Christian. I tried :set hidden, but it
behaved the same way.
Did you make sure to explicitly load each buffer before running your
example code, but after you had turned 'hidden' on?
Using the Perl interface, I see the same
Oh, sorry, I forgeted that 'fileencoding' may be empty. This should be
handled.
I encountered the opposite that 'fileencoding' is often different from
'encoding' while editing existing files.
Ben Fritz wrote:
On Aug 26, 9:40 am, Ben Fritz fritzophre...@gmail.com wrote:
From my
14 matches
Mail list logo
