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 Thanks for you help! Thomas
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. Aditya
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
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 ___________________________________________________________________________________
Am Donnerstag, den 08.09.2011, 10:57 +0200 schrieb luigi scarso:
On Thu, Sep 8, 2011 at 10:39 AM, Thomas Friedrich
wrote: Question: Is there a way to replace the ">>" and "<<" strings in the typesetting environment by something else? Or another work around?
maybe \startHaskell foo = bar =/BTEX<
-- luigi
For anyone who's interested, I will do the following now: \startHaskell foo /BTEX{\tt >>\!=}/ETEX bar foo /BTEX>>\!=/ETEX bar bar /BTEX{\tt =\!<<}/ETEX foo bar /BTEX=\!<
On 8-9-2011 10:39, Thomas Friedrich wrote:
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?
this is because << >> is considered grouping just use mkiv Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (5)
-
Aditya Mahajan
-
Hans Hagen
-
luigi scarso
-
Thomas Friedrich
-
Wolfgang Schuster