ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jesse Alama <alama@stanford.edu>
To: ntg-context@ntg.nl
Subject: Re: Spacing after \cite
Date: Mon, 30 Mar 2009 08:16:15 -0700	[thread overview]
Message-ID: <m2wsa7xcqo.fsf@stanford.edu> (raw)
In-Reply-To: <49D076B8.6070309@elvenkind.com>

Taco Hoekwater <taco@elvenkind.com> writes:

> Wolfgang Schuster wrote:
>>>>
>>>> So, \doifnextcharelse vs \doifnextoptionalelse.
>
> I still think Hans should fix that in the core, but ...
>
>>> Any progress on this?  I'm seeing the same behavior.
>> 
>> \startmode[whisper]
>> ask Taco for a after key and use \autoinsertnextspace
>> \stopmode
>
> can you try this in the header just to see how if it works out?
>
>   \usemodule[bib]
>   \let\normaldocite\docite
>   \def\docite[#1][#2]%
>     {\normaldocite[#1][#1]\autoinsertnextspace }
>
>   ...
>   \starttext

Thanks for helping out with this.  Is the second "#1" supposed to be
"#2"?  In any case, this fix gives an error:

! You can't use `macro parameter character #' in horizontal mode.
\p!doifinstringelse ...tringelse \@EA ##\@EA 1#1##
                                                  2##3\war {\unless \if ##2@...
\rawdodoifinsetelse ...ingelse \@@@instring {,#1,}
                                                  \@EA \firstoftwoarguments ...
\addtocommalist #1#2->\rawdoifinsetelse {#1}#2
                                              \resetglobal {\dodoglobal \ede...
\doifreferencefoundelse ...ce \ifreferencefound #2
                                                  \else #3\fi \egroup \dores...
\redoloop ->\expandrecursecontent 
                                  \endofloop 
<to be read again> 
                   {
...
l.1184 \completepublications[criterium=all]

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
___________________________________________________________________________________


  reply	other threads:[~2009-03-30 15:16 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
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 [this message]
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=m2wsa7xcqo.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).