[Top][All Lists]

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

[Groff-commit] groff ChangeLog doc/groff.texinfo

From: Werner LEMBERG
Subject: [Groff-commit] groff ChangeLog doc/groff.texinfo
Date: Wed, 18 Feb 2009 09:58:42 +0000

CVSROOT:        /cvsroot/groff
Module name:    groff
Changes by:     Werner LEMBERG <wl>     09/02/18 09:58:42

Modified files:
        .              : ChangeLog 
        doc            : groff.texinfo 

Log message:
        * doc/groff.texinfo: Improve documentation of `lsm' request.


Index: ChangeLog
RCS file: /cvsroot/groff/groff/ChangeLog,v
retrieving revision 1.1195
retrieving revision 1.1196
diff -u -b -r1.1195 -r1.1196
--- ChangeLog   14 Feb 2009 17:21:35 -0000      1.1195
+++ ChangeLog   18 Feb 2009 09:58:41 -0000      1.1196
@@ -1,3 +1,7 @@
+2009-09-18  Werner LEMBERG  <address@hidden>
+       * doc/groff.texinfo: Improve documentation of `lsm' request.
 2009-02-14  Werner LEMBERG  <address@hidden>
        Implement a leading spaces macro request, `lsm', in analogy to

Index: doc/groff.texinfo
RCS file: /cvsroot/groff/groff/doc/groff.texinfo,v
retrieving revision 1.282
retrieving revision 1.283
diff -u -b -r1.282 -r1.283
--- doc/groff.texinfo   14 Feb 2009 17:21:37 -0000      1.282
+++ doc/groff.texinfo   18 Feb 2009 09:58:42 -0000      1.283
@@ -12375,6 +12375,16 @@
 there was no leading space macro is stored in register @code{lss}.
 Note that @code{lsn} and @code{lss} are available even if no leading
 space macro has been set.
+The first thing a leading space macro sees is a token.  However, some
+escapes like @code{\f} or @code{\m} are handled on the fly (see
address@hidden Internals}, for a complete list) without creating a token
+at all.  Consider that a line starts with two spaces followed by
address@hidden  While skipping the spaces @code{\fI} is handled too so
+that groff's current font is properly set to @samp{I}, but the leading
+space macro only sees @code{foo}, without the preceding @code{\fI}.
+If the macro should see the font escape you have to `protect' it with
+something which creates a token, for example with @code{\&\fIfoo}.
 @c ---------------------------------------------------------------------

reply via email to

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