bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #61019] [me] using PS and n1 together produces a lot of diagnostic


From: G. Branden Robinson
Subject: [bug #61019] [me] using PS and n1 together produces a lot of diagnostic noise
Date: Sun, 8 Aug 2021 06:02:49 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Update of bug #61019 (project groff):

                  Status:             In Progress => Fixed                  
             Open/Closed:                    Open => Closed                 
         Planned Release:                    None => 1.23.0                 

    _______________________________________________________

Follow-up Comment #3:


commit 155540306593ac4c81bb3a3fcc04793f44be8541
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sun Aug 8 01:58:43 2021 +1000

    [me]: Fix PS/n1 combination diagnostic spew.

    * tmac/e.tmac (@h): Place comment escape sequence immediately after
      macro argument.  (When redefining a request, one needs to remember
      that request arguments are not parsed exactly as macro arguments are.)
      (n2): Prefix with `do` requests using long register names.
      (n2): Add macro-local register `|l` to store length of first argument.
      Don't attempt to extract a substring beyond its bounds, which produces
      a warning diagnostic.
      (&&): Define no-op macro for use as end macro in nested macro
      definition.
      (PS): Fix unbalanced-else diagnostic by changing `if` to `ie`.
      (PS): Initialize `PS_nm_cnt` register to 0 instead of relying on
      implicit definition.
      (PS): Prefix with `do` definition of long macro name.
      (PS): Indent call of end macro.
      (PS): Add comment after escaped space.
      (PS, PF): Prefix with `do` call of long macro name.

    Fixes <https://savannah.gnu.org/bugs/?61019>.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61019>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]