Re: gvim --help

2012-10-24 Fir de Conversatie Christian Brabandt
On Tue, October 23, 2012 21:48, Marc Weber wrote: What magic is gvim doing to hide its documentation? I understand this: [marc@nixos:~]$ gvim --help 1 /tmp/file; ls -l /tmp/file 3326 (bytes in /tmp/file) I'd expect stdout to be printed to my console [marc@nixos:~]$ gvim --help 2 /tmp/file;

Re: E163 confusing in some circumstances

2012-10-24 Fir de Conversatie Ingo Karkat
On 24-Oct-2012 02:25:58 +0200, Ben Schmidt wrote: I think E163 could do with some rewording, or perhaps another error could be created. It seems E163 is used when there are less than two arguments, and E165 or E164 when there are two or more. However, the case when there are zero arguments is

[DOC PATCH] It is not stated that VIM::Eval returns only the value in scalar context

2012-10-24 Fir de Conversatie ZyX
It was stated only in :h perl-overview alongside with other examples. # HG changeset patch # User ZyX kp-...@ya.ru # Date 1351072849 -14400 # Node ID 6f110cb9089b4c875af465d136229a3154425212 # Parent 57e8b75298d6b6e9ef899af66c79a22cb6334988 Added information about returning value of VIM::Eval in

Re: Suggested improvement to starting.txt

2012-10-24 Fir de Conversatie Marvin Renich
* Tony Mechelynck antoine.mechely...@gmail.com [121023 23:32]: ---help *-h* *--help* --h Give usage (help) message and exit. {not in Vi} +-h Give usage (help) message and exit. {not in Vi} *-h* See

Re: How to check for $ProgramFiles(x86) ?

2012-10-24 Fir de Conversatie Ben Fritz
On Wednesday, October 24, 2012 3:25:41 PM UTC-5, Timothy Madden wrote: I am trying to see if the current system is 32-bit or 64-bit Windows. On 64-bit Windows the environment variable $ProgramFiles(x86) is known to exits, but Vim will just check for $ProgramFiles and the appendthe '(x86)'

Re: E163 confusing in some circumstances

2012-10-24 Fir de Conversatie Ben Schmidt
On 24/10/12 6:14 PM, Ingo Karkat wrote: On 24-Oct-2012 02:25:58 +0200, Ben Schmidt wrote: I think E163 could do with some rewording, or perhaps another error could be created. It seems E163 is used when there are less than two arguments, and E165 or E164 when there are two or more. However,

Re: [DOC PATCH] It is not stated that VIM::Eval returns only the value in scalar context

2012-10-24 Fir de Conversatie Bram Moolenaar
ZyX wrote: It was stated only in :h perl-overview alongside with other examples. I'll include it, thanks. -- I learned the customs and mannerisms of engineers by observing them, much the way Jane Goodall learned about the great apes, but without the hassle of grooming.

Re: E163 confusing in some circumstances

2012-10-24 Fir de Conversatie Bram Moolenaar
Ben Schmidt wrote: I think E163 could do with some rewording, or perhaps another error could be created. It seems E163 is used when there are less than two arguments, and E165 or E164 when there are two or more. However, the case when there are zero arguments is confusing. E.g. vim -u

Re: gvim --help

2012-10-24 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: On Tue, October 23, 2012 21:48, Marc Weber wrote: What magic is gvim doing to hide its documentation? I understand this: [marc@nixos:~]$ gvim --help 1 /tmp/file; ls -l /tmp/file 3326 (bytes in /tmp/file) I'd expect stdout to be printed to my console

Re: :echo is not working under certain conditions

2012-10-24 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: On Fri, September 28, 2012 16:04, Marco Hinz wrote: Hello! A member of #vim has experienced a weird behaviour while Vim scripting. Under certain conditions :echo would only print one line at max. Thus neither 2x echo nor 1x echo containing a \n would work.

Re: gvim --help

2012-10-24 Fir de Conversatie Marc Weber
Sorry, if you don't have a terminal you don't use gvim --help usually. Anybody who did proof me wrong, please. Thus it should be fine to print --help output before starting the gui and everything should be fine. My idea was to check for the --servername flag to find out whether a vim executable