[patch] usr_toc.txt missing subchapter heading
Hi folks, Bram! It seems usr_toc.txt wasn't updated accordingly when the new subchapter on defaults.vim file explained was introduced in usr_05. Appended patch fixes this. Florian --- vim/runtime/doc/usr_toc.txt 2019-01-31 20:07:23.345453525 +0100 +++ vim.patched/runtime/doc/usr_toc.txt 2019-05-23 22:31:14.647649308 +0200 @@ -103,12 +103,13 @@ |usr_05.txt| Set your settings |05.1| The vimrc file |05.2| The example vimrc file explained - |05.3| Simple mappings - |05.4| Adding a package - |05.5| Adding a plugin - |05.6| Adding a help file - |05.7| The option window - |05.8| Often used options + |05.3| The defaults.vim file explained + |05.4| Simple mappings + |05.5| Adding a package + |05.6| Adding a plugin + |05.7| Adding a help file + |05.8| The option window + |05.9| Often used options |usr_06.txt| Using syntax highlighting |06.1| Switching it on -- -- 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/190523-203421%40tin.fm-r.eu. For more options, visit https://groups.google.com/d/optout.
[patch][man][de] vim.1 translated to German
Hi, o Elias Diem pub.li...@webconect.ch: On 2012-06-17 Florian Rehnisch wrote: I would be gratituded if some german fellow could comment it. Here's a patch of what I think should be changed. Feel free to apply it. Done. Thanks. Thanks also to Dominik for pointing to LanguageTool. Bram, I think it's ready to include. Find it at http://xdff.de/vim-man/ (*-de.1 and *-de.UTF-8 as usual). flori -- 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
Re: [man][de][rfr] vim.1 translated to German, please review
o tux. z...@tuxproject.de: Florian Rehnisch schrob am 17. Jun. 2012 um 2:38 Zeit: I would be gratituded if some german fellow could comment it. Some punctuation is missing and some grammar is a bit incorrect. New vs Old Spelling issues? hmmm :/ How can I patch that from Windows? patch? diff? kdiff.sf.net or GNU diffutils gnuwin32.sf.net/packages/diffutils.html but I don't fly MSW. flori -- 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
Re: [man][de][rfr] vim.1 translated to German, please review
o tux. z...@tuxproject.de: Some general things though: 1) Use German quote signs. These » « are French. Done in UTF-8 copy, stuck with guillemets in latin1 copy. Remaning issues all done. Thanks. flori -- 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
Re: [man][de][rfr] vim.1 translated to German, please review
o Florian Rehnisch f...@gmx.de: Remaning issues all done. Thanks. s/Remaning/Remaining/ And Vim has such a nice spell checker ... flori -- 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
[man][de][rfr] vim.1 translated to German, please review
Moin, some years ago I was sent a translation of vim.1 to German. Now I finally did the effort to bring it in good shape. I would be gratituded if some german fellow could comment it. Find it at http://xdff.de/vim-man/ (*-de.1 and *-de.UTF-8 as usual, *.biling is a two lang version for easier review). Thanks, flori -- 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
Re: help.txt: ft_sql.txt missing
o Bram Moolenaar b...@moolenaar.net: Florian Rehnisch wrote: I wonder if noone noticed yet that ft_sql.txt is missing from the overview list in help.txt. Could be after ft_ada.txt. You must be using a slightly old version, the line is there now. Seems like I need enlightenment. I don't find it in my carefull patched 7.2 release nor in http://vim.svn.sourceforge.net/viewvc/vim/vim7/runtime/doc/help.txt?revision=1626view=markup. Where else doI have to look? Thanks, flori -- --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: help.txt: ft_sql.txt missing
o James Vega james...@jamessan.com: On Thu, Oct 8, 2009 at 10:06, Florian Rehnisch eix...@gmx.de wrote: o Bram Moolenaar b...@moolenaar.net: Florian Rehnisch wrote: I wonder if noone noticed yet that ft_sql.txt is missing from the overview list in help.txt. Could be after ft_ada.txt. You must be using a slightly old version, the line is there now. Seems like I need enlightenment. I don't find it in my carefull patched 7.2 release nor in [cvs] Where else doI have to look? Thanks, Runtime file updates are done out of band from patch updates (which is what the svn and cvs repositories track). See http://www.vim.org/runtime.php. Ah, thanks for enlightenment, and thanks for fixing. flori -- --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
help.txt: ft_sql.txt missing
Hi Bram, folks. I wonder if noone noticed yet that ft_sql.txt is missing from the overview list in help.txt. Could be after ft_ada.txt. flori --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: usr_4[34].txt cosmetics
o Matt Wozniski m...@drexel.edu: On Fri, Dec 26, 2008 at 6:49 AM, Florian Rehnisch wrote: Hi folks, it is said, that translators are the best profreaders. ;-) Ah well, sorry for that. I'm non-native ... # type: Plain text #: usr_43.txt:61 # FIXME: ticks around maplocalleader, not dquotes, for it's an option msgid Likewise, the mapping for \\\c\ will disappear when editing another buffer. The \:map buffer\ command creates a mapping that is local to the current buffer. This works with any mapping command: \:map!\, \:vmap\, etc. The |LocalLeader| in the mapping is replaced with the value of \maplocalleader\. I disagree with this - maplocalleader isn't an option, it's a variable. 'options' should be quoted in the vim help, and variables should be double quoted. Ah, I see. Learning by errors. So why not state it's a variable, like this: #v+ --- usr_43.txt 2008-08-11 21:35:03.0 +0200 +++ eix/usr_43.txt 2008-12-28 12:23:59.0 +0100 @@ -57,7 +57,8 @@ Likewise, the mapping for \c will disappear when editing another buffer. The :map buffer command creates a mapping that is local to the current buffer. This works with any mapping command: :map!, :vmap, etc. The -|LocalLeader| in the mapping is replaced with the value of maplocalleader. +|LocalLeader| in the mapping is replaced with the value of the variable +maplocalleader. You can find examples for filetype plugins in this directory: #v- flori -- http://www.florianrehnisch.de/vimhelp/ --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
usr_4[34].txt cosmetics
Hi folks, it is said, that translators are the best profreaders. Sometimes, I make annotations. Let's see what I have: # type: Plain text #: usr_43.txt:61 # FIXME: ticks around maplocalleader, not dquotes, for it's an option msgid Likewise, the mapping for \\\c\ will disappear when editing another buffer. The \:map buffer\ command creates a mapping that is local to the current buffer. This works with any mapping command: \:map!\, \:vmap\, etc. The |LocalLeader| in the mapping is replaced with the value of \maplocalleader\. # type: Plain text #: usr_44.txt:501 #, no-wrap # FIXME shouldn't that be C++ syntax msgid The \:runtime!\ command searches 'runtimepath' for all \syntax/c.vim\ files.\n This makes the C syntax be defined like for C files. If you have replaced this one the\n c.vim syntax file, or added items with an extra file, these will be loaded as\n well.\n After loading the C syntax items the specific C++ items can be defined.\n For example, add keywords that are not used in C: \n # type: Plain text #: usr_44.txt:513 #, no-wrap # FIXME s,It,A script, msgid Now consider the Perl language. It consists of two distinct parts: a\n documentation section in POD format, and a program written in Perl itself.\n The POD section starts with \=head\ and ends with \=cut\.\n You want to define the POD syntax in one file, and use it from the Perl\n syntax file. The \:syntax include\ command reads in a syntax file and stores\n the elements it defined in a syntax cluster. For Perl, the statements are as\n follows: \n # type: Plain text #: usr_44.txt:668 # FIXME comma after b:current_syntax msgid Choose a good, descriptive name for your syntax file. Use lowercase letters and digits. Don't make it too long, it is used in many places: The name of the syntax file \name.vim\, 'filetype', b:current_syntax the start of each syntax group (nameType, nameStatement, nameString, etc). Thanks and merry christmas, flori -- vimhelp-de: http://www.florianrehnisch.de/vimhelp/ --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
ft_sql.txt not mentioned in help.txt
Moin, I wounder why noone noticed before: ft_sql.txt is not mentioned in help.txt. Already reported to Bram. BTW: I noticed this, while I updated vimhelp-de to the 72 release. As usual available from http://www.florianrehnisch.de/vimhelp/. Now in ZIP format as well. Thanks, flori --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
