Hi Bram and list, 2018-7-8(Sun) 23:51:22 UTC+9 Bram Moolenaar: > Tony wrote: > > > > > Hm, it seems that Bram writes "gvim" but "GvimExt" almost everywhere, > > > but that the author of the CSApprox plugin consistently uses "GVim" — > > > see quickfix list below. > > > > > > This said, with Vim there usually isn't "only one way" of doing > > > things, there often are several key sequences that give the same > > > result, and as long as the text is clear I wouldn't be paranoid about > > > which letter to write in uppercase — except in code examples, where > > > case consistency is usually required (a variable named fooBar is not > > > the same as Foobar or FooBar or foobar or FOOBAR or, of course, > > > foo_bar). In code, and e.g. in examples of command-lines to invoke the > > > program, the Vim executable name must be in all lowercase, i.e. vim, > > > view, vimdiff, gvim, gview, etc. > > > > The executables are always lower case, that's clear. > > > > Since Vim is a name, a product name, it starts with a capital. > > > > In some cases VIM is used, but that should be an exception. > > > > Now for GUI Vim, how to write it in normal text? I would say that Vim is > > the strongest part of the name, and prepending "g" is for the GUI > > variant. Thus gVim would be preferred. > > > > If you think that every name should start with a capital, then you end > > up with GVim. But two capitals is a bit strange, I would only use that > > at the start of a sentence. Also, Gvim is strange, since it is dropping > > the capital from Vim. There is one exception: We are using GvimExt as a > > directory name. Changing that would be a hassle, so let's keep it. > > > > I also think that gVim looks better.
Are you sure? You are making the following remarks in 2017-05-30. https://groups.google.com/d/msg/vim_dev/a0CkwXDiQDg/8nWORUIlAAAJ > While "Vim" is a name, "gvim" is a command. Vim can also be a command, > thus then it's written as "vim". Depends on the context. > > I agree that "Gvim" and "gVim" are a bit strange. "GVim" is weird. > Just using "gvim" seems best. And the following patch is relevant. https://github.com/vim/vim/commit/6aa8cea46d4179b2617daae034063dd0d8054e35 I do not mind changing it, but I think that it is better to write the decision matter somewhere in github's README.md. -- Best regards, Hirohito Higashi (h_east) -- -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
