Fix a performance bug around SGR 1006 style mouse reporting

2013-02-01 Fir de Conversatie Hayaki Saito
Hello, I found a performance bug in SGR 1006 style mouse reporting patch which once I sent. The termcode of SGR 1006 style is "ESC [ <". So we don't need to parse it duplicately to distinguish it from termresponse code (typically it starts with "ESC [ >" or "ESC [ ?"). This patch will improve p

Re: Patch 7.3.798

2013-02-01 Fir de Conversatie toothpik
how terribly embarrassing -- according to my update.log, no!  apologies for the noise sc > > From: Ken Takata >To: vim_dev@googlegroups.com >Cc: toothpik >Sent: Friday, February 1, 2013 1:41 PM >Subject: Re: Patch 7.3.798 > >Hi toothpik, > >2013/02/02 Sat

Re: what happened to luxi mono?

2013-02-01 Fir de Conversatie Charles Campbell
Christian J. Robinson wrote: On Fri, 1 Feb 2013, Charles Campbell wrote: My vim's status: * :set guifont=Luxi\ Mono\ 10 used to work (in fact, still does on my home computer) *snip* If your Vim is built with Motif, it simply will not be able to use the "new style" fonts like "Luxi Mono";

Re: Patch 7.3.798

2013-02-01 Fir de Conversatie Tony Mechelynck
On 01/02/13 20:41, Ken Takata wrote: Hi toothpik, 2013/02/02 Sat 4:27:54 UTC+9 toothpik: that was my point: version.c didn't get updated by my 'hg pull' so version still shows 797 Did you do 'hg update' after 'hg pull'? Thanks, Ken Takata Good point. "hg pull" by itself makes the new cha

Re: what happened to luxi mono?

2013-02-01 Fir de Conversatie Tony Mechelynck
On 01/02/13 20:37, Charles Campbell wrote: Tony Mechelynck wrote: On 01/02/13 18:11, Charles Campbell wrote: James McCoy wrote: On Feb 1, 2013 11:43 AM, "Charles Campbell" mailto:charles.e.campb...@nasa.gov>> wrote: I've found some more out -- it appears that several directories and files g

Re: [patch] Limit window size on all platforms when setting lines/columns

2013-02-01 Fir de Conversatie Bram Moolenaar
Daniel Harding wrote: > The attached patch is a follow-up to patch 7.3.117 (Problem: When > changing the font size, only MS-Windows limits the window size. > Solution: Also limit the window size on other systems. (Roland > Puntaier)). That patch fixed the problem that on non-MS-Windows > s

Re: New featuabsolute line number in relativenumber for the current line

2013-02-01 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: > Hi François! > > On Fr, 01 Feb 2013, François Ingelrest wrote: > > > On Wed, Jan 30, 2013 at 12:31 PM, Bram Moolenaar wrote: > > > This looks like a good solution. I'll include it. With Christian's > > > addition. > > > > I think I found a case where the 'relative

Re: what happened to luxi mono?

2013-02-01 Fir de Conversatie Christian J. Robinson
On Fri, 1 Feb 2013, Charles Campbell wrote: My vim's status: * :set guifont=Luxi\ Mono\ 10 used to work (in fact, still does on my home computer) *snip* If your Vim is built with Motif, it simply will not be able to use the "new style" fonts like "Luxi Mono"; you will be stuck with the

Re: Patch 7.3.798

2013-02-01 Fir de Conversatie Ken Takata
Hi toothpik, 2013/02/02 Sat 4:27:54 UTC+9 toothpik: > that was  my point:  version.c didn't get updated by my 'hg pull' so version > still > shows 797 Did you do 'hg update' after 'hg pull'? Thanks, Ken Takata -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type

Re: what happened to luxi mono?

2013-02-01 Fir de Conversatie Charles Campbell
Tony Mechelynck wrote: On 01/02/13 18:11, Charles Campbell wrote: James McCoy wrote: On Feb 1, 2013 11:43 AM, "Charles Campbell" mailto:charles.e.campb...@nasa.gov>> wrote: I've found some more out -- it appears that several directories and files got changed so that only root had access. fc

Re: Patch 7.3.798

2013-02-01 Fir de Conversatie toothpik
that was  my point:  version.c didn't get updated by my 'hg pull' so version still shows 797 sc > > From: Christian Brabandt >To: "vim_dev@googlegroups.com" >Sent: Friday, February 1, 2013 11:36 AM >Subject: Re: Patch 7.3.798 > >Hi toothpik! > >On Fr, 01 F

Re: Patch 7.3.786

2013-02-01 Fir de Conversatie Bram Moolenaar
Ken Takata wrote: > 2013/01/31 Thu 5:56:41 UTC+9 Bram Moolenaar wrote: > > > That doesn't look right, it would access pygilstate before setting it. > > Hmm, but the same can be said of if_python.c. pygilstate would be > accessed in Python_SaveThread() because PY_CAN_RECURSE is normally defined

Re: what happened to luxi mono?

2013-02-01 Fir de Conversatie Tony Mechelynck
On 01/02/13 18:11, Charles Campbell wrote: James McCoy wrote: On Feb 1, 2013 11:43 AM, "Charles Campbell" mailto:charles.e.campb...@nasa.gov>> wrote: > I've found some more out -- it appears that several directories and files got changed so that only root had access. fc-list now shows Luxi Mo

Re: Patch 7.3.798

2013-02-01 Fir de Conversatie Christian Brabandt
Hi toothpik! On Fr, 01 Feb 2013, toothpik wrote: > I have a script I call u that performs a > >     cd ~/.build/vim/vim > >     hg pull 2>&1 >> ../update.log > > I'm also on suse 12.1 -- small world What does your :version show? The patch included a change to the version.c file (as you can s

Re: what happened to luxi mono?

2013-02-01 Fir de Conversatie Christian Brabandt
Hi Charles! On Fr, 01 Feb 2013, Charles Campbell wrote: > James McCoy wrote: > > > > > >On Feb 1, 2013 11:43 AM, "Charles Campbell" > >mailto:charles.e.campb...@nasa.gov>> > >wrote: > >> I've found some more out -- it appears that several directories > >and files got changed so that only root had

Re: what happened to luxi mono?

2013-02-01 Fir de Conversatie Charles Campbell
James McCoy wrote: On Feb 1, 2013 11:43 AM, "Charles Campbell" mailto:charles.e.campb...@nasa.gov>> wrote: > I've found some more out -- it appears that several directories and files got changed so that only root had access. fc-list now shows Luxi Mono fonts, for example. > > However, I st

Re: what happened to luxi mono?

2013-02-01 Fir de Conversatie James McCoy
On Feb 1, 2013 11:43 AM, "Charles Campbell" wrote: > I've found some more out -- it appears that several directories and files got changed so that only root had access. fc-list now shows Luxi Mono fonts, for example. > > However, I still can't get vim to accept > > :set guifont=Luxi\ Mono\ 10 >

Re: what happened to luxi mono?

2013-02-01 Fir de Conversatie Charles Campbell
Taylor Hedberg wrote: Charles Campbell, Fri 2013-02-01 @ 11:30:47-0500: Taylor Hedberg wrote: Is the font *only* missing in Vim, or has it disappeared from other applications as well? Does it show up under xfontsel and/or fc-list on your system? xfontsel : trying family, no luxi present fc-lis

Re: what happened to luxi mono?

2013-02-01 Fir de Conversatie Taylor Hedberg
Charles Campbell, Fri 2013-02-01 @ 11:30:47-0500: > Taylor Hedberg wrote: > >Is the font *only* missing in Vim, or has it disappeared from other > >applications as well? Does it show up under xfontsel and/or fc-list on > >your system? > xfontsel : trying family, no luxi present > fc-list : no luxi

Re: what happened to luxi mono?

2013-02-01 Fir de Conversatie Charles Campbell
Taylor Hedberg wrote: Is the font *only* missing in Vim, or has it disappeared from other applications as well? Does it show up under xfontsel and/or fc-list on your system? xfontsel : trying family, no luxi present fc-list : no luxi present Its really odd that Luxi disappeared from the system;

Re: what happened to luxi mono?

2013-02-01 Fir de Conversatie Taylor Hedberg
Is the font *only* missing in Vim, or has it disappeared from other applications as well? Does it show up under xfontsel and/or fc-list on your system? signature.asc Description: Digital signature

Re: Patch 7.3.798

2013-02-01 Fir de Conversatie toothpik
I have a script I call u that performs a     cd ~/.build/vim/vim     hg pull 2>&1 >> ../update.log I'm also on suse 12.1 -- small world sc > > From: Tony Mechelynck >To: vim_dev@googlegroups.com >Sent: Friday, February 1, 2013 5:40 AM >Subject: Re: Patch 7.

what happened to luxi mono?

2013-02-01 Fir de Conversatie Charles Campbell
Hello! I seem to have run into a font problem -- as in the font I was using, "Luxi Mono 10", is no longer a valid font. Here's what happened: * used gvim with Luxi Mono 10 * broke for lunch * returned * updated vim from 7.3.784 to 7.3.796 * Luxi mono font no longer available Now, my system i

Re: New feature: absolute line number in relativenumber for the current line

2013-02-01 Fir de Conversatie David Fishburn
On Thu, Jan 31, 2013 at 7:42 PM, Charles E Campbell < drc...@campbellfamily.biz> wrote: > Ben Fritz wrote: > >> I only rarely edit files with 1 or more lines. Most of the time for >> me, my 'rnu' column takes 4 columns, and my 'nu' column takes 5. I don't >> care about the extra width, and wou

Re: Patch 7.3.798

2013-02-01 Fir de Conversatie Cesar Romani
On 31/01/2013 10:36 p.m., Sergey Khorev wrote: > > It also doesn't work on Windows by building with MinGW. > I always get: > > [...] > ... -freg-struct-return -s -DINCLUDE_MZSCHEME_BASE if_mzsch.c -o > gobjZi386/if_mzsch.o > if_mzsch.c: In function 'window_new': > if_mz

Re: Patch 7.3.798

2013-02-01 Fir de Conversatie Tony Mechelynck
On 01/02/13 02:48, toothpik wrote: for me, version.c was not updated when I pulled this update -- I didn't expect much since I don't build for mzscheme, but at least version should have updated sc Neither do I (the script I source before building includes the line export CONF_OPT_MZSCHEME='--

Re: New feature: absolute line number in relativenumber for the current line

2013-02-01 Fir de Conversatie Nazri Ramliy
On Fri, Feb 1, 2013 at 8:42 AM, Charles E Campbell wrote: > When some users of some simulation s/w I helped write have a problem, I > usually end up with 10-150G long debugging traces; I usually break these up > into 1G chunks and "edit" (more usually, examine) these. So I often end up > with fil

Re: New featuabsolute line number in relativenumber for the current line

2013-02-01 Fir de Conversatie Christian Brabandt
Hi François! On Fr, 01 Feb 2013, François Ingelrest wrote: > On Wed, Jan 30, 2013 at 12:31 PM, Bram Moolenaar wrote: > > This looks like a good solution. I'll include it. With Christian's > > addition. > > I think I found a case where the 'relativenumber' option is reset. I'm > sending this re