On Dec 3, 10:21 pm, Gregory Margo wrote:
> On Wed, Dec 02, 2009 at 08:20:40PM -0800, JD wrote:
> > Vim is hardlocking ... FreeBSD 5.4
>
> No offense, but are you really using such an old (2005-vintage) FreeBSD
> release?
>
> Or is it really OpenBSD 5.4, a much more recent product?
>
> --
> ++
On Wed, Dec 02, 2009 at 08:20:40PM -0800, JD wrote:
> Vim is hardlocking ... FreeBSD 5.4
No offense, but are you really using such an old (2005-vintage) FreeBSD release?
Or is it really OpenBSD 5.4, a much more recent product?
--
+
On 03/12/09 12:49, Henrik Öhman wrote:
> On Dec 3, 2:14 am, "John Beckett" wrote:
>> Steve Hall wrote:
>>> Hmm, so then the original MyDiff() might have been ok for you?
>>
>> No. People have complained on the wiki that the "Vim without
>> Cream" distribution does NOT work with diff. There were se
On Thu, 2009-12-03 at 03:49 -0800, Henrik Öhman wrote:
>
> I was wondering why I hadn't discovered this problem, and then I
> realised it's because I haven't used the _vimrc that "Vim without
> Cream" uses since I first installed Vim.
I have to admit, I haven't used a default vimrc since 1999. :
On 03/12/09 21:16, JD wrote:
> On Dec 3, 4:26 am, Tony Mechelynck
> wrote:
>> On 03/12/09 08:03, JD wrote:
>>
>>
>>
>>> On Dec 3, 1:46 am, Tony Mechelynck
>>> wrote:
On 03/12/09 05:20, JD wrote:
>>
> Vim is hardlocking for me on every single run on my FreeBSD 5.4
> system. I've tried 7
On Dec 3, 4:26 am, Tony Mechelynck
wrote:
> On 03/12/09 08:03, JD wrote:
>
>
>
> > On Dec 3, 1:46 am, Tony Mechelynck
> > wrote:
> >> On 03/12/09 05:20, JD wrote:
>
> >>> Vim is hardlocking for me on every single run on my FreeBSD 5.4
> >>> system. I've tried 7.2.299, 7.2.309 and 7.2.315 and all a
On Thu, Dec 3, 2009 at 12:30 PM, Charles Campbell
wrote:
> James Vega wrote:
>> On Thu, Dec 03, 2009 at 01:06:54PM +0100, Karsten Hopp wrote:
>>
>>> Hi,
>>>
>>> I've got a bugreport that you might end up with invalid syntax files
>>> when the automated download for new spell files is used.
>>> Tha
James Vega wrote:
> On Thu, Dec 03, 2009 at 01:06:54PM +0100, Karsten Hopp wrote:
>
>> Hi,
>>
>> I've got a bugreport that you might end up with invalid syntax files
>> when the automated download for new spell files is used.
>> That's https://bugzilla.redhat.com/show_bug.cgi?id=518791
>>
>> It
On Thu, Dec 03, 2009 at 01:06:54PM +0100, Karsten Hopp wrote:
> Hi,
>
> I've got a bugreport that you might end up with invalid syntax files
> when the automated download for new spell files is used.
> That's https://bugzilla.redhat.com/show_bug.cgi?id=518791
>
> It looks like elinks -dump forma
Am 03.12.2009 13:06, schrieb Karsten Hopp:
> Hi,
>
> I've got a bugreport that you might end up with invalid syntax files
> when the automated download for new spell files is used.
^^^ spell
--
Hi,
I've got a bugreport that you might end up with invalid syntax files
when the automated download for new spell files is used.
That's https://bugzilla.redhat.com/show_bug.cgi?id=518791
It looks like elinks -dump formats the contents of the downloaded file,
try p.e.
elinks 'http://ftp.vim.or
On Dec 3, 2:14 am, "John Beckett" wrote:
> Steve Hall wrote:
> > Hmm, so then the original MyDiff() might have been ok for you?
>
> No. People have complained on the wiki that the "Vim without
> Cream" distribution does NOT work with diff. There were several
> misguided suggestions for how to make
On 12/02/2009 11:59 AM, Bram Moolenaar wrote:
> Patch 7.2.315
> Problem:Python libs can't be found on 64 bit system.
> Solution: Add lib64 to the list of directories. (Michael Henry)
> Files:src/auto/configure, src/configure.in
>
Thanks, Bram, I can confirm that this patch wor
On 03/12/09 09:58, Dominique Pellé wrote:
[...]
> The output of backtrace may help to figure out why it hogs the CPU.
> You will need to compile/link Vim with symbols (-g -O0) to get a proper
> stack trace with gdb.
>
> -- Dominique
>
...and, of course, run the non-stripped executable, i.e., the o
On 03/12/09 08:03, JD wrote:
> On Dec 3, 1:46 am, Tony Mechelynck
> wrote:
>> On 03/12/09 05:20, JD wrote:
>>
>>> Vim is hardlocking for me on every single run on my FreeBSD 5.4
>>> system. I've tried 7.2.299, 7.2.309 and 7.2.315 and all are broken.
>>
>>> It appears to compile fine, but on run, it
jdho...@gmail.com wrote:
> Vim is hardlocking for me on every single run on my FreeBSD 5.4
> system. I've tried 7.2.299, 7.2.309 and 7.2.315 and all are broken.
>
> It appears to compile fine, but on run, it fails to respond to any
> keystrokes and eats nearly 100% of my CPU till I send it a
> SIG
On Dec 3, 3:04 am, Michal Kurgan wrote:
> On Wed, 2 Dec 2009 22:55:10 -0800 (PST)
>
> JD wrote:
> > Thanks for the response Gary. I believe i built vim with debug symbols
> > correctly, but after it hardlocks, kill -6 doesn't dump a core file
> > anywhere i can see nor does it terminate the proce
On Wed, 2 Dec 2009 22:55:10 -0800 (PST)
JD wrote:
> Thanks for the response Gary. I believe i built vim with debug symbols
> correctly, but after it hardlocks, kill -6 doesn't dump a core file
> anywhere i can see nor does it terminate the process
>
Probably you need to set core file size l
18 matches
Mail list logo
