From: Thomas Friedrich <info@suud.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Typesetting >> in verbatim
Date: Thu, 08 Sep 2011 10:39:34 +0200 [thread overview]
Message-ID: <1315471174.10062.33.camel@friedrich> (raw)
In-Reply-To: <54584B50-4F96-4383-80A9-7AC029B975A6@googlemail.com>
Am Donnerstag, den 08.09.2011, 09:59 +0200 schrieb Wolfgang Schuster:
> Am 08.09.2011 um 09:55 schrieb Aditya Mahajan:
>
> > On Wed, 7 Sep 2011, Thomas Friedrich wrote:
> >
> >> Hi,
> >>
> >> I am having problems typing ">>" when typesetting code within a
> >> \definetyping environment.
> >>
> >> I hope someone might be able to give me a hint. My code looks as
> >> follows:
> >>
> >> \definetyping
> >> [Haskell]
> >> [ option=commands,
> >> before={\startframedtext[width=\makeupwidth,
> >> frame=off,bottomframe=on,topframe=on,
> >> background=screen,backgroundscreen=.90]},
> >> after={\stopframedtext},
> >> bodyfont=9pt,
> >> margin=1.5em]
> >>
> >> \startHaskell
> >> main = foo >>= bar
> >> \stopHaskell
> >>
> >> Whenever ConTeXt comes across >> anywhere in the text, it just doesn't
> >> typeset anything. So in the above case, I get the output:
> >>
> >> main = foo = bar
> >
> > Confirmed. >> are eaten in MkII but everything works fine with MkIV. My guess is because of automatic ligatures for >>. My usual trick for disabling such ligatures in MkII is
> >
> > \usetypescript [modern] [texnansi]
> > \setupbodyfont [modern]
> >
> > but that does not work in this case. There were some discussions in the past about disabling ligatures in typewriter font, but I don't remember the exact solution.
>
> No, the culprit is “option=commands" which gobbles “>>”.
>
> Wolfgang
You are absolutely right, Wolfgang. When removing the "option=commands"
from the definition, the ">>" won't get eaten. (Thanks!) However, my
whole code consists of things such as
\startHaskell
main = f1 /BTEX$\circ$/ETEX f2 >>= hey
\stopHaskell
How comes that the ">>" are gobbled? Even worse, something like
\startHaskell
foo = bar =<< print
\stopHaskell
won't even compile. It doesn't like "<<".
Question: Is there a way to replace the ">>" and "<<" strings in
the typesetting environment by something else? Or another work around?
Thanks,
Thomas
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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:[~2011-09-08 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 9:42 Thomas Friedrich
2011-09-08 7:55 ` Aditya Mahajan
2011-09-08 7:59 ` Wolfgang Schuster
2011-09-08 8:39 ` Thomas Friedrich [this message]
2011-09-08 8:57 ` luigi scarso
2011-09-08 14:34 ` Thomas Friedrich
2011-09-08 14:51 ` 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=1315471174.10062.33.camel@friedrich \
--to=info@suud.de \
--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).