From: Christopher Creutzig <christopher@creutzig.de>
Subject: Re: \noalign?
Date: Mon, 03 Oct 2005 19:01:30 +0200 [thread overview]
Message-ID: <434163EA.1070207@creutzig.de> (raw)
In-Reply-To: <43405386.6000809@wxs.nl>
Hans Hagen wrote:
>>which tables allow using \noalign and in what places?
>>\NC one \NC two \NC three \NC\AR
>>\HL\noalign{\pause}%
>>\NC one \NC two \NC three \NC\AR
>>\noalign{\pause}\HL
> it all depends on what you want to achieve
I want to place a \pdfspecial in front of the \HL. Peter Rolf pointed
out correctly (and I had seen that myself as well) that the problem
seems to be with \AR only. I'll try and check if I can make the whole
thing work transparently with \AR or if I have to ask users to use \FR,
\MR, \LR for this usage pattern. (Usage: You build a table line by line
in a presentation.)
regards,
Christopher
prev parent reply other threads:[~2005-10-03 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 19:04 \noalign? Christopher Creutzig
2005-10-02 14:38 ` \noalign? Peter Rolf
2005-10-02 17:47 ` \noalign? Christopher Creutzig
2005-10-02 23:13 ` \noalign? Peter Rolf
2005-10-02 21:39 ` \noalign? Hans Hagen
2005-10-03 17:01 ` Christopher Creutzig [this message]
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=434163EA.1070207@creutzig.de \
--to=christopher@creutzig.de \
--cc=ntg-context@ntg.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).