Hi tyru!
On Mi, 11 Aug 2010, tyru wrote:
--- code ---
function! MyStatusline()
let pos = getpos('.')
try
normal! 0
return blah blah
finally
call setpos('.', pos)
endtry
endfunction
let statusline = '%{MyStatusline()}'
On 11/08/10 02:57, John Beckett wrote:
[...]
While it would best to eliminate the redundant redraws
altogether (and I'll perhaps have a chance to look at that after
7.3 is released), I was wondering what happens once echoing of
the command fills the screen. There seems to be a flag which
tells
On 11/08/10 15:40, KF Leong wrote:
On Aug 11, 6:39 pm, Lech Lorenslech.lor...@gmail.com wrote:
Here's what I get:http://llorens.visualserver.org/c-vim-problem/c.png
BTW I am sure that what you claim is happening actually used to
happen. I think it was me who suggested to Bram that the cDefine
I mean if there is such mechanism in the vim script itself.
OK, maybe the title of this mail is not very clear for you to
understand, i just give an example.
let foo = {}
let foo.var = 100
we can access the value 100 by :
echo foo.var
echo foo['var']
i just want to know if there is a mechanism
On 12-Aug-2010 10:19, winterTTr wrote:
I mean if there is such mechanism in the vim script itself.
OK, maybe the title of this mail is not very clear for you to
understand, i just give an example.
let foo = {}
let foo.var = 100
we can access the value 100 by :
echo foo.var
echo
On 12/08/10 00:32, Steve Hall wrote:
As a rule, are the Mercurial runtimes more current than FTP? Or are we
still in the situation where either patches or FTP files could be? (In
times past, I found that FTP always superseded patches.)
--
Steve Hall [ digitect dancingpaper com ]
--
You
Hi,
Ingo Karkat wrote:
On 12-Aug-2010 10:19, winterTTr wrote:
Or is there an alternate method to accessing dictionary when the key
is not found
, instead of showing error directly?
You can use
echo get(foo, 'var', MyFunction('var'))
MyFunction() can then return whatever you want
This is a regression introduced by my own patch previously
(7ce8b24450dc: Improvements for
:find completion. (Nazri Ramliy)).
Attached patch fixes the regression and add tests to test73 to catch the bug.
The test runs fine on unix, but fails on msvc vim. I'll investigate
it later. Sorry I'm in
On 12 August 2010 17:01, Jürgen Krämer jottka...@googlemail.com wrote:
Hi,
Ingo Karkat wrote:
On 12-Aug-2010 10:19, winterTTr wrote:
Or is there an alternate method to accessing dictionary when the key
is not found
, instead of showing error directly?
You can use
echo get(foo,
Adrien Pied Piérard wrote:
Dear everyone,
As a polyglot vim user, I happen to write and read files written in
several languages, including multibyte ones.
It works very well, as long as the files I read are mine. When I
happen to read someone else's file, I often have problems, for the
text
On Aug 12, 4:23 am, winterTTr winterttr@gmail.com wrote:
OK, thanks so much for your answers. I do not notice the get() method.
There is indeed an alternate way to do so. That's great.
However, I must use this code everywhere if i want the feature as i mentioned.
Even the other person
On 12 August 2010 20:34, Ben Fritz fritzophre...@gmail.com wrote:
On Aug 12, 4:23 am, winterTTr winterttr@gmail.com wrote:
OK, thanks so much for your answers. I do not notice the get() method.
There is indeed an alternate way to do so. That's great.
However, I must use this code
Can someone who was involved in the addition of changelog_entry_prefix
please look at this. I can’t remember what the deal was. Thanks!
(The version in the Mercurial repository has the correct date, by the way.)
-- Forwarded message --
From: Alexandre Fournier
On 12.08.2010 06:33:07
James Vega james...@jamessan.com wrote:
On Tue, Aug 10, 2010 at 11:15:41PM +0200, Bram Moolenaar wrote:
A configure check would help to decide whether everything works
without
RTLD_GLOBAL global. If it does, then the current solution is best. If
it doesn't it might
As a workaround, use winsaveview()/winrestview()
oh, thanks for the info :)
I will use it instead.
--
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
Nazri Ramliy wrote:
This is a regression introduced by my own patch previously
(7ce8b24450dc: Improvements for
:find completion. (Nazri Ramliy)).
Attached patch fixes the regression and add tests to test73 to catch the bug.
The test runs fine on unix, but fails on msvc vim. I'll
Dominique Pelle wrote:
I've compiled Vim-7.3e (2539:9397d2d76340) with the clang compiler on Linux.
All tests pass. However, I see something wrong when doing:
$ vim -c 'saveas! /tmp/foo'
Vim prints:
/tmp/foo [New File] 0 lines, 585937717901131776 characters written
Obviously
Jakson Aquino wrote:
On Tue, Aug 10, 2010 at 6:15 PM, Bram Moolenaar b...@moolenaar.net wrote:
Unfortunately, when I run Aap, applying the diff fails. Â It looks like
the diff was made for another pt_PT.aff file. Â The one that was
downloaded looks like this:
SET UTF-8
KF Leong wrote:
On 2010-08-12 05:36, Bram Moolenaar wrote:
The diff has wrapped lines. Please attach it instead of putting it in
the main text.
Sorry! Attached c.vim diff to restore the behaviour of the syntax region
functionality.
I fail to see the problem this solves. The
Bram Moolenaar wrote:
I'll change the E999 to a valid number, we should have a tag in the help
file that explains the message.
Should each translator update the E999 in src/po/*.po files to the new
value or can it be done automatically?
Here are the po file which already contain E999:
$ cd
20 matches
Mail list logo
