On Fri, Sep 17, 2010 at 4:56 AM, John Beckett johnb.beck...@gmail.com wrote:
Is there anything wrong with sourceforge.net/htmldoc apart from
your desire to get other people involved in maintenance of the FAQ?
What about putting it on http://github.com ? The advantage is that is
easy for other
On Fri, Jul 23, 2010 at 8:17 PM, James Vega james...@jamessan.com wrote:
That's interesting. As far as I can tell, Python's build system doesn't
do this normally. It would appear your distribution (which is?) has
changed that.
In my system the files on lib-dynload are linked to libpython.so
On Wed, Jun 9, 2010 at 11:53 PM, epanda callingel...@hotmail.fr wrote:
If Tony dont alerted me, I though this is another one not related to
'nico io'. I this list, usually people use real names. Or stick to
only one nick.
In the period we live in, with High Definition Wide Screen, I maintain
On Thu, Jun 10, 2010 at 10:26 AM, Luis Carvalho lexcarva...@gmail.com wrote:
Of course, if you can always :set go-=T, then the toolbar is irrelevant for
you. The problem is not having a toolbar users don't like, but having a
toolbar that users enjoy.
[snip]
Unix users usually are more
I'm getting segmentation faults when setting the guidecolumn to any number
The gdb backtrace output is:
---
Program received signal SIGSEGV, Segmentation fault.
0x005374fa in showruler (always=0) at screen.c:9482
9482 leif ((*p_stl != NUL ||
On Sat, May 2, 2009 at 8:09 PM, Kazuo Teramoto kaz@gmail.com wrote:
I'm getting segmentation faults when setting the guidecolumn to any number
The gdb backtrace output is:
---
Program received signal SIGSEGV, Segmentation fault
On Sat, May 2, 2009 at 8:25 PM, Kazuo Teramoto kaz@gmail.com wrote:
On Sat, May 2, 2009 at 8:09 PM, Kazuo Teramoto kaz@gmail.com wrote:
I'm getting segmentation faults when setting the guidecolumn to any number
The gdb backtrace output
On Sat, May 2, 2009 at 8:09 PM, Kazuo Teramoto kaz@gmail.com wrote:
I'm getting segmentation faults when setting the guidecolumn to any number
The gdb backtrace output is:
---
Program received signal SIGSEGV, Segmentation fault
On Sun, May 3, 2009 at 12:11 AM, _Lone lost.stran...@gmail.com wrote:
Are you running on Linux/Unix? I don't have Linux/Unix and I have only
tested with Windows. Can someone else who has access to *nix please
take a look? The crash seems to be in an area outside of the patch
changes but can
On Jan 1, 2008 6:10 PM, Tony Mechelynck [EMAIL PROTECTED] wrote:
Apparently, the fact that I succeeded to connect to a server where /pub/vim
was a vailable, and even to downloaded all patches till 7.1.180, was a
one-time non-repeatable fluke: I cn't do it again.
ftp.vim.org is working for me,
10 matches
Mail list logo