Sounds good, though I'd rather not scope the patch to 10.2
unconditionally - that just reintroduces the same issue for Jaguar
users who want to use FSF GCC to bring themselves up to date.
Unfortunately, I don't have a Mac with gcc-2.95 so I can't confirm
what the version string looks like to write
Hi,
2013/10/14 Mon 16:39:04 UTC+9 ZyX wrote:
If I am not mistaking, this patch includes timers string in has() list two
times.
Oh, it was my mistake.
In f_canceltimeout in a first if in a first if in a while cycle indentation
is wrong: 4 spaces go before tab. Later indentation is wrong
On Sunday, October 20, 2013 10:39:28 PM UTC-5, Andre Sihera wrote:
Furthermore, a timer being effectively an interrupt, there should be
an extra test
case that executes underneath the timer when it fires that can be shown
to produce
a known result when the timer interrupt
On Sunday, October 20, 2013 4:07:20 PM UTC-5, Marvin Renich wrote:
How can you determine what syntax group is used for a particular
character?
http://vim.wikia.com/wiki/Identify_the_syntax_highlighting_group_used_at_the_cursor
--
--
You received this message from the vim_dev maillist.
* Ben Fritz fritzophre...@gmail.com [131021 09:12]:
On Sunday, October 20, 2013 4:07:20 PM UTC-5, Marvin Renich wrote:
How can you determine what syntax group is used for a particular character?
http://vim.wikia.com/wiki/Identify_the_syntax_highlighting_group_used_at_the_cursor
* Marvin Renich m...@renich.org [131021 10:07]:
Thanks, Ben; that's exactly what I was looking for. Hopefully, Dr. Chip
can figure out why the highlighting is wrong. BTW, did you try to
reproduce the incorrect highlighting? I would like to at least know if
this is easily reproducible by
I've applied the following patch to pum_redraw function to avoid rare segfaults
I was suffering.
diff -r 92c9748e0ccb src/popupmnu.c
--- a/src/popupmnu.cSun Oct 06 17:46:56 2013 +0200
+++ b/src/popupmnu.cMon Oct 21 12:29:31 2013 -0200
@@ -295,6 +295,8 @@
for (i = 0; i pum_height;
On Monday, October 21, 2013 9:56:26 AM UTC-5, telemachus wrote:
On Mon Oct 10/21/13 at 10:29, Marvin Renich wrote:
Dr. Chip sent me an updated sh.vim that works. Thank you!
Can I ask what email you used to reach him?
I've had luck in the past with the email address in the header of
On Mon Oct 10/21/13 at 10:29, Marvin Renich wrote:
Dr. Chip sent me an updated sh.vim that works. Thank you!
Can I ask what email you used to reach him? I sent a patch here and to him
a few months ago for sh.vim, but I haven't heard any response from anyone.
(It concerns incorrect indendation
specifically while debugging, pum_first was 1 making idx beyond arrays bounds.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this
On Mon Oct 10/21/13 at 8:04, Ben Fritz wrote:
On Monday, October 21, 2013 9:56:26 AM UTC-5, telemachus wrote:
Can I ask what email you used to reach him?
I've had luck in the past with the email address in the header of his
plugins.
But you need to remove the capital letters NOSPAM
Peter Aronoff wrote:
On Mon Oct 10/21/13 at 8:04, Ben Fritz wrote:
On Monday, October 21, 2013 9:56:26 AM UTC-5, telemachus wrote:
Can I ask what email you used to reach him?
I've had luck in the past with the email address in the header of his
plugins.
But you need to remove the capital
Hi Bram!
On So, 20 Okt 2013, Bram Moolenaar wrote:
Christian Brabandt wrote:
Bram,
when using visual block_mode and replacing the selected block with=20
Enter, Vim currently does not break the line, but inserts the=20
linebreak literally, e.g. when doing this:
On Oct 21, 2013 3:48 PM, Ken Takata ken...@csc.jp wrote:
Hi,
2013/10/14 Mon 16:39:04 UTC+9 ZyX wrote:
If I am not mistaking, this patch includes timers string in has()
list two times.
Oh, it was my mistake.
In f_canceltimeout in a first if in a first if in a while cycle
indentation is
Ran into this guy using ctrl-p. I don't have a traceback, but the problem is
that close_buffer sets win-w_buffer to NULL and set_last_cursor then explodes.
Since w_buffer isn't guaranteed to exist, set_last_cursor should just check
for it.
more info:
close_buffer(win, buf, action,
Francisco Lopes wrote:
I've applied the following patch to pum_redraw function to avoid rare
segfaults I was suffering.
diff -r 92c9748e0ccb src/popupmnu.c
--- a/src/popupmnu.c Sun Oct 06 17:46:56 2013 +0200
+++ b/src/popupmnu.c Mon Oct 21 12:29:31 2013 -0200
@@ -295,6 +295,8 @@
Christian Brabandt wrote:
Bram,
when using visual block_mode and replacing the selected block with=20
Enter, Vim currently does not break the line, but inserts the=20
linebreak literally, e.g. when doing this:
10o12345ESC9k02lC-V9jrCR you are left with:
12^M45
[...]
Geoff Greer wrote:
Thanks for taking time to look at our patch and give feedback. Besides
pausing/resuming timers, are there any other blockers for merging this
patch? Matt and I really want to get it merged, but there's been a
recurring pattern where we address one thing only to have
On Sat, Oct 19, 2013 at 03:04:45PM +0200, Christian Brabandt wrote:
Bram,
when using visual block_mode and replacing the selected block with
Enter, Vim currently does not break the line, but inserts the
linebreak literally, e.g. when doing this:
10o12345ESC9k02lC-V9jrCR you are left with:
Bram Moolenaar wrote:
Francisco Lopes wrote:
I've applied the following patch to pum_redraw function to avoid rare
segfaults I was suffering.
diff -r 92c9748e0ccb src/popupmnu.c
--- a/src/popupmnu.cSun Oct 06 17:46:56 2013 +0200
+++ b/src/popupmnu.cMon
20 matches
Mail list logo
