From: Nikolai Weibull <context-list@pcppopper.org>
Subject: Getting { in the input.
Date: Fri, 28 May 2004 13:13:37 +0200 [thread overview]
Message-ID: <20040528111337.GD4964@puritan.pcp.ath.cx> (raw)
Again I'm having some problems generating my ASCII table, this time it's
{ and } that are the culprits. I'm currently using $\{$ and $\}$ for
them, but it would be great if there was a way to get them rendered like
the other characters that have \type{...} surrounding them. There
doesn't seem to be an easy way to do this...is there perhaps a hard one?
nikolai
--
::: name: Nikolai Weibull :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA :: loc atm: Gothenburg, Sweden :::
::: page: www.pcppopper.org :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
next reply other threads:[~2004-05-28 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 11:13 Nikolai Weibull [this message]
2004-05-28 11:22 ` Patrick Gundlach
2004-05-29 9:59 ` Nikolai Weibull
2004-06-01 18:50 ` 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=20040528111337.GD4964@puritan.pcp.ath.cx \
--to=context-list@pcppopper.org \
--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).