On 10/04/09 01:41, Mun Johl wrote:
Hi Tony,
Please see my comments below.
On Tue, Apr 07, 2009 at 09:19 PM PDT, Tony Mechelynck wrote:
[...]
TM http://vim.wikia.com/wiki/Setting_the_font_in_the_GUI
Great write-up, thanks! It answered my main point of confusion which
was why on my
On Tue 07 Apr 2009 at 12:42:08 +0200, Bram Moolenaar wrote:
This has two advantages:
1. It's backwards compatible.
2. Avoids accidentally typing the wrong number of hex digits.
3. Allows typing a hex digit next as a separate character.
Eh, _three_ advantages.
Nobody expects the spanish
Ralf Schandl wrote:
after several years I had the chance to compile Vim on zOS Unix.
That's nice to hear. I like supporting small groups of users.
I already fixed some problems, but some are left:
1) test 11 fails, because gzip is not available on zOS Unix (at least
not by
Hi,
I am the maintainer for vim in MacPorts. The configure script triggered
a linking error for _Xsetlocale for us on Mac OS X. Here is a patch
which adds a conditional to make sure this test is not run if the
x_includes variable is actually not set.
Regards,
Rainer
On 11/04/09 00:14, Rainer Müller wrote:
Hi,
I am the maintainer for vim in MacPorts. The configure script triggered
a linking error for _Xsetlocale for us on Mac OS X. Here is a patch
which adds a conditional to make sure this test is not run if the
x_includes variable is actually not set.
On Fri, Apr 10, 2009 at 6:43 PM, Tony Mechelynck wrote:
Couldn't you run test just once? Maybe something more or less like
if test -n $x_includes -a $x_includes != NONE
Just my sense of aesthetics, I'm not on a Mac.
Usually, yes - but lore tells of shells where test isn't POSIX
On 11/04/09 04:16, Matt Wozniski wrote:
On Fri, Apr 10, 2009 at 6:43 PM, Tony Mechelynck wrote:
Couldn't you run test just once? Maybe something more or less like
if test -n $x_includes -a $x_includes != NONE
Just my sense of aesthetics, I'm not on a Mac.
Usually, yes - but lore
On Fri, Apr 10, 2009 at 10:53 PM, Tony Mechelynck wrote:
On 11/04/09 04:16, Matt Wozniski wrote:
On Fri, Apr 10, 2009 at 6:43 PM, Tony Mechelynck wrote:
Couldn't you run test just once? Maybe something more or less like
if test -n $x_includes -a $x_includes != NONE
Just my sense
On 11/04/09 05:02, Matt Wozniski wrote:
On Fri, Apr 10, 2009 at 10:53 PM, Tony Mechelynck wrote:
On 11/04/09 04:16, Matt Wozniski wrote:
On Fri, Apr 10, 2009 at 6:43 PM, Tony Mechelynck wrote:
Couldn't you run test just once? Maybe something more or less like
if test -n
