From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setupnote (was subfootnote)
Date: Tue, 12 Oct 2010 10:46:38 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1010121044510.22642@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <AANLkTimS6srkV8+qB6YSSGUYRmGbwxv1fktnZ6P+WD+7@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 388 bytes --]
On Tue, 12 Oct 2010, luigi scarso wrote:
> You are right, my apologies for the error.
> I mean that in the meanwhile perhaps you can use somenthing like this
> \long\def\StartFootnote#1\StopFootnote{\startfootnote#1\stopfootnote\space}
Better use \autoinsertnextspace rather than \space. Or perhaps add
\autoinsertnextspace to \dodoredefinenotecommands. See the attached file.
Aditya
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: TEXT/x-tex; name=test.tex, Size: 748 bytes --]
\unprotect
\def\dodoredefinenotecommands#1#2#3%
{\unexpanded\expandafter\def\csname\e!start#3#1\expandafter\endcsname\expandafter
{\expandafter\dosingleempty\csname\s!do\e!start#3#1\endcsname}%
\unexpanded\expandafter\def\csname\s!do\e!start#3#1\expandafter\endcsname
\expandafter[\expandafter##\expandafter1\expandafter]\expandafter##\expandafter2\csname\e!stop#3#1\endcsname
{\begingroup
\doenumerationinit{#1}{#2}{#3}%
\@@notemakedescription[##1]{}{##2}%
\endgroup\autoinsertnextspace}}
\definenote [\v!footnote]
\protect
\starttext
let see if\startfootnote Footnote \stopfootnote the space goobled.
let see if
\startfootnote Footnote \stopfootnote
the space goobled.
\stoptext
[-- Attachment #3: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-10-12 14:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 12:03 subfootnote Steffen Wolfrum
2010-09-30 16:05 ` subfootnote Aditya Mahajan
2010-09-30 16:28 ` subfootnote Wolfgang Schuster
2010-09-30 16:53 ` subfootnote Steffen Wolfrum
2010-09-30 18:06 ` subfootnote Wolfgang Schuster
2010-09-30 18:31 ` subfootnote Steffen Wolfrum
2010-09-30 18:42 ` subfootnote Wolfgang Schuster
2010-09-30 18:57 ` subfootnote Steffen Wolfrum
2010-09-30 20:07 ` subfootnote Hans Hagen
2010-09-30 20:06 ` subfootnote Hans Hagen
2010-10-05 12:41 ` subfootnote Alan BRASLAU
2010-10-05 13:32 ` subfootnote Wolfgang Schuster
2010-10-05 14:01 ` subfootnote Steffen Wolfrum
2010-10-07 8:36 ` subfootnote Hans Hagen
2011-02-15 10:24 ` subfootnote Steffen Wolfrum
2010-10-12 9:48 ` \setupnote (was subfootnote) Alan BRASLAU
2010-10-12 9:54 ` Steffen Wolfrum
2010-10-12 10:27 ` Alan BRASLAU
2010-10-12 10:39 ` luigi scarso
2010-10-12 11:09 ` Yury G. Kudryashov
2010-10-12 11:32 ` luigi scarso
2010-10-12 14:46 ` Aditya Mahajan [this message]
2010-10-14 9:03 ` luigi scarso
2010-10-12 11:35 ` Wolfgang Schuster
2010-10-12 14:51 ` Aditya Mahajan
2010-10-12 15:06 ` Alan BRASLAU
2010-10-12 15:18 ` Hans Hagen
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=alpine.LNX.2.01.1010121044510.22642@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.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).