All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Borislav Petkov <bp@alien8.de>
Cc: perfbook@vger.kernel.org
Subject: Re: perfbook build error
Date: Fri, 12 Dec 2014 08:38:35 -0800	[thread overview]
Message-ID: <20141212163835.GA29275@linux.vnet.ibm.com> (raw)
In-Reply-To: <20141211211429.GA23711@linux.vnet.ibm.com>

On Thu, Dec 11, 2014 at 01:14:29PM -0800, Paul E. McKenney wrote:
> On Thu, Dec 11, 2014 at 09:22:38PM +0100, Borislav Petkov wrote:
> > On Thu, Dec 11, 2014 at 12:10:14PM -0800, Paul E. McKenney wrote:
> > > > ! Illegal parameter number in definition of \Hy@tempa.
> > > > <to be read again> 
> > > >                    d
> > > > l.876 two \co{#define}
> > > >                        statements, giving us not one but two ways to create
> > > > ? 
> > > > ! Emergency stop.
> > > > <to be read again> 
> > > >                    d
> > > > l.876 two \co{#define}
> > > >                        statements, giving us not one but two ways to create
> > > > End of file on the terminal!
> > > > ---
> > > 
> > > That is odd given that URLs really can contain "#"...
> > 
> > I'm reading the error message like it has a problem with the "#" in
> > "#define" but I might be wrong.
> 
> Yep, that is my feeling as well.  And so \url{#define} would mean
> the name "define" in the current document.  Which admittedly would be
> more meaningful in an html document.

Does wrapping the \co{} in mbox help?  Please see the patch below for
an example.

Your environment apparently does handle \co{} in other environments,
as there are a lot of them in Chapter 1.  So if mbox fixes it for you,
I would be OK mboxing all the \co{}s in tables.

							Thanx, Paul

------------------------------------------------------------------------

diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
index c98f3a78652f..a5b530fc989e 100644
--- a/toolsoftrade/toolsoftrade.tex
+++ b/toolsoftrade/toolsoftrade.tex
@@ -1242,7 +1242,7 @@ but may be implemented straightforwardly as follows:
 	\hline
 	\hline
 	Thread Management
-		& \co{pthread_t}
+		& \mbox{\co{pthread_t}}
 			& \co{struct task_struct} \\
 	\cline{2-3}
 		& \co{pthread_create()}


  reply	other threads:[~2014-12-12 16:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20141211173210.GE31140@pd.tnic>
2014-12-11 17:52 ` perfbook build error Paul E. McKenney
2014-12-11 19:07   ` Borislav Petkov
2014-12-11 19:17     ` Borislav Petkov
2014-12-11 19:32       ` Paul E. McKenney
2014-12-11 19:59         ` Borislav Petkov
2014-12-11 20:10           ` Paul E. McKenney
2014-12-11 20:22             ` Borislav Petkov
2014-12-11 21:14               ` Paul E. McKenney
2014-12-12 16:38                 ` Paul E. McKenney [this message]
2014-12-12 17:53                   ` Borislav Petkov
     [not found]                     ` <20141212181804.GX25340@linux.vnet.ibm.com>
2014-12-12 18:47                       ` Borislav Petkov
2014-12-12 18:58                         ` Paul E. McKenney
2014-12-12 19:13                           ` Borislav Petkov
2014-12-12 19:30                             ` Paul E. McKenney
2014-12-12 20:15                               ` Borislav Petkov
2014-12-12 20:27                                 ` Paul E. McKenney
2014-12-11 19:51     ` Paul E. McKenney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141212163835.GA29275@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=bp@alien8.de \
    --cc=perfbook@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.