From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: NTG-Context ConTeXt users <ntg-context@ntg.nl>
Subject: \type ignores space between command and bracket
Date: Tue, 5 Nov 2019 21:14:36 +0100 [thread overview]
Message-ID: <9436d0e1-a117-1d97-c34a-a7ca1e52942f@gmail.com> (raw)
Hi,
in the following code example the result from \type lacks the space
between \cmd and the following left bracket.
\starttext
\starttyping
\cmd [...]
\stoptyping
\type{\cmd [...]}
\stoptext
Wolfgang
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2019-11-05 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 20:14 Wolfgang Schuster [this message]
2024-02-02 10:16 ` [NTG-context] " wolfgangbackes--- via ntg-context
2024-02-02 17:34 ` Hans Hagen via ntg-context
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=9436d0e1-a117-1d97-c34a-a7ca1e52942f@gmail.com \
--to=wolfgang.schuster.lists@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).