Loading ...
Sorry, an error occurred while loading the content.

Re: Command history while debugging is gone

Expand Messages
  • Gregory Margo
    ... Is there some reason that :hist is not in the docs? Here s a patch against 6.3.10 that may need rewording regarding debug mode: ... *************** ***
    Message 1 of 7 , Jul 1, 2004
    • 0 Attachment
      On Wed, Jun 30, 2004 at 11:19:03PM +0200, Bram Moolenaar wrote:
      > debug mode history? Try ":hist >".


      Is there some reason that ":hist >" is not in the docs?
      Here's a patch against 6.3.10 that may need rewording regarding debug mode:

      *** runtime/doc/cmdline.txt.save 2004-06-07 02:05:17.000000000 -0700
      --- runtime/doc/cmdline.txt 2004-07-01 09:35:21.000000000 -0700
      ***************
      *** 45,56 ****

      *cmdline-history* *history*
      The command-lines that you enter are remembered in a history table. You can
      ! recall them with the up and down cursor keys. There are actually four
      history tables:
      - one for ':' commands
      - one for search strings
      - one for expressions
      ! - one for input lines, typed for the |input()| function.
      These are completely separate. Each history can only be accessed when
      entering the same type of line.
      Use the 'history' option to set the number of lines that are remembered
      --- 45,57 ----

      *cmdline-history* *history*
      The command-lines that you enter are remembered in a history table. You can
      ! recall them with the up and down cursor keys. There are actually five
      history tables:
      - one for ':' commands
      - one for search strings
      - one for expressions
      ! - one for input lines, typed for the |input()| function
      ! - one for debug mode.
      These are completely separate. Each history can only be accessed when
      entering the same type of line.
      Use the 'history' option to set the number of lines that are remembered
      ***************
      *** 305,310 ****
      --- 306,312 ----
      s[earch] or / search string history
      e[xpr] or = expression register history
      i[nput] or @ input line history
      + d[ebug] or > debug mode history
      a[ll] all of the above
      {not in Vi}



      --
      +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
      Gregory H. Margo
      Home: greg at margofamily dot org, gmargo at yahoo dot com or pacbell dot net
    • Bram Moolenaar
      ... Thanks. Strange that this was missing. -- ARTHUR: Listen, old crone! Unless you tell us where we can buy a shrubbery, my friend and I will ... we will
      Message 2 of 7 , Jul 1, 2004
      • 0 Attachment
        Gregory Margo wrote:

        > On Wed, Jun 30, 2004 at 11:19:03PM +0200, Bram Moolenaar wrote:
        > > debug mode history? Try ":hist >".
        >
        > Is there some reason that ":hist >" is not in the docs?
        > Here's a patch against 6.3.10 that may need rewording regarding debug
        > mode:

        Thanks. Strange that this was missing.

        --
        ARTHUR: Listen, old crone! Unless you tell us where we can buy a shrubbery,
        my friend and I will ... we will say "Ni!"
        CRONE: Do your worst!
        "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

        /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
        /// Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
        \\\ Project leader for A-A-P -- http://www.A-A-P.org ///
        \\\ Buy at Amazon and help AIDS victims -- http://ICCF.nl/click1.html ///
      Your message has been successfully submitted and would be delivered to recipients shortly.