On 2009-01-11, at 13:54, hamlen wrote:
I've been meaning to request a patch that does exactly what Jonathon's
patch does except only when a specific option appears in scrollopt.
Here's a version that does that (as well as significantly cleaning up
the code). I did the reverse, adding the
Did you think about use leases to exclusively lock file during save?
I mean fcntl() with F_SETLEASE. It acquires mandatory lock and doesn't break
hard links, which you afraid of. Processes which try to read file during
saving are blocked on open() until lease is removed, so it doesn't change
This patch is completely rewritten, with very little in common with
the previous one. Again, some review is much needed. I didn't adjust
the documentation; is it customary for me to do that, or to have Bram
do it?
That's your job.
Nico
--~--~-~--~~~---~--~~
On 2009-01-12, at 03:29, Nico Weber wrote:
This patch is completely rewritten, with very little in common with
the previous one. Again, some review is much needed. I didn't adjust
the documentation; is it customary for me to do that, or to have Bram
do it?
That's your job.
OK, once more
Hi everyone,
I've been troubled by this issue some time ago but I didn't report it
because I was not sure it was caused by colorscheme or other situation
external to vim. Today other people (in IRC) confirmed the problem and
suggested reporting it.
The picture [1] represents the problem.
The
On 11/01/09 22:43, Renato Alves wrote:
Hi everyone,
I've been troubled by this issue some time ago but I didn't report it
because I was not sure it was caused by colorscheme or other situation
external to vim. Today other people (in IRC) confirmed the problem and
suggested reporting it.
From Tony Mechelynck on 01/12/2009 02:29 AM:
On 11/01/09 22:43, Renato Alves wrote:
Hi everyone,
I've been troubled by this issue some time ago but I didn't report it
because I was not sure it was caused by colorscheme or other situation
external to vim. Today other people (in IRC)
On 12/01/09 04:55, Renato Alves wrote:
[...]
Hi Tony,
Thanks for your feedback.
I understand that console level is a potential headache since there are
a ton of different consoles/terms and not all support the same features.
However the reason why I reported this was not to address yet
