> "What is a PR?" and "How do I do it?"
He means 'pull request' in 'Github',
or actually you should be Ok to go with 'git patch' workflow as well;
just send your code patch mail to him. FYI. check ':h develop.txt'
--
shane.xb.qian
--
--
You received this message from the "vim_dev" maillist.
D
> Hi,
>
> I would argue that:
>
> - if (insert->length > 0)
> - {
> - // remove trailing ESC
> - --insert->length;
> - if (s[insert->length] == ESC)
> - s[insert->length] = NUL;
> - }
> + if (insert.length > 0 && s[insert.length - 1] == ESC) // remove trailing
> ESC
> + s[insert.length - 1] = NUL
On 25/01/08 08:44PM, Christian Brabandt wrote:
>
> On Wed, 08 Jan 2025, shane qian wrote:
>
> > Hi,
> > sorry cannot open google link here unfortunately.
> > what I means: a buffer cannot be created without a window existed and
> > displayed it in a popup, or if had, means that window had been
> Reported-by: Lifepillar
> Signed-off-by: Christian Brabandt
>
> popup_close({id} [, {result}]) *popup_close()*
> - Close popup {id}. The window and the associated buffer will
> - be deleted.
> + Close popup {id}. The w
sometime it happened such E254 err at my v9.1.698 (linux xfce-term
xterm-256color)
Error detected while processing ColorSchemePre Autocommands for "*":
E254: Cannot allocate color 235
```
hi clear difftext
hi difftext cterm=bold ctermbg=red ctermfg=235
au colorschemepr
> I think the easiest way to follow Vim Development from Github is, if you
> got to the Vim Repository page on Github https://github.com/vim/vim and
> you click on the little watch button. Then you receive notifications for
> all PRs, Issues and activities there in. Of course this requires to ha
> I follow Vim development activity through the vim_dev mailing list
> rather than at https://github.com/vim/vim/. That generally works
> well, except that I seem to miss the original postings of some
> issues and/or PRs. I see responses, but not the original postings,
> so I'm potentially missin
> Suddenly when opening a CSS file in Vim (or when opening an HTML file,
> because HTML syntax invokes CSS syntax), I see a huge lot of errors.
> This is at patchlevel 9.1.296 or earlier. I didn't see it a few days
> ago but I'm not sure at which changeset it appeared.
> >>>
>
> patch 9.1.0342: tests: test_taglist fails when 'helplang' contains non-english
>
> Commit:
> https://github.com/vim/vim/commit/ae7e61c928b4adaa220e59ecebc75ef630674207
> Author: Julio B
> Date: Tue Apr 16 22:55:04 2024 +0200
>
> patch 9.1.0342: tests: test_taglist fails when 'helplang'
> add runtime/doc/tags-* to ignore files
> (https://github.com/vim/vim/issues/14479)
>
> diff --git a/.gitignore b/.gitignore
> index 5275e..241e96eaf 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -96,6 +96,7 @@ src/kword_test
>
> # Generated by "make install"
> runtime/doc/doctag
On 24/04/10 03:15PM, shane.qian wrote:
> > > Suddenly when opening a CSS file in Vim (or when opening an HTML file,
> > > because HTML syntax invokes CSS syntax), I see a huge lot of errors.
> > > This is at patchlevel 9.1.296 or earlier. I didn't see it a few da
> > Suddenly when opening a CSS file in Vim (or when opening an HTML file,
> > because HTML syntax invokes CSS syntax), I see a huge lot of errors.
> > This is at patchlevel 9.1.296 or earlier. I didn't see it a few days
> > ago but I'm not sure at which changeset it appeared.
>
> Hm, may it be re
> The recently introduced matchbufline() and matchstrlist() functions
> use the 'ignorecase' option value. If this option is set, then these
> functions ignore the case when matching the strings.
> So the behavior of a plugin using these functions depends on a user
> configuration.
> To ignore thi
> runtime(misc): announce adoption of various runtime files
not sure what happened, but thank you Charles @cecamp
you are definitely a legacy of vim history too, lots of init/basic and
important vim plugins from your built.
seems you were leaving, for whatever reason, i will miss you.
--
shane.
On 24/02/14 08:04PM, shane.qian wrote:
> > Hi,
> > I was experimenting with setting up clangd and clang-format for the
> > codebase. I've read the `:h develop` but I still have missing information.
> >
> > 1. Tabs or spaces? The documentation doesn'
> Hi,
> I was experimenting with setting up clangd and clang-format for the
> codebase. I've read the `:h develop` but I still have missing information.
>
> 1. Tabs or spaces? The documentation doesn't specify it and the source
> files sometimes mix spaces and tabs.
> 2. What parts of C99 are su
> I hope this is the right place to ask a question to Vim maintainers. My
> question is about this post: https://github.com/vim/vim/issues/6445
not sure if it was right place, but i replied it in your ticket.
or anyway, please refer 'https://github.com/vim/vim/issues/8122'
i was struggle or try t
On 23/08/26 03:08PM, shane.qian wrote:
> > > If "public" is omitted, shouldn't class members and method be private by
> > > default just like "def" functions
> > > and script variables are script-local by default unless prefixed with
> >
> > If "public" is omitted, shouldn't class members and method be private by
> > default just like "def" functions
> > and script variables are script-local by default unless prefixed with
> > "export"?
> >
>
> Currently object/class methods are always public and the object/class
> private metho
On 23/08/24 08:18PM, Yegappan Lakshmanan wrote:
> Hi all,
>
> The following item is in the todo.txt file for implementing private
> methods in a class:
>
> - Private methods?
> either: private def Func()
> or: def _Func()
> Perhaps use "private" keyword instead of "_" pre
> If this is annoying and nobody uses it anyhow, I can stop it. Or I can
> start to use the prefix '^Commit:' in the patch messages.
could you also think if possible to reduce the general comments in github to
forward to vim_dev mailing list?
since there lots of mails actually dup between this
21 matches
Mail list logo
