Re: BUG: 2dd does not delete on last line
Ik ben het met je eens, Bram, je schreef op 2013-07-16 17:21: Maybe it's a bug that when you tell Vim to delete lines that don't exist it doesn't beep and do nothing. But it's always been that way and there is no reason why it's more of a problem now then 10 years ago. So let's just leave it. Je kunt inderdaad geen regels weggooien die er niet zijn en zo is het altijd geweest. Groetjes, Adri -- -- 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 vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: patch 7.1.040
Just my 2 eurocents. :)
On Thu, Jul 26, 2007 at 20:56:54 +, Bram Moolenaar wrote:
[ --- runtime/doc/eval.txt Wed Jul 25 21:05:56 2007 ]
! matchdelete({id}) *matchdelete()* *E802* *E803*
! Deletes a match with ID {id} previously defined by |matchadd()|
! or one of the |:match| commands. Returns 0 if succesfull,
^^
successful
! setmatches({list}) *setmatches()*
! Restores a list of matches saved by |getmatches()|. Returns 0
! if succesfull, otherwise -1. All current matches are cleared
^^
successful
[ --- runtime/doc/pattern.txt Tue Jul 24 15:47:01 2007 ]
! Also see |matcharg()|and |getmatches()|. The former returns
^^
| a
! matches (aside from |:match|, |:2match| and |:3match|are
^^
| a
Adri
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Re: patch 7.1.068
On Sun, Aug 12, 2007 at 14:55:48 +, Bram Moolenaar wrote: Patch 7.1.068 --- runtime/doc/options.txt Sat Aug 11 17:25:38 2007 ! 4. one of the other windows are wider than the current or new !window. Should be: ...one of the other windows is wider... ^^ Adri --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Bug with )
An easy way to reproduce this bug: $ echo y y $ vim -u NONE y y 1 line, 2 characters Then type ) and the cursor moves one position to the right, although there's nothing there! Vim 7.1 - Included patches: 1-2, 4-6, 8-12 - on Fedora 7. Adri --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Patch for Unix filename expansion to try out
On Fri, Jan 04, 2008 at 12:17:42 +, Bram Moolenaar wrote: A couple of problems were detected when the Unix shell is used to expand file names containing characters such as a single quote. This applies to completion on the command line and glob(). I made a patch that defines a function to echo each file name separately. Inspired by a patch that Dasn made, but staying on the safe side. The patch for ex_docmd.c changes detecting the end of the file name when doing command line completion. This specifically fixes a file name containing . Please try it out and let me know if there are any new problems. I tried it out and found a problem. This is my directory structure: a'b/ DS=70 DS 70 DS=D66 + S70 There is a directory a'b and it contains three files. The first filename (DS=70) doesn't contain any spaces, the other two do. Now I start Vim. At first, I'm inputting :n a followed by a TAB. The screen will display :n a\'b/, which is correct. Then I type a TAB again and again and again. $ vim :n aTAB :n a\'b/ :n a\'b/TABTABTAB :n a\'b/DS=70 :n a\'b/DS=70 :n a\'b/DS=70 (Nothing happens, only one filename matches) :n a\'b/*6TAB (Nothing happens, no filename matches) :n a\'b/*6*0TAB (Nothing happens, no filename matches) :n a\'b/DS\ 7TAB (Nothing happens, no filename matches) :n a\'b/DS\TAB :n a\'b/DS\* Adri (Vim 7.1 + patches 1-200 plus Bram's Patch for Unix filename expansion) --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
tar: Read 5120 bytes from - (Re: Porting vim to Astlinux)
On Sun, Dec 16, 2007 at 01:54:08 +, Philip Prindeville wrote: bzcat /home/philipp/trunk/dl/vim-7.1.tar.bz2 | tar -C /home/philipp/trunk/build_i586 -xf - tar: Read 5120 bytes from - Any idea why (re: the short read on tar)? This is not a problem. Tar doesn't complain if you decompress the .bz2 file at first and then tar -xf the decompressed file (.tar). Tar doesn't know the size of the uncompressed file (yet) when it's still compressed because Tar is reading from stdin. Try this: (bzcat ~/.../.../vim-7.1.tar.bz2 ; dd bs=5120 if=/dev/zero count=1 ) | tar tvf - Does it help? Adri ᴠɪᴍ ⒎ ① --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Patch for Unix filename expansion to try out
On Tue, Jan 15, 2008 at 13:08:01 +, Tony Mechelynck wrote: Dasn wrote: On 14/01/08 21:49 +0100, Adri Verhoef wrote: Please try it out and let me know if there are any new problems. I tried it out and found a problem. This is my directory structure: a'b/ DS=70 DS 70 DS=D66 + S70 There is a directory a'b and it contains three files. The first filename (DS=70) doesn't contain any spaces, the other two do. Now I start Vim. At first, I'm inputting :n a followed by a TAB. The screen will display :n a\'b/, which is correct. Then I type a TAB again and again and again. $ vim :n aTAB :n a\'b/ :n a\'b/TABTABTAB :n a\'b/DS=70 :n a\'b/DS=70 :n a\'b/DS=70 (Nothing happens, only one filename matches) [snip] Adri (Vim 7.1 + patches 1-200 plus Bram's Patch for Unix filename expansion) I can't reproduce this with 1-229. Patch 223 has been released, have a try? There were two successive versions of Bram's patch in this thread (the second version replacing only part of the first), and both have been released since then. If Adri was using the first version, and it was corrected by the second one, that would explain it. Bram's Patch for Unix filename expansion is in fact patches 7.1.223 + 7.1.226. My shell is Bash on Fedora 7. (se sh=/bin/sh) -rwxr-xr-x 1 root root 801504 2007-11-26 16:03 /bin/bash lrwxrwxrwx 1 root root 4 2008-01-14 08:58 /bin/sh - bash Anyway, I tried reversing Bram's Patch for Unix filename expansion, then apply #223, yet it fails to see the filenames containing a space character. This time I tried this directory structure: b'c/file001 b'c/file 01 b'c/file 1 Three files, one with one space in its name, one with two spaces in its name (between 'e' and '1'). Typing: :n b\'c/*TABTAB or :n b\'c/TABTAB (without the asterisk) only shows one filename: file001 My next try was to put only one file in a directory called c'd, like so: $ mkdir c\'d $ touch c\'d/one\ space $ src/vim :n c\'d/TABTAB (This just beeps at me. No filename matching.) One other try then, without the apostrophe to ensure that we don't need a backslash at first (for locating the directory). $ mkdir de $ touch de/sp\ a\ ce $ src/vim :n de/*TABCR de/sp a ce 0L, 0C (Result: OK!) OK, then back to directory c'd which contains the filename one space. $ src/vim :n c\'d/* c'd/one 0L, 0C :arg [c'd/one] space So this is where something goes wrong, if anyone can follow me. With patches 7.1.0-200 + 7.1.223 + 7.1.226. Adri --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Patch for Unix filename expansion to try out
Well, I don't know what happened, but after one more batch of tests suddenly everything seems to work that was earlier reported as bad. One thing that was strange though: Vim reported to have patch #215 installed twice, while I can't remember I downloaded that one even once. :-| Everyone, I'll promise to find another case that doesn't work next time! :-) Thanks for anticipating, Adri --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Weird font issue
On Fri, Dec 21, 2007 at 15:36:03 +, Jeff Lanzarotta wrote:
Thanks.
I was messing around with my vimrc file and inadvertently added 'set
digraph'...
I have now turned that feature off...
James Vega [EMAIL PROTECTED] wrote: On Fri, Dec 21, 2007 at 06:12:24AM
-0800, Jeff Lanzarotta wrote:
When I am in insert mode and I do:
'a' then backspace, 'a' then backspace, 'a' then backspace, repeatively,
the character 'a' is replaced with 'å'.
This is happening because you have the 'digraph' option enabled. When
this option is enabled, you can input unicode characters by typing
{char1} {char2} instead of using {char1}{char2}. This is
described at :help 'digraphs'.
James
--
Jeff Lanzarotta, your quoting mechanism cripples the text portion of the
message that you quoted. It said: {char1} BS {char2} instead of ...
and now it reads {char1} {char2} instead of
Adri
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
spend vs. spent
I saw the word spend being used and wondered why it wasn't being spelled as spent. I decided to grep both words in all '.c' files I could find. Here is a sample of the result: $ find|grep \\.c$|xargs grep [^u]spend ./src/eval.c:proftime_T uf_tm_total;/* time spend in function + children */ ./src/eval.c:proftime_T uf_tm_self; /* time spend in function itself */ ./src/eval.c:proftime_T *uf_tml_total; /* time spend in a line + children */ ./src/eval.c:proftime_T *uf_tml_self; /* time spend in a line itself */ ./src/ex_cmds2.c:proftime_T sn_pr_total;/* time spend in script + children */ ./src/ex_cmds2.c:proftime_T sn_pr_self; /* time spend in script itself */ ./src/ex_cmds2.c:proftime_T sn_prl_total; /* time spend in a line + children */ ./src/ex_cmds2.c:proftime_T sn_prl_self;/* time spend in a line itself */ ./src/ex_cmds2.c: /* Grow the array before starting the timer, so that the time spend $ find|grep \\.c$|xargs grep spent ./src/eval.c:proftime_T uf_tm_children; /* time spent in children this call */ ./src/eval.c:proftime_T uf_tml_children; /* time spent in children for this line */ ./src/eval.c:proftime_T prof_child; /* time spent in a child */ ./src/eval.c: * Take care of time spent in a child. ./src/ex_cmds2.c:proftime_T sn_prl_children; /* time spent in children for this line */ ./src/ex_cmds2.c: * Count time spent in children after invoking another script or function. ./src/syntax.c: * To reduce the time spent in keepend(), remember at which level in the state IMO it is: To spend - spending - spent It's not in a real bug in the program source, but ... Adri --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: [Alpha/Gcc] compiler warning for Vim 7.1.230
On Fri, Jan 18, 2008 at 13:29:51 +0100, Bram Moolenaar wrote: Adri Verhoef wrote: Compilation of Vim 7.1.230 on an Alpha processor with Gcc yielded: gui_motif.c: In function 'find_replace_dialog_create': gui_motif.c:3816: warning: cast to pointer from integer of different size That line would be: XtAddCallback(frdp-find, XmNactivateCallback, find_replace_callback, (XtPointer) (do_replace ? FRD_R_FINDNEXT : FRD_FINDNEXT)); I don't see how this is different from similar calls, e.g.: XtAddCallback(frdp-replace, XmNactivateCallback, find_replace_callback, (XtPointer)FRD_REPLACE); Perhaps you can try out what would silence the compiler? Here is the solution: XtAddCallback(frdp-find, XmNactivateCallback, find_replace_callback, (do_replace ? (XtPointer)FRD_R_FINDNEXT : (XtPointer)FRD_FINDNEXT)); Cheers, Adri --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
To be fixed in Vim's documentation
In autocmd.txt: Search for 'the commands,'. When executing the commands, the messages from one command overwrites a 'the messages' doesn't correspond to 'overwrites', presumably the 's' in 'overwrites' should be removed (assumption is based on the third line of text below current one: 'When one command outputs two messages this can happen anyway.'). === In syntax.txt: :g/Borne/p This covers the normal Unix (Borne) sh, bash and the Korn shell. sh: (default) Borne shell the Borne shell syntax. No need to quote RFCs or market penetration I think 'Borne' should be 'Bourne'. === :h helpgrep snip Compressed help files will not be searched (Debian compresses the help files). Compression is also used in Fedora. The only uncompressed .txt file is 'help.txt'. $ rpm -qa vim\* vim-enhanced-7.1.245-1.fc7 vim-common-7.1.245-1.fc7 vim-X11-7.1.245-1.fc7 vim-minimal-7.1.245-1.fc7 Fedora uses RPM for management of its software packages. According to Wikipedia, Debian uses APT: Prominent features of Debian are its package management system (especially APT) (see http://en.wikipedia.org/wiki/Debian). Adri --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Some more things to be fixed in Vim's documentation
:h tex-package In syntax.txt, next line: Wish To Highlight More Commmands? ~ 'Commmands' should be 'Commands'. === In usr_45.txt: URL http://www.microsoft.com/typography/fontpack/default.htm doesn't work, maybe http://www.microsoft.com/typography/fonts/default.aspx is a good alternative? * Adri * --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: To be fixed in Vim's documentation
On Wed, Apr 30, 2008 at 18:16:33 +, Bram Moolenaar wrote: James Vega wrote: On Sat, Apr 26, 2008 at 01:07:39PM +0200, Adri Verhoef wrote: :h helpgrep snip Compressed help files will not be searched (Debian compresses the help files). Compression is also used in Fedora. The only uncompressed .txt file is 'help.txt'. Compressed help files are no longer used in Debian for the Vim packages. It looks like some of the packages for Vim scripts still do though. OK, so then the sentence should be: Fedora compresses the help files. Right, Bram. Adri --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
UTF-8 bomb showing up after :%!sort
I have this textfile that contains three lines: 3 2 1 Now do: :se fileencoding=utf8 bomb :%!sort Result: 1 2 feff3 Now do: :w newfile newfile [New] 3L, 12C written :w !od -c 000 357 273 277 1 \n 2 \n 357 273 277 3 \n 014 I think there is a problem here, namely that the BOM (Byte Order Mark, see :help 'bomb') is transferred to the shell command, when it shouldn't. In my opinion Vim should be able to temporarily remove the BOM, then execute the shell command, and finally place the BOM back at its original place, at the beginning of the file. Background: a colleague of mine received a file from abroad (with afterwards what appeared to be a BOM) and while editing the file, he sorted the file (:%!sort) and noticed some strange characters at the end of the file. Since his terminal can't handle UTF-8, he saw these three characters in Latin-1: ï » ¿ (in octal: \357 \273 \277). Trying to remove them, he typed xxx, then wrote the file and quit Vim. Then he started Vim again, did some more editing and sorted the file again and saw - again - those three strange characters, erased them again and sorted again and there they were *again*! It puzzled me for a while, too, until I adviced him to try setting 'fileencoding' to latin1. This helped, but only later I figured out what had happened. What do you think? Adri --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Update of netbeans help file
On Mon, May 26, 2008 at 15:05:40 +, Philippe Fremy wrote: 4. Error Messages *netbeans-messages* Those error messages are specific to NetBeans socket protocol: ^ These? Read-only file [] So Vim does not allow modifications to files when run with in NetBeans mode. run within? 6. NetBeans protocol *netbeans-protocol* [] see http://www.a-a-p.org) and other IDE. The extensions are marked with the other IDE? another IDE? other IDEs? NetBeans users (ie, not Agide users). However, a bug was fixed which could i.e.? seqno The IDE uses a sequence number for Commands and Functions. A Reply must use the sequence number of the Function that it is associated with. with which it is associated.? Adri --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: [patch] fixed typos in help files
On Wed, Jun 25, 2008 at 20:26:59 +, Dominique Pelle wrote: *** version7.txt 24 Jun 2008 22:33:14 - 1.217 --- version7.txt 25 Jun 2008 20:11:22 - *** *** 263,269 Ruby|ft-ruby-omni| SQL |ft-sql-omni| XML |ft-xml-omni| ! any language wih syntax highligting |ft-syntax-omni| You can add your own omni completion scripts. --- 263,269 Ruby|ft-ruby-omni| SQL |ft-sql-omni| XML |ft-xml-omni| ! any language with syntax highligting|ft-syntax-omni| Also notice that it should be 'highlighting'. Cheers, Adri --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Documentation error
In eval.txt (vim 8.0.1842), line 5423, job_start() is documented. On the 13th line underneath it there is this text: On MS-Windows, job_start() makes a GUI application hidden. If want to show it, Use :!start instead. Perhaps it should be "If you want" and "use"? -- -- 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 "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Typo(s) in channel.txt
Originally, I reported this back in 2018. Since then, the documentation for job_start() moved from eval.txt to channel.txt and the text that I'm describing is still there. In the documentation for job_start() it shows: On MS-Windows, job_start() makes a GUI application hidden. If want to show it, Use |:!start| instead. Perhaps the last line should read: you want to show it, use |:!start| instead. [inserting the word 'you' and changing 'Use' into 'use'] Adri -- -- 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 "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/b2d91e4b-817b-dd62-3753-2a68dae46b35%40a3.xs4all.nl.
Re: Documentation error
I found this older message; the issue hasn't been resolved because the text has been moved from eval.txt to the file channel.txt (as part of the package vim-common-9.0.1677-2.fc38.x86_64). See issue below. > Op 17-05-2018 20:08 CEST schreef Bram Moolenaar : > > > Adri Verhoef wrote: > > > In eval.txt (vim 8.0.1842), line 5423, job_start() is documented. On > > the 13th > > line underneath it there is this text: > > > > On MS-Windows, job_start() makes a GUI application > > hidden. If > > want to show it, Use :!start instead. > > > > Perhaps it should be "If you want" and "use"? > > Yes, I'll correct it. > > -- > Why is "abbreviation" such a long word? > > /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ > ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ > \\\ an exciting new programming language -- http://www.Zimbu.org/// > \\\help me help AIDS victims -- http://ICCF-Holland.org/// "want to show it, Use :!start instead." is now on line 959. Adri -- -- 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 "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/1477030968.479533.1692006412437%40kpc.webmail.kpnmail.nl.
Re: Farewell to Bram and dedicate upcoming Vim 9.1 to him (#12749)
> Op 13-08-2023 10:45 CEST schreef Christian Brabandt :
[..]
> diff --git a/runtime/doc/intro.txt b/runtime/doc/intro.txt
[..]
> @@ -216,7 +217,7 @@ Vim would never have become what it is now, without the
> help of these people!
> Bill Foster Athena GUI port (later removed)
> Google Lets me work on Vim one day a week
I noticed this: "Lets me work". Bram worked for Google for 15 years, until
September 2021.
Shouldn't this "Lets me" be past tense then, like "Let Bram"? Alternatively:
"Letting Bram".
> diff --git a/LICENSE b/LICENSE
[..]
> @@ -21,8 +21,8 @@ II) It is allowed to distribute a modified (or extended)
> version of Vim,
>maintainer will do with your changes and under what license they
>will be distributed is negotiable. If there has been no
> negotiation
>then this license, or a later version, also applies to your
> changes.
> - The current maintainer is Bram Moolenaar . If this
> - changes it will be announced in appropriate places (most likely
> + The current maintainers are listed here:
> https://github.com/orgs/vim/people.
> + If this changes it will be announced in appropriate places (most
> likely
>vim.sf.net, www.vim.org and/or comp.editors). When it is completely
>impossible to contact the maintainer, the obligation to send him
>your changes ceases. Once the maintainer has confirmed that he has
Above it says: "The current maintainers are listed".
As we can see, that's plural. Let's watch out for the word "maintainer" then.
Let's also have another look at the lines above.
"It is allowed to distribute a modified (or extended) version of Vim",
that's singular ("version of Vim"). Then the next lines: "maintainer will do
with your changes and under what license they will be distributed is
negotiable".
I think this can be split into two parts: the part where the changes are
mentioned
and the part where the license of the version is discussed. 'The changes'
might be plural, but 'the version' is singular. So shouldn't this be "the
maintainers will do with your changes and under what license that version"
(trying to avoid the word 'it' or 'they' after "under what license") then?
Possibly, the following lines:
"impossible to contact the maintainer, the obligation to send him
your changes ceases. Once the maintainer has confirmed that he has"
should then be changed into:
"impossible to contact the maintainers, the obligation to send them
your changes ceases. Once the maintainers have confirmed that they have"
There are more locations where "maintainer" is mentioned. Should I list them?
The same text appears in file uganda.txt:
> diff --git a/runtime/doc/uganda.txt b/runtime/doc/uganda.txt
[..]
> @@ -46,8 +46,8 @@ II) It is allowed to distribute a modified (or extended)
> version of Vim,
> maintainer will do with your changes and under what license they
> will be distributed is negotiable. If there has been no negotiation
> then this license, or a later version, also applies to your changes.
> - The current maintainer is Bram Moolenaar . If this
> - changes it will be announced in appropriate places (most likely
> + The current maintainers are listed here:
> https://github.com/orgs/vim/people.
> + If this changes it will be announced in appropriate places (most
> likely
> vim.sf.net, www.vim.org and/or comp.editors). When it is completely
> impossible to contact the maintainer, the obligation to send him
> your changes ceases. Once the maintainer has confirmed that he has
So the same remarks apply. :-)
This wasn't changed yet:
> diff --git a/runtime/indent/README.txt b/runtime/indent/README.txt
[..]
> If you have remarks about an existing file, send them to the maintainer of
> that file. Only when you get no response send a message to b...@vim.org.
That should possibly be changed into:
"get no response send a message to the vim-dev mailing list ."
The word "me" is also 'suspect':
> diff --git a/runtime/syntax/model.vim b/runtime/syntax/model.vim
[..]
> -" Maintainer:Bram Moolenaar
> -" Last Change: 2005 Jun 20
> +" Maintainer:The Vim Project
> +" Last Change: 2023 Aug 10
> +" Former Maintainer: Bram Moolenaar
>
> " very basic things only (based on the vgrindefs file).
> " If you use this language, please improve it, and send me the patches!
Maybe change "me" into "us"?
> diff --git a/src/po/README.txt b/src/po/README.txt
[..]
> You should include your name and E-mail address instead, for example:
Shouldn't this just be "e-mail" instead of "E-mail"?
The same applies here:
> diff --git a/src/po/README_mingw.txt b/src/po/README_mingw.txt
[..]
> You should include your name and E-mail address instead, for example:
Adri
PS Great that you've taken up the project!
