Patch 9.0.0044
Problem:    Typos in comments, wrapping lines.
Solution:   Adjust comments.  Wrap lines.
Files:      src/ex_docmd.c, src/getchar.c, src/message.c, src/search.c,
            src/textformat.c


*** ../vim-9.0.0043/src/ex_docmd.c      2022-07-02 13:43:17.947746835 +0100
--- src/ex_docmd.c      2022-07-03 11:44:34.419309971 +0100
***************
*** 3120,3126 ****
                // Special case: empty command uses "+":
                //  "'<,'>mods" -> "mods *+
                //  Use "*" instead of "'<,'>" to avoid the command getting
!               //  longer, in case is was allocated.
                mch_memmove(orig_cmd, cmd_start, len);
                STRCPY(orig_cmd + len, " *+");
            }
--- 3120,3126 ----
                // Special case: empty command uses "+":
                //  "'<,'>mods" -> "mods *+
                //  Use "*" instead of "'<,'>" to avoid the command getting
!               //  longer, in case it was allocated.
                mch_memmove(orig_cmd, cmd_start, len);
                STRCPY(orig_cmd + len, " *+");
            }
*** ../vim-9.0.0043/src/getchar.c       2022-07-02 12:08:12.813935667 +0100
--- src/getchar.c       2022-07-03 11:51:09.610670246 +0100
***************
*** 3020,3027 ****
  vgetorpeek(int advance)
  {
      int               c, c1;
!     int               timedout = FALSE;       // waited for more than 1 second
!                                       // for mapping to complete
      int               mapdepth = 0;           // check for recursive mapping
      int               mode_deleted = FALSE;   // set when mode has been 
deleted
  #ifdef FEAT_CMDL_INFO
--- 3020,3028 ----
  vgetorpeek(int advance)
  {
      int               c, c1;
!     int               timedout = FALSE;       // waited for more than 
'timeoutlen'
!                                       // for mapping to complete or
!                                       // 'ttimeoutlen' for complete key code
      int               mapdepth = 0;           // check for recursive mapping
      int               mode_deleted = FALSE;   // set when mode has been 
deleted
  #ifdef FEAT_CMDL_INFO
*** ../vim-9.0.0043/src/message.c       2022-06-29 21:16:53.641158372 +0100
--- src/message.c       2022-07-04 15:57:35.421274126 +0100
***************
*** 1883,1889 ****
                --trail;
        }
        // find end of leading whitespace
!       if (curwin->w_lcs_chars.lead || curwin->w_lcs_chars.leadmultispace != 
NULL)
        {
            lead = s;
            while (VIM_ISWHITE(lead[0]))
--- 1883,1890 ----
                --trail;
        }
        // find end of leading whitespace
!       if (curwin->w_lcs_chars.lead
!                                || curwin->w_lcs_chars.leadmultispace != NULL)
        {
            lead = s;
            while (VIM_ISWHITE(lead[0]))
*** ../vim-9.0.0043/src/search.c        2022-06-17 18:19:20.000000000 +0100
--- src/search.c        2022-06-30 21:36:01.688866559 +0100
***************
*** 2059,2065 ****
   * "oap" is only used to set oap->motion_type for a linewise motion, it can be
   * NULL
   */
- 
      pos_T *
  findmatchlimit(
      oparg_T   *oap,
--- 2059,2064 ----
*** ../vim-9.0.0043/src/textformat.c    2022-05-24 13:55:19.000000000 +0100
--- src/textformat.c    2022-06-30 21:00:28.698025823 +0100
***************
*** 92,98 ****
        int     did_do_comment = FALSE;
  
        virtcol = get_nolist_virtcol()
!               + char2cells(c != NUL ? c : gchar_cursor());
        if (virtcol <= (colnr_T)textwidth)
            break;
  
--- 92,98 ----
        int     did_do_comment = FALSE;
  
        virtcol = get_nolist_virtcol()
!                                  + char2cells(c != NUL ? c : gchar_cursor());
        if (virtcol <= (colnr_T)textwidth)
            break;
  
*** ../vim-9.0.0043/src/version.c       2022-07-06 12:57:27.964846666 +0100
--- src/version.c       2022-07-06 13:30:47.836926730 +0100
***************
*** 737,738 ****
--- 737,740 ----
  {   /* Add new patch number below this line */
+ /**/
+     44,
  /**/

-- 
Q: Should I clean my house or work on Vim?
A: Whatever contains more bugs.

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \\\
///                                                                      \\\
\\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

-- 
-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20220706123209.65A5D1C06D7%40moolenaar.net.

Raspunde prin e-mail lui