e we don't check the return value. Getting an out of memory error
here looks very unlikely...
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.v
Op za 1 jun. 2024 11:58:
>
>1. Position the cursor on any line and type the following command:
>
>:.wq!
>
>
>
I guess that the . indicates the range of lines to write, the current one...
Christ van Willegen
>
--
--
You received this message from the "
a
newer version you can try?
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
t; + File ${VIMTOOLS}\libsodium.dll
> +!endif
>
> SetOutPath $0
>
>
Looking at the diff, I can only see that the path to libsodium has changed,
but I don't see any references to libgcc_s_sjlj-1.dll nor anything that
looks like a PATCHLEVEL.
Was there more to include in this p
Hi,
On Sat, Mar 9, 2024 at 6:07 PM Christian Brabandt
wrote:
> is this ready?
>
Yes, but I'm totally unhappy with the way you need to invoke the Makefile
to get this to work, but I couldn't think of a better way :-(
Christ van Willegen
--
--
You received this message from the &q
On Sat, Mar 9, 2024 at 6:06 PM Christian Brabandt
wrote:
> is this ready now?
>
Yes. Or at least, ready for review :-)
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
Typo comment:
+ - {pos1} and {pos2} must belong to a |bufloaded()| buffer.
+ - It is evaluated in current window context, this makes a
+ different if a buffer is displayed in a different window and
+ 'virtualedit' or 'list' is set
*this makes a difference
Christ van Willegen
--
--
You
*argend = NUL;
> +
> semsg(_(e_cannot_use_an_object_variable_except_with_the_new_method_str),
> arg);
> + *argend = c;
> + break;
> + }
> +
>
Will this check fail if the class method using "this." is called
newCalculation()? Or are an
%1$0*2$.*3$d %4$d
*E1404*
(the [flags] are specified _after_ the {n$} positional argument
specifier...) Sorry about that error in the docs!
Christ van Willegen
--
--
You received this message from the "vim_dev" ma
path('gcc')
> +if g:GCC->empty()
> + throw 'Skpped: gcc is not found in $PATH'
> +endif
> +
>
"Skipped" (2 x)
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
ble
in other languages. This same code has been added to NeoVim (as far as I
can tell), so you can reuse translations back and forth.
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 t
Op di 15 aug. 2023 21:27 schreef John Marriott :
> On 14-Aug-2023 02:15, Christian Brabandt wrote:
> > patch 9.0.1704: Cannot use positional arguments for printf()
> >
> > Commit:
> https://github.com/vim/vim/commit/0c6181fec4c362eb9682d5af583341eb20cb1af5
> &g
..@vim.org.
A similar message is in the syntax/README, IIRC...
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
I tried contacting the author, but got their email address wrong, so I'll
just copy my message here. Would you accept this patch, or do you want a PR?
I looked at your PR, and since things are still 'in flux', I thought
I'd share this off-list, beacuse I would like to add to your PR, and
that
e community without Bram, but at them
moment I think we can continue for quite some time 'in his spirit'.
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://
un-contraditionary changes (mostly bug-fixes)
>
I could also read through them to see what they are all about, since you're
still on your holiday. Shall I add a LGTM comment for the PRs I've seen?
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
D
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 the Google Groups
get it.
https://datatracker.ietf.org/doc/rfc2325/history/
1998-04-01
(System) RFC published
So, it's a joke alright...
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
ected 0 but got 642
> command line..script
> /home/runner/work/vim/vim/src/testdir/runtest.vim[569]..function
> RunTheTest[52]..Test_source_files line 40: ../list.c: missing white space
> after "if"/"while"/"for": Expected 0 but got 2340
>
Check l
Hi,
Op di 30 mei 2023 08:00 schreef K.Takata :
> When Vim is compiled with debug mode on MSVC, the following command causes
> an assertion error:
>
This leaks memory, though, because of the malloc() call...
Christ van Willegen
>
--
--
You received this message from the "
ations, could you advise me on how to
proceed with PR #12140 ? CodeCov tells me that it drops coverage a lot, but
I disagree with the computer :-)
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are reply
Op za 29 apr. 2023 16:50 schreef Christ van Willegen :
> Hi,
>
> Op za 29 apr. 2023 13:10 schreef Bram Moolenaar :
>
>>
>> Patch 9.0.1497
>> Problem:The ruler percentage can't be localized.
>> Solution: Use a string that can be translated. (Emir Sari, c
, perc);
And specify %3d%% or %%%-3d in the format string?
Ah, I think not, because you need the space _before_ the %...
I did create #12140 to be able to specify the %$ format, but that doesn't
handle this, either.
Christ van Willegen
>
--
--
You received this message from the "vim_dev"
I think this one is ready for review.
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 b
Op do 2 mrt. 2023 13:08 schreef 依云 :
> If I send you the output of "git diff", is that enough to test?
>
> Yes!
>
I'll be home in about 4.5 hours. That would, probably, be in the middle of
the night for you...
I'll send it via direct email...
Christ van Willegen
&
Hi,
Op do 2 mrt. 2023 11:20 schreef 依云 :
> Hi Christ van Willegen, where is your patch that I can try out?
>
On my computer so far :-)
If I send you the output of "git diff", is that enough to test?
Christ van Willegen
>
--
--
You received this message from the &qu
ight
> > argument from through va_arg().
> >
>
> I'll try to see if I can come up with something...
>
> Christ van Willegen
I didn't realize this was on my to do list so long ago already!
Anyway, I'm (finally!) working on this, and got quite a bit working
alread
Hi,
Totally off topic for this list, but I ran into it and _had_ to share it...
I'll get back in my cave now...
Christ van Willegen
https://fosstodon.org/@ids1024/109515255660791632
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply belo
Op do 27 okt. 2022 20:55 schreef Bram Moolenaar :
>
> I am very sorry to report that I have a medical problem.
>
Beterschap!!
Christ van Willegen
>
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are
Op za 1 okt. 2022 16:34 schreef Bram Moolenaar :
>
>
> + Calling a function in an expr option ~
> +
> *expr-option-function*
> + A few options, such as 'foldexpr', are an expresison that is evaluated
> to get
> + a value.
>
* expression
Christ van Willegen
>
--
Typo:
Op di 21 jun. 2022 23:16 schreef Bram Moolenaar :
> + // Although unlikely, it is possible that the expression
> invokes a
> + // substitute command (it might fail, but still). Therefore
> keep
> + // an array if eval results.
>
Array of
--
--
You
Hi,
Op wo 15 jun. 2022 12:55 schreef Bram Moolenaar :
> A generic solution would be to make the "%1$s" form work with
> vim_snprintf(). I don't know how complicated this is, getting the right
> argument from through va_arg().
>
I'll try to see if I can come up with so
_alloc(rettv) == FAIL)
> + return;
>
...
+ if (rettv_list_alloc(rettv) == FAIL)
> + return;
> +
>
...
+ if (rettv_list_alloc(rettv) != OK)
> + return;
> +
>
Any specific reason why the first compares use == FAIL and the third != OK ?
Christ van Willeg
m_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/20220417201719.8D9731C03BA%40moolenaar.net
> .
>
Here's another one:
//is cleared, we my bounce, but no worse than before.
May
Christ van Willegen
&
initialzed list from a function works
> lines =<< trim END
> vim9script
> var list: list
> *
uninitialized
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the
is no need to import sys, it's done by default.
>
> +
> *python-environment*
> + Environment variables set in Vim are not always available in Python.
> This
> + depends on how Vim and Python were build. Also see
>
built
Christ van Willegen
>
--
--
You received this mess
> {
> char *name = (char *)self->buf->buf->b_fname;
> @@ -5378,7 +5378,7 @@ BufferRange(BufferObject *self, PyObject *args)
> BufferRepr(BufferObject *self)
> {
> if (self->buf == INVALID_BUFFER_VALUE)
> - return PyString_FromFormat("",
> s
e end of the function.
Sorry for the sketchy test, I don't have much experience in writing tests
for Vim9...
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 inf
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
rn (wp->w_p_fdm[0] != NUL && wp->w_p_fdm[2] == 'r');
> }
>
> // foldmethodIsSyntax() {{{2
> *** ../vim-8.2.3661/src/version.c 2021-11-24 14:59:12.573593141 +
> --- src/version.c 2021-11-24 15:13:09.260714187 +
> ***
> *** 75
Hi,
Op vr 22 okt. 2021 23:18 schreef Bram Moolenaar :
>
>
> + def DoTest()
> + const Goo = G()
> + assert_equal(42, Foo)
> + enddef
> + DoTest()
> + END
>
Goo?
Christ van Willegen
>
--
--
You received this message from the
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
;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
+ INIT(= N_("E1211: List required for argument %d"));
> + EXTERN char e_bool_required_for_argument_nr[]
> + INIT(= N_("E1211: Bool required for argument %d"));
>
It's not a problem that these error numbers are the same?
Christ van Willegen
>
--
--
Y
(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"
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
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
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
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
.
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
({'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
> --- 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
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.
> +
)
> " 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 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
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
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 "
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
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
) && (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
"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
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
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
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 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?
*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
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
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
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
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.
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?
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
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
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
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
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
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
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 "
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,
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
*/
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
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
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
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
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
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
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
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
*/
! 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
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
> +#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
1 - 100 din 141 matches
Mail list logo
