Re: [Patch] Fixed error in setting up Edit.Color Scheme submenu

2008-08-21 Fir de Conversatie Jürgen Krämer
Hi, Tony Mechelynck wrote: On 20/08/08 10:56, Jürgen Krämer wrote: Hi, I have a lot of color schemes below ~/.vim/colors and ~ expands to C:\Dokumente und Einstellungen\jkr.HABEL, so the execution of let s:n = globpath(runtimepath, colors/*.vim) in $VIMRUNTIME/menu.vim returns a

Re: Bug with v_K and potentially K command

2008-08-21 Fir de Conversatie Matt Wozniski
On Thu, Aug 21, 2008 at 1:56 AM, Ben Schmidt wrote: place your cursor on 'pwnme', and press K. xclock appears. Yeah, this is the kind of exploit where you have to tell the user to do something stupid and them blame Vim that the user is stupid. Yes. Still...that seems to be the current

RE: Reading a file from a script?

2008-08-21 Fir de Conversatie Robert Webb
Ag. D. Hatzimanikas: I could also use readfile(), which would probably suffice, but is this more or less efficient than loading a file into a vim buffer. I will still need to read the whole file either way since I don't know how far through the file I will need to look. Now if

Re: Reading a file from a script?

2008-08-21 Fir de Conversatie Ingo Karkat
On 21-Aug-08 16:15, Robert Webb wrote: Ag. D. Hatzimanikas: I could also use readfile(), which would probably suffice, but is this more or less efficient than loading a file into a vim buffer. I will still need to read the whole file either way since I don't know how far through the file

Re: Bug with v_K and potentially K command

2008-08-21 Fir de Conversatie Matt Wozniski
On Thu, Aug 21, 2008 at 1:05 PM, Tony Mechelynck wrote: On 21/08/08 08:25, Matt Wozniski wrote: [...] In that vein, perhaps using the shell should be an option... but doubtless the best default behavior is to use system(3) for places like :! where shell expansion is good,and execlp() for

Re: Bug with v_K and potentially K command

2008-08-21 Fir de Conversatie Tony Mechelynck
On 21/08/08 08:25, Matt Wozniski wrote: [...] In that vein, perhaps using the shell should be an option... but doubtless the best default behavior is to use system(3) for places like :! where shell expansion is good,and execlp() for those places where we decidedly don't want any shell

Re: Bug or feature? E670

2008-08-21 Fir de Conversatie Tony Mechelynck
On 21/08/08 14:42, Marvin Renich wrote: [...] I would have expected :helptags to use the current value of 'fencs', which, if encoding=utf-8, defaults to ucs-bom,utf-8,default,latin1, which should favor utf-8 over latin1. Tony, what was fencs when you ran helptags? just what you said above.

Re: Opening a file as the OS would

2008-08-21 Fir de Conversatie Tony Mechelynck
On 20/08/08 16:16, Robert Webb wrote: Hi, What's the best way (on Windows) to open a file from vim in whatever Windows normally uses to open that file? For example, :!% will open the current file, but it leaves a DOS window handing around while the file is open, which requires a hit-enter

Menu Toolbar.Find does not exist?

2008-08-21 Fir de Conversatie Tony Mechelynck
In $VIMRUNTIME/menu.vim (dated 2008 Jun 30) a tooltip is defined for a ToolBar.Find menu which does not exist: lines 981-988 if !has(gui_athena) an 1.95 ToolBar.-sep3- Nop an 1.100 ToolBar.Replace :promptreplCR vunmenu ToolBar.Replace vnoremenu

:args reorders arguments

2008-08-21 Fir de Conversatie björn
Hi, This may not be the right place for this post, but it seems like I've come across a bug so I am posting here. If I type :args file1.m file1.h file2.m then I expect the arglist to have the file appear in the order I specified, but instead the arglist is in this order: file1.m file2.m

Re: Bug or feature? E670

2008-08-21 Fir de Conversatie Bram Moolenaar
Marvin Renich wrote: * Bram Moolenaar [EMAIL PROTECTED] [080821 00:55]: Tony Mechelynck wrote: E670: Mix of help file encodings within a language: /usr/local/share/vim/vimfiles/doc/hicolors.txt The error is given by the :helptags command. Bug or feature? 1.

Re: Menu Toolbar.Find does not exist?

2008-08-21 Fir de Conversatie Bram Moolenaar
Tony Mechelynck wrote: In $VIMRUNTIME/menu.vim (dated 2008 Jun 30) a tooltip is defined for a ToolBar.Find menu which does not exist: lines 981-988 if !has(gui_athena) an 1.95 ToolBar.-sep3-Nop an 1.100 ToolBar.Replace :promptreplCR

Bug in clipboard handling on X11

2008-08-21 Fir de Conversatie Matt Wozniski
Not sure what's going on here, but I've found a crash that's easy to reproduce. First, open two X11 enabled vim (not gvim) processes. In the first, do: :let @+ = repeat('a', 1024*1024) in order to store 1MB of data to the clipboard. The exact amount is irrelevant, but the larger the size, the

Re: synIDattr() and 'guisp' attribute [with patch]

2008-08-21 Fir de Conversatie Matt Wozniski
On Fri, Aug 15, 2008 at 2:02 AM, Matt Wozniski wrote: synIDattr() currently does not support the ability to read a 'guisp' attribute from a highlight group, even though the underlying C function it exposes does support it. I've attached a patch to update the interface and docs to allow and

Re: Menu Toolbar.Find does not exist?

2008-08-21 Fir de Conversatie Tony Mechelynck
On 22/08/08 03:13, Bram Moolenaar wrote: [...] Looks like this is a leftover from when ther was a Find toolbar item. I'll remove tmenu ToolBar.Find. Rather than that, I've added a Find toolbar item (duplicating the Edit=Find... menu the way Toolbar=Replace duplicates Edit=Find and

Right-align vs right-justify documentation?

2008-08-21 Fir de Conversatie Peter Prohaska
Hi, the docs tell me that... :help right-justify There is no command in Vim to right justify text. [...] :help :right Right-align lines in [...] Doesn't that mean, that at least 'gq' followd by ':right' would right- justify whatever text object? Not sure if i'm missing some subtle point here.