Am 06.10.2010 19:41, schrieb Britton Kerin:
* It seems to cause problems to use inputdialog() from a plugin at
startup. The following in ~/.vim/after/plugin/test_inputdialog.vim:
call inputdialog("foo?")
shows the problems. For some reason, the prompt appears as
an error messa
Pablo Contreras wrote:
> Hi All,
> You may think I'm crazy, why would you want to call HIGHLIGHT so many
> times??? Because I wrote a color scheme script that updates the highlight
> continuously. Each 'time' it calls HIGHLIGHT 40 times to update each major
> syntax element's name, and if as I did
Pablo Contreras wrote:
> Hi All,
> You may think I'm crazy, why would you want to call HIGHLIGHT so many times=
> ??? Because I wrote a color scheme script that updates the highlight contin=
> uously. Each 'time' it calls HIGHLIGHT 40 times to update each major syntax=
> element's name, and if a
-Original Message-
From: vim_dev@googlegroups.com [mailto:vim_...@googlegroups.com] On Behalf
Of Dominique Pellé
Sent: 10 October 2010 09:18
To: vim_dev@googlegroups.com
Subject: Re: Sorry for no subject; HIGHLIGHT stops working around 144000th
time
Pablo Contreras wrote:
>> Hi All,
>> Yo
H Xu wrote:
> Does this bug get any chance to be fixed? Thanks.
This is not a bug. Works as intended.
> On 10/1/10, Tony Mechelynck wrote:
> > On 01/10/10 03:39, H Xu wrote:
> >> Hello,
> >>
> >> The value of "fileencoding" does not change after saving a new file,
> >> until reopen the file.
Patch 7.3.021
Problem:Conflict for defining Boolean in Mac header files.
Solution: Define NO_X11_INCLUDES. (Rainer Muller)
Files: src/os_macosx.m, src/vim.h
*** ../vim-7.3.020/src/os_macosx.m 2010-08-15 21:57:29.0 +0200
--- src/os_macosx.m 2010-10-10 17:01:55.
Hello Bram,
The way to reproduce it is simple: open a new file:
vim test.txt
test.txt must not exist.
Then input some letters and use ":w" to save the file. now check the
value of "fileencoding": it is empty, while it should be some value.
I don't think this is what intended to be. Thank you.
Ho
On Mon, Oct 11, 2010 at 01:01:48AM +0800, H Xu wrote:
> Hello Bram,
> The way to reproduce it is simple: open a new file:
> vim test.txt
>
> test.txt must not exist.
> Then input some letters and use ":w" to save the file. now check the
> value of "fileencoding": it is empty, while it should be so
-Original Message-
From: vim_dev@googlegroups.com [mailto:vim_...@googlegroups.com] On Behalf
Of Bram Moolenaar
Sent: 10 October 2010 09:35
To: Pablo Contreras
Cc: vim_dev@googlegroups.com
Subject: Re: (about highlight)
Pablo Contreras wrote:
>> Hi All,
>> You may think I'm crazy, why wo
-Original Message-
From: vim_dev@googlegroups.com [mailto:vim_...@googlegroups.com] On Behalf
Of Bram Moolenaar
Sent: 10 October 2010 09:35
To: Pablo Contreras
Cc: vim_dev@googlegroups.com
Subject: Re: (about highlight)
Pablo Contreras wrote:
>> Hi All,
>> You may think I'm crazy, why wo
When using vim-gnome (7.3), only the first font in the 'guifont' list
is ever checked. This is because pango_font_description_from_string()
does its best to return a usable font, even if it doesn't actually
find anything that even vaguely matches.
I have put together a quick patch that adds some c
11 matches
Mail list logo
