From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to not gobble space after a command
Date: Fri, 20 Nov 2009 11:30:22 +0100 [thread overview]
Message-ID: <fe8d59da0911200230y393c4442m104c68814ab258ae@mail.gmail.com> (raw)
In-Reply-To: <20091120102352.GZ3418@katherina.student.utwente.nl>
On Fri, Nov 20, 2009 at 11:23 AM, Matthijs Kooijman <matthijs@stdin.nl> wrote:
> Hi all,
>
> I'm working with a few custom macros to simplify typing a bit, like:
>
> \def\VHDL{\small{VHDL}}
>
> However, when I use this macro in text, like \VHDL this, it gobbles the space
> after it. I've seen some references that say to solve this by writing \VHDL{}
> instead, but that is of course very unpretty. I've tried to put all kinds of
> stuff ({}, \mbox{}, \obeyedspace, etc.) inside the \VHDL macro, but it seems
> the space is already gone there, so that didn't work. (Note that just putting
> a space inside the macro won't work, for cases where I use \VHDL, like this)
>
> It seems that latex has an xspace package that does some guesswork about
> whether a space is required, but it looks mightily scary. Does ConTeXt provide
> for any way to solve this problem in a nice way? Or is this just so
> fundamental in TeX that there is no real solution?
I don't know the answer.
But I remember that a similar question time ago
trigged to me to know more about \futurelet
and I consider it a real gain for my own personal macro.
Maybe can be the same for you.
--
luigi
___________________________________________________________________________________
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:[~2009-11-20 10:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 10:23 Matthijs Kooijman
2009-11-20 10:30 ` luigi scarso [this message]
2009-11-20 10:31 ` Taco Hoekwater
2009-11-20 10:41 ` Matthijs Kooijman
2009-11-20 10:50 ` luigi scarso
2009-11-20 11:00 ` Matthijs Kooijman
2009-11-20 11:05 ` luigi scarso
2009-11-30 20:53 ` Matthijs Kooijman
2009-11-30 21:04 ` luigi scarso
2009-11-30 21:31 ` Matthijs Kooijman
2009-11-30 23:14 ` Hans Hagen
2009-11-30 23:18 ` luigi scarso
2009-11-30 23:42 ` Hans Hagen
2009-11-30 23:53 ` luigi scarso
2009-11-20 11:04 ` Alan BRASLAU
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=fe8d59da0911200230y393c4442m104c68814ab258ae@mail.gmail.com \
--to=luigi.scarso@gmail.com \
--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).