XPost: alt.comp.os.windows-10, alt.comp.software.thunderbird   
   From: confused@nospam.net   
      
   Frank Slootweg  wrote:   
   >   It's probably best to set a line length (textwidth in vim) and then set   
   > a wrapmargin from that line length, i.e.   
   >   
   >:set textwidth=80   
   >:set wrapmargin=8   
      
   There is also ":set whichwrap=b,s,<,>,[,]" which can be modified if needed.   
      
   >   So you have a textwidth of 80 characters, but the text starts wrapping   
   > at column 72.   
      
   Good idea.   
      
   >   You probably want to be able to reformat a section while you're   
   > composing/editing. Use   
   >   
   >:set fo=tcrq   
   >   
   >   Now you can select a section by Ctrl-V and moving the cursor down over   
   > as many lines of text as you want and then use 'gq' (without quotes) to   
   > reformat the selected lines within the given textwidth and wrapmargin.   
      
   Another good idea.   
      
   >   I *start* in vim, because it's a real editor unlike the Thunderbird's   
   > built-in composer, and then I copy-and-paste the text into Thunderbird's   
   > compose window. (I often do it via an intermediate copy from Notepad, so   
   > close vim, open the textfile in Notepad and copy-and-paste from Notepad   
   > to Thunderbird.)   
      
   That's what I do also, although I don't bother with the line lengths.   
   I just can't stand Thunderbird's composer windows being so non useful.   
      
   > Some way, mine is set to 72 characters, but I don't know where.   
      
   The rc files are confusingly all over the place for gvim I think.   
      
   If you run ":echo $VIM" it will give your the install directory.   
   If you run ":echo $HOME" it will tell you where your home dir is.   
   If you run ":echo $VIMRUNTIME" it will tell you the run directory.   
   If you run ":version" inside of gvim, you'll get these four locations.   
      
   1. System vimrc file   
   2. User vimrc file   
   3. 2nd user vimrc file   
   4. 3rd user vimrc file   
      
   I have no idea which of the first two wins in the end.   
   Nor did I even know about the latter two until just now.   
      
   Who is the 2nd and 3rd user?   
   Anyway, there are even more rc files that this command reported for me.   
   5. User exrc file   
   6. 2nd user exrc file   
   7. system gvimrc file   
   8. user gvimrc file   
   9. 2nd user gvimrc file   
   10. 3rd user gvimrc file   
   11. defaults file   
   12. system menu file   
      
   Out of those dozen files, which is the one whose settings win?   
   Only gvim knows for sure.   
      
   One way around that might be to source a known rc file inside of gvim.   
   Maybe something like ":source $VIMRUNTIME/tb.txt"   
      
   Where you can look at it with something like ":r $VIMRUNTIME/tb.txt"   
   And you can check that it worked with something like ":set"   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)