I noticed a typo in version7.txt. Attached patch fixes it.
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
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
to the file after (or before, depending
on the direction that the user was navigating when the swap file was
found).
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
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 message because you
: ! * Prepare the read buffers for reading (if they contains something).
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
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
list is
set, which is the expected behaviour.
I checked out your patch, but for me it gives counter-intuitive
results. I get a | char on position 3, 5, 7, 9, 11 etc (ts = 2, sw =
2).
Attached is a screen shot of what I mean.
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
On Wed, Mar 12, 2014 at 2:46 PM, Francisco Lopes
francisco.mailing.li...@oblita.com wrote:
Does Vim do that trying to be smart? because it doesn't seem a behavior of
the plugin
Any other plugins you've loaded? delimitMate comes to mind...
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41
Hi,
just have to share this here:
https://twitter.com/robertnyman/status/446547284915150848
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
Hi,
On Tue, Mar 4, 2014 at 8:37 AM, Christ van Willegen
cvwille...@gmail.com wrote:
Hi hari.g,
On Sun, Dec 1, 2013 at 9:07 AM, hari.g harig...@gmail.com wrote:
After giving this more thought, I feel that overloading 'list' and
'listchars'
to show indentation levels is not right. Also
--enable-rubyinterp
You can get around this by adding --disable-smack on the configure line.
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
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 message because you
-round
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
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 message
attachments by carrier pigeon is _only_ supported on April 1st.
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
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
sent twice because an ACK was not received 'in time'.
Vague description, I know, but I haven't really seen the problem myself...
Then again, maybe this one also gets dupped, you get another example :-)
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
crushing corn and olive oil comes from crushing olives,
so where does baby oil come from?
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit
Hi,
Not sure if this is related...
When I'm editting code ia SSH on an Ubuntu 11.10 machine, the screen is
messed up very easily if I use anything but width 80. Ctrl-l fixes it
temporarily.
I'm not using listchars. What can I do to tey to reproduce this?
Christ van Willegen
--
You received
Hello,
my first patch ever, so bear with me...
I'm editting a lot of .twig (HTML template) files lately, and I
noticed that the syntax file for twig exists, but the file type was
not set automatically. So, I went ahead and added it to my
filetype.vim. Included is the patch.
Christ van Willegen
?
The only thing I am unsure about is the while loop taking out \n/\r
from the end of the file name... is this the way it should be done?
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply
that there are a few typos in the revised README.txt.
First of all, 'maillists' should probably be 'mailing lists'. And the
lonely 't' looks like it shouldn't be there,
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
You received this message from the vim_dev maillist.
Do
On Jul 27, 2011 12:59 AM, Benjamin R. Haskell v...@benizi.com wrote:
Here's the whole set for testing:
₀₁₂₃₄₅₆₇₈₉
Of those 10 chars, _only_ 1 to 4 show up on my tablet's screen... so that
may be an indication of special status as wel?
Christ van Willegen
--
You received this message from
(almost completely?) fallen from
usage, but wouldn't it be more complete to also specify this trigraph
in the regular expression(s)? It's probably a PITA to support them,
but for completeness sake...
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
You received this message
files...
Christ van Willegen
--
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
...' on the receiving end in one case...
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
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
in the documentation at the top of the diff...
Also I'd suggest:
- This is most usefule, to finetune
- This is most useful to finetune
Christ van Willegen
--
--
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
*/
+ name[1] = (int)KE_FOCUSGAINED;
+ add_termcode(name, (char_u *)\033[I, FALSE);
Does add_termcode handle a non-zero terminated string?
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply
?
Yes, in term.c, names of termcode seem to be always treated as fixed
size(2byte) data.
I confirmed these are always accessed with bracket operators [], at least
in add_termcode().
Ok! Like I said tis was only from looking at the diff, not at the full
source code...
Christ van Willegen
--
09
.
+ */
+ void
+ may_req_bg_color()
+ {
+ if (rbg_status == RBG_GET
That comment looks wrong for that function.
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
Or even:
's' drop one empty item at start
'S' drop all empty items at start
(same for 'e' and 'E')
Christ van Willegen
--
--
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 ht
I'll try to look into this myself, but I
wanted to put the RFE here first, since other people may have a better
insight into the code, and may have done this before (it would be my
first or second Vim patch...)
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
You
modified hidden buffer, the current buffer is
> ! abandoned and the first changed hidden buffer becomes
> the current buffer.
> Use ":qall!" to exit always.
Small nitpick in the docs: The first line of
> + char_u s[4];
> + sprintf((char *)s, " @%c", Recording);
> + MSG_PUTS_ATTR(s, attr);
> + }
> + }
Is it (perhaps remotely...) possible to record into a register that
internally translates to a 2-byte value, overflowing the buffer
allocated to be 4 by
On Thu, Nov 19, 2015 at 10:45 PM, Christian Brabandt <cbli...@256bit.org> wrote:
> On Do, 19 Nov 2015, Christ van Willegen wrote:
>> Is it (perhaps remotely...) possible to record into a register that
>> internally translates to a 2-byte value, overflowing the buffer
>&
On Mon, Feb 22, 2016 at 11:13 PM, Bram Moolenaar <b...@moolenaar.net> wrote:
>
> Tux wrote:
>
>> Well, well.
>
> Sorry, I find it difficult to count beyond 4. :-)
I find that difficult to believe since VI is 6 in roman numerals ;-)
Christ van Willegen
--
--
You
us != JOB_STARTED
> || (job->jv_stoponexit == NULL && job->jv_exit_cb == NULL))
> + {
> job_free(job);
> + }
Any particular reason these {} were added? It seems contrary to the
usual coding style...
Christ van Willegen
--
--
for the string to become equal? If it
only returns if the comparison is true, the assert after that call is
useless...
Christ van Willegen
--
--
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 in
color|
> + t_8bset background color (R, G, B) *t_8b*
> *'t_8b'*
> + |xterm-true-color|
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type y
*/
! c = *ptr
Now you miss that assignment into c.
Christ van Willegen
--
--
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 receive
Op 21 sep. 2016 23:40 schreef "Marty Chang" <vim-dev-git...@256bit.org>:
>
> Actually I ran :scriptnames inside Vim as suggested on another thread and
found that the py.vim file I put inside ~/.vim/ftplugin didn't even execute.
Shouldn't it be called python.vim then
That I should never exit a file with the cursor at
the end? Or I should not use the documented restore-cursor code?
Is it possible to wrap that code into
if ('')
Please correct me if I'm wrong, I don't do much Vim scripting...
Christ van Willegen
--
--
You received this message from the "
Op 14 okt. 2016 17:21 schreef "Martin Vuille" <vim-dev-git...@256bit.org>:
>
> But I am unsure how to incorporate the files "foo" and "bar" into the
test.
You can write them from the test.
Christ van Willegen
--
--
You received this message from the
Op 1 dec. 2016 14:54 schreef "Brenton Horne" <vim-dev-git...@256bit.org>:
>
> Why vim-win32-installer?
_Like_ vim-win32-installer...
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the te
Op 1 dec. 2016 15:28 schreef "Brenton Horne" <vim-dev-git...@256bit.org>:
>
> Yep, I know that's why I deleted that comment.
Oh, I reacted via the mailing list, I didn't know that! Sorry...
Christ van Willegen
--
--
You received this message from the "vim_dev"
> +#ifdef FEAT_MBYTE
> +if ((eap->cmdidx != CMD_make) && (eap->cmdidx != CMD_lmake))
> +{
> +/* Use 'genc' for grep commands if it is set. */
> +if (*curbuf->b_p_genc != NUL)
> +enc = curbuf->b_p_genc;
> +else if (*p_genc != NU
On Tue, Jan 3, 2017 at 9:50 AM, Ken Takata <ktakata65...@gmail.com> wrote:
> Hi,
>
> 2017/1/3 Tue 17:38:15 UTC+9 Christ van Willegen wrote:
>> Here as well (is it my viewer?? Ah! Mixed tabs and spaces! It isn't my
>> viewer after all! Are mixed spaces/tabs allowed in
Op 7 dec. 2016 17:03 schreef "lacygoill" <vim-dev-git...@256bit.org>:
I don't know where to find the patch and how to apply it..
If it's correct, it will be applied by Bram Moolenaar and distributed in an
official version. You'll just have to wait...
Christ van Willegen
--
e, wp === curwin (by the if above it), therefore
it can't be == NULL...
Regards,
Christ van Willegen
--
--
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/maill
a 'should never happen' case. I looked at the invocations of
that function, and saw that wp is used everywhere. So it either has
been checked, or was NULL way before ever reaching this point.
YMMV, maybe I didn't investigate long enough...
Christ van Willegen
--
--
You received this message fr
Hi,
This part looks weird:
- qf_jump(qi, 0, 0, forceit);
+
+ if (!forceit)
+ {
+ qf_jump(qi, 0, 0, forceit);
+ }
Might as well write qf_jump(qi, 0, 0, false) there...
Christ van Willegen
--
--
You received
l GA
Weird sig...
Christ van Willegen
--
--
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 message because you are subsc
ng width and height.
Christ van Willegen
--
--
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 message because you are su
Op 4 nov. 2017 11:49 schreef "Christian Brabandt" <vim-dev-git...@256bit.org
>:
I am sorry, I can hardly understand. Please give precise steps to reproduce
the issue.
He means not letting go of the Ctrl key, but holding it all the time.
Christ van Willegen
--
--
You recei
Hi,
Someone will surely mention this, but you should move the old maintainer to
a line with "Previous maintainer"
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For mor
String turn time value into a String
Shouldn't both these functions have "String" as their return type?
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For m
Hi Hirohito Higashi,
On Wed, May 23, 2018 at 12:05 PM, h_east <h.east@gmail.com> wrote:
> Hi Christ,
>
> Oh, It's my mistake.
> Attached patch fixes this.
>
> Thanks for reporting!
You're welcome!
Christ van Willegen
--
--
You received this message from the "
greeing). "don't" is
> the correct form ("buffers that don't have a name", where the subject of
> "don't" is "that" = "buffers").
>
The patch proposes don't, so it is correct.
Christ van Willegen
--
--
You received this message from the
Do you have expandtabs set? That would explain this, I think...
Christ van Willegen
--
--
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
---
Yo
uot; condition looks weird. It looks as if the variable u_sync_once is
set to 2 unconditionally, and then tested if it is == 1. I'm probably
wrong, though...
Christ van Willegen
>
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply be
Hi,
Perhaps you were bitten by
https://github.com/vim/vim/commit/fc65cabb15d0236bce001ad78e12a40511caf941#commitcomment-30321957
I don't know if and when Bram has updated this.
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type
*/
struct buffblock
{
buffblock_T *b_next;/* pointer to next buffblock */
char_u b_str[FLEX_ARRAY]; /* contents */
};
This way, you only need to write the code once, and the compiler gets
tested in both cases.
If the compiler(s) all get flexible array compatibility, the
characters in the 'mask' parameter is an 'r'...
Christ van Willegen
--
--
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 mes
g and/or end of strings, not out of the middle
>
> I need to learn to have more faith in myself
>
If you tested it, I'm sure you've seen the result. I only looked at the
docs, wondered about the missing "r" and thought "that's because it's part
of the mask and the rest of the resul
Op di 16 okt. 2018 14:51 schreef zdohnal :
> Would anyone mind giving me a hint what can cause behavior what user
> experiences? Was it possible to do this style of copy/pasting in the past
> and it changed? Or is it the bug?
>
Sounds like bracketed paste mode interfering somehow?
ple. If they keep failing, can
I send the patches directly to the list?
Christ van Willegen
--
--
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.
initstr += 2;" as wel...)
Bram, should the pattern at the top of this function be changed to
note that these names for the executable are not recognized? Not sure
if 'viex' or 'viexim' would make sense...
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist
v_ga.ga_len = len;
>
Will this never fail?
Christ van Willegen
>
--
--
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 th
Op ma 7 jan. 2019 21:17 schreef Bram Moolenaar
> Ken Takata wrote:
>
> > * The latest version of Elvis is 2.2. Not being developed now.
>
> Yeah, it appears to have faded away.
>
Left the building?
I'll see myself out now...
Christ van Willegen
>
--
--
You re
t;
> *** ../vim-8.1.0405/src/testdir/test_startup.vim2018-09-16
> 16:28:08.358268312 +0200
> --- src/testdir/test_startup.vim
>
+ " Test the -V[N] argument to set the 'version' option to [N]
>
Verbose?
Christ van Willegen
--
--
You received this message from the &q
bution...
Christ van Willegen
--
--
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 message because you are subscribed to t
Op wo 27 feb. 2019 15:03 schreef Bram Moolenaar :
> Please include the Vim patch number. A hex number is not very useful
>
That was a specific commit to Github, I guess...
Christ
>
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text
The declaration of char *cp should be left at the top of the function.
Setting the value can be where you put it.
Christ van Willegen
Op do 7 feb. 2019 22:30 schreef Friedrich2 Found with cppcheck 1.86. Please c. f. the commit descriptions.
> --
> You ca
*p = '/';
> +
> + #if defined(FEAT_MBYTE) && defined(WIN3264)
>
FEAT_MBYTE was recently promoted, right?
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For mo
Op vr 8 feb. 2019 20:55 schreef bam80 It seems the email address NdrOchip@ScampbellPfamily.AbizM-NOSPAM is
> invalid.
>
> That's because you didn't remove the capital letters (NOSPAM) from the
> address.
>
> I did. Still no reply :(
>
Including the ones inside the address?
Op di 12 feb. 2019 22:15 schreef Bram Moolenaar Closed #3941 <https://github.com/vim/vim/issues/3941> via 57ee2b6
> <https://github.com/vim/vim/commit/57ee2b6e0b5b730d12ee9db00a8e2a577df9e374>
> .
>
That commit looks totally unrelated to regular expressions...
Op do 24 jan. 2019 01:39 schreef Bram Moolenaar
> Christ van Willegen wrote:
>
> > Op wo 23 jan. 2019 21:57 schreef Bram Moolenaar >
> > >
> > > Patch 8.1.0798
> > >
> > > + if (len > 0)
> > > + to->vva
"line", wp->w_winrow + 1);
> + dict_add_number(dict, "col", wp->w_wincol + 1);
> + dict_add_number(dict, "width", wp->w_width);
> + dict_add_number(dict, "height", wp->w_height);
> + }
> + }
>
What happens if
) && (options[opt_idx].flags & P_SECURE))
> return e_secure;
>
> +/* Safe the global value before changeing anything. This is needed as for
>
> s/Safe/Save/ ?
>
Also, it should be "changing"
Christ van Willegen
>
--
--
You received this
of the languages I 'touched', so I can't take over
maintenance.
Please consider including these with Vim.
Christ van Willegen
--
--
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://w
txt
@@ -132,7 +132,7 @@ When using replace mode, the text properties stay
on the same character
positions, even though the characters themselves change.
-When text property columns are not updated ~
+When are text property columns not updated ~
- When setting the line with |setline()| or through
Hi,
I see that Heiko Erhardt has stopped development of this plugin, so
I'm sending this patch to the list instead.
It just fixes some comments, nothing more.
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below th
Hi Yegappan,
On Fri, Jul 19, 2019 at 8:39 AM Yegappan Lakshmanan wrote:
> On Thu, Jul 18, 2019 at 11:31 PM Christ van Willegen
> wrote:
> >
> > Hi,
> >
> > Op vr 19 jul. 2019 07:56 schreef Yegappan Lakshmanan
> > :
> >>
> >> I have por
e
> ! down. A click in the lower half wil scroll the text one line up.
> However,
> this is limited so that the popup does not get smaller.
>
I would suggest the text to read "A click in the upper half of the
scrollbar will scroll the text down one line. A click in the lower half
wil scroll
gt; buf_T *buf = NULL;
> ! dict_T*d = NULL;
> int nr;
> int i;
>
> ! if (argvars != NULL)
> {
> ! // Check arguments look OK.
"Check that arguments look OK" looks better IMHO
Christ van Wil
et var ?= value", conditional assignment. Patch by Dave Eggum,
>2006 Dec 11.
>
> There are one or two places in the patch that include code or comments
that implements the .= operator.
Is that intentional?
Christ van Willegen
>
--
--
You received this message from the "
Op do 7 nov. 2019 23:09 schreef Bram Moolenaar :
>
> Patch 8.1.2269
>
> ***
> *** 3367,3372
> --- 3360,3367
> break;
> #endif
> *pbuf_end++ = *str++;
> + if (pbuf_end - pbuf + 1 >= LSIZE)
> + bre
m_strchr(p, ' ') != NULL)
> + {
> + len = STRLEN(p) + 3; // two quotes and a trailing NUL
> + cmd = alloc(len);
>
Shouldn't you check for a NULL pointer here?
Christ van Willegen
>
--
--
You received this message from the "vim_dev" mailli
)
> " works with and without :call
> assert_equal(4, g:counter)
> ! assert_equal(4, g:counter)
> unlet g:counter
> enddef
>
If it's supposed to work with and without call(), why did you delete one of
them?
Christ van Willegen
--
--
You received this messag
Op za 22 feb. 2020 14:27 schreef Bram Moolenaar :
>
>
>
> + *v:numbersize*
> *numbersize-variable*
> + v:numbersize Number of bits in a Number. This is normally 64, but on
> some
> + systems it my be 32.
> +
> --- 99,110
> # define rb_ary_detransient rb_ary_detransient_stub
> #endif
>
> + // On macOS pre-installed Ruby defines "SIZEOF_TIME_T" as "SIZEOF_LONG" so
> it
> + // conflicts with the definition in config.h then causes macro-redifned
> warn
({'a': 99, 'b': 100}, d)
> endfunc
>
> + " Cannot use += with a locked dick
This is probably true, but I guess you meant 'dict' here..
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
You received this message from the "vim_dev" maillist.
Do
.
Fix if you see fit to do so.
Christ van Willegen
>
--
--
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 message becaus
mNpixmapData, menu->xpm);
XtSetArg(args[n++], XmNlabelLocation, XmBOTTOM);
}
would have been nicer in the first place, I think... No {} needed!
I assume that those are function calls!
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
Do not top-post!
Hi,
two typos fixed below...
Christ van Willegen
On Sat, Jun 13, 2020 at 3:48 PM Bram Moolenaar wrote:
> Patch 8.2.0970
> Problem:Terminal properties are not available in Vim script.
> Solution: Add the terminalprops() function.
> Files: src/term.c, src/proto/t
Op zo 29 nov. 2020 14:21 schreef Bram Moolenaar :
>
> Patch 8.2.2069
>
> + " Test for updating the quickfix buffer whenever the assocaited quickfix
> list
> + " is changed.
>
Associated
Christ van Willegen
>
--
--
You received this message from the "v
Op vr 20 nov. 2020 11:40 schreef Naruhiko Nishino :
> This PR will be fix the flickering.
>
+ if (0 < title_len)
+ {
Personally, I find this inverted condition hard to read. Could you
change it to tl>0?
Thanks!
Christ van Willegen
--
--
You received this
setcursor();
> + out_flush();
> + }
> + }
> + #endif
>
If the (Un)focus escape sequence happens to be sent twice, the key_name[1]
will not be set to KE_IGNORE. Is that a problem?
Christ van Willegen
>
--
--
You received this message from t
* Returns:
> ! * Number option: gov_number, *numval gets value.
> ! * Tottle option: gov_bool, *numval gets value.
>
Toggle option meant here??
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text yo
lled with spaces
> + leadcol += (colnr_T) (ptr - line) + 1;
> + }
> }
>
I guess this won't work for multi byte characters, although these won't
match whitespace. So, the code probably works as is... ignore this comment
;-)
Christ van Willegen
>
--
--
You received this m
(eap, , line_arg, _to_free) == FAIL
) would make this case faster, and really skip getting the function
body. Or do you _need_ to get the function body here in order to go to
the correct spot in the script??
Christ van Willegen
--
--
You received this message from the "vim_dev"
;w_width is a non zero value, _and_ the call to
win_col_off(curwin) returns the same value, then width can become 0. I do
not have the code here to check if this is possible...
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! T
that the abbreviation for the option is tsrfu and the
variable is called thsfu, but that's just nitpicking I guess...
Christ van Willegen
>
--
--
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
Op ma 29 nov. 2021 18:13 schreef Tim Chase :
> *@Gumnos* commented on this pull request.
> --
>
> In runtime/syntax/vb.vim
> <https://github.com/vim/vim/pull/9233#discussion_r758570913>:
>
> >
>
> " String and Character cont
1 - 100 din 140 matches
Mail list logo
