From: Jesse Alama <alama@stanford.edu>
To: ntg-context@ntg.nl
Subject: Re: Spacing after \cite
Date: Sun, 29 Mar 2009 11:09:58 -0700 [thread overview]
Message-ID: <m263hsyzd5.fsf@stanford.edu> (raw)
In-Reply-To: <alpine.LNX.2.00.0903101204290.8765@ybpnyubfg.ybpnyqbznva>
Aditya Mahajan <adityam@umich.edu> writes:
> On Tue, 10 Mar 2009, Aditya Mahajan wrote:
>
>> So I am guessing that the difference is because of something else,
>> but I cannot see any differences.
>
> The old version gives
>
> \dodoubleempty #1->\noshowargumenterror \doifnextcharelse
> [{\dodoubletestempty #1} {\dodoublefakeempty #1}
> #1<-\dododocite
>
>
> The new one gives
>
> \dodoubleempty #1->\noshowargumenterror \doifnextoptionalelse {\dodoubletestemp
> ty #1} {\dodoublefakeempty #1}
> #1<-\dododocite
>
> So, \doifnextcharelse vs \doifnextoptionalelse.
Any progress on this? I'm seeing the same behavior.
Jesse
--
Jesse Alama (alama@stanford.edu)
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-03-29 18:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 15:59 Aditya Mahajan
2009-03-10 16:09 ` Aditya Mahajan
2009-03-29 18:09 ` Jesse Alama [this message]
2009-03-29 18:27 ` Wolfgang Schuster
2009-03-29 19:24 ` Jesse Alama
2009-03-30 7:37 ` Taco Hoekwater
2009-03-30 15:16 ` Jesse Alama
2009-03-31 7:43 ` Taco Hoekwater
2009-03-31 16:43 ` Jesse Alama
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=m263hsyzd5.fsf@stanford.edu \
--to=alama@stanford.edu \
--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).