texinfo-commits
[Top][All Lists]
Advanced

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

[5964] linemac macro/newline example became wrong


From: karl
Subject: [5964] linemac macro/newline example became wrong
Date: Sun, 14 Dec 2014 18:07:23 +0000

Revision: 5964
          http://svn.sv.gnu.org/viewvc/?view=rev&root=texinfo&revision=5964
Author:   karl
Date:     2014-12-14 18:07:22 +0000 (Sun, 14 Dec 2014)
Log Message:
-----------
linemac macro/newline example became wrong

Modified Paths:
--------------
    trunk/ChangeLog
    trunk/doc/texinfo.texi

Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog     2014-12-14 17:36:49 UTC (rev 5963)
+++ trunk/ChangeLog     2014-12-14 18:07:22 UTC (rev 5964)
@@ -1,3 +1,9 @@
+2014-12-14  Karl Berry  <address@hidden>
+
+       * doc/texinfo.texi (Macro Details): the linemac example became
+       wrong at some point; just have to be vague, it seems.
+       Report from Gavin.
+
 2014-12-13  Gavin Smith  <address@hidden>
 
        * doc/texinfo.texi (Info Format Regular Nodes)
@@ -6,6 +12,9 @@
 
 2014-12-03  Karl Berry  <address@hidden>
 
+       * doc/texinfo.tex: oops, \relax not \thisisundefined for
+       \ifx\csname
+
        * texindex.tex (\U): new command @U.
        (\DeclareUnicodeCharacter): define a cs for @U to use.
        (\globalllet): helper macros.

Modified: trunk/doc/texinfo.texi
===================================================================
--- trunk/doc/texinfo.texi      2014-12-14 17:36:49 UTC (rev 5963)
+++ trunk/doc/texinfo.texi      2014-12-14 18:07:22 UTC (rev 5964)
@@ -15343,28 +15343,10 @@
 In general, the interaction of newlines in the macro definitions and
 invocations depends on the precise commands and context,
 notwithstanding the previous statements.  You may be able to work
-around some problems with judicious use of @code{@@c}.  Suppose you
-define a macro that is always used on a line by itself:
+around some problems with judicious use of @code{@@c} to ``comment
+out'' a newline, but @code{@@c} will cause problems in other cases.
+We are unable to make any general statements.
 
address@hidden
-@@macro linemac
-@@cindex whatever @@c
-@@end macro
-...
-foo
-@@linemac
-bar
address@hidden example
-
-Without the @code{@@c}, there will be a unwanted blank line between
-the @samp{@@cindex whatever} and the @samp{bar} (one newline comes
-from the macro definition, one from after the invocation), causing an
-unwanted paragraph break.
-
-On the other hand, you wouldn't want the @code{@@c} if the macro was
-sometimes invoked in the middle of a line (the text after the
-invocation would be treated as a comment).
-
 @item
 In general, you can't arbitrarily substitute a macro (or
 @code{@@value}) call for Texinfo command arguments, even when the text




reply via email to

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