[NTG-context] bug in \type?
Dear list,
using the latest beta (it also happens with ConTeXt from TL 2013), I
don’t get the space in \type{\em #1}.
Here you have a minimal sample that shows the difference with other
verbatim commands:
\starttext
\type{\em #1}
\arg{\em #1}
\starttyping\em #1\stoptyping
\stoptext
Is this a bug in \type or am I missing something?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
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
___
Re: [NTG-context] Bug in \type
On 28-9-2010 2:38, Aditya Mahajan wrote:
Hi,
There is a bug in buff-ver.mkiv. Minimal example:
\starttext
\type+\test{+
\stoptext
fixed in next beta
-
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
-
___
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
___
[NTG-context] Bug in \type
Hi,
There is a bug in buff-ver.mkiv. Minimal example:
\starttext
\type+\test{+
\stoptext
gives
Runaway argument?
\stoptext
! File ended while scanning use of \dodotypeDD.
system error on line 0 in file : File ended while scanning use
of \dodotypeDD ...
empty file
inserted text
\par
* ./test
This example works fine in MkII.
Bugfix: In buff-ver.mkiv change line395
\setcatcodetable \typcatcodesa
to
\setcatcodetable \vrbcatcodes
Aditya
___
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
___
Re: [NTG-context] Bug with type .. ?
Taco Hoekwater wrote:
Hans Hagen wrote:
Question for taco: can we make such spaces optionally disappear in future
tex's?
In most cases, yes.
(but not always, because something like the internal form of
\aacute a can not reliably be represented by adding extra
tokens like in \aacute{}a, for example)
indeed, but it would already help if non-letters (i.e. the chars with catcodes
not making up a \cs) would be taken care of
\abc def - not handled
\abc{def}- space omitted
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bug with type .. ?
Aditya Mahajan wrote:
On Fri, 28 Jul 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
Isn't \type.. be supposed to be equivalent to \type{..} ?
\title{some \type{thing} }
works perfectly but
\title{some \typething}
will not work in commands that get an argument because it is
related to catcode changes
Ah. Makes sense.
we could use \scantokens if there was not this space-creeps-in-after
\cs problem)
Well, found a workaround. Not sure if this one is a bug or a feature
(is a feature to me)
\title{some \type{\thing\{and\}}}
However, things get real weird.
\title{\type{$\Pr\{A\}$}}
gives me
you can try:
\title{\retype{$\Pr\{A\}$}}
watch the space after \Pr
Question for taco: can we make such spaces optionally disappear in future tex's?
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bug with type .. ?
Hans Hagen wrote:
Question for taco: can we make such spaces optionally disappear in future
tex's?
In most cases, yes.
(but not always, because something like the internal form of
\aacute a can not reliably be represented by adding extra
tokens like in \aacute{}a, for example)
Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bug with type .. ?
On Sat, 29 Jul 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
On Fri, 28 Jul 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
Isn't \type.. be supposed to be equivalent to \type{..} ?
\title{some \type{thing} }
works perfectly but
\title{some \typething}
will not work in commands that get an argument because it is
related to catcode changes
Ah. Makes sense.
we could use \scantokens if there was not this space-creeps-in-after
\cs problem)
Well, found a workaround. Not sure if this one is a bug or a feature
(is a feature to me)
\title{some \type{\thing\{and\}}}
However, things get real weird.
\title{\type{$\Pr\{A\}$}}
gives me
you can try:
\title{\retype{$\Pr\{A\}$}}
watch the space after \Pr
Thanks for the hint.
I also found out
\startbuffer
$\Pr\{A\}$
\stopbuffer
\title{\typebuffer}
which seems pretty robust.
Aditya
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bug with type .. ?
On Fri, 28 Jul 2006, Aditya Mahajan wrote:
Isn't \type.. be supposed to be equivalent to \type{..} ?
\title{some \type{thing} }
works perfectly but
Actually this does not work as expected. The font does not change to
monotype. Is that delebrate?
Aditya
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bug with type .. ?
Aditya Mahajan wrote:
Isn't \type.. be supposed to be equivalent to \type{..} ?
\title{some \type{thing} }
works perfectly but
\title{some \typething}
will not work in commands that get an argument because it is
related to catcode changes
we could use \scantokens if there was not this space-creeps-in-after
\cs problem)
Hans
--
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bug with type .. ?
Aditya Mahajan wrote:
On Fri, 28 Jul 2006, Aditya Mahajan wrote:
Isn't \type.. be supposed to be equivalent to \type{..} ?
\title{some \type{thing} }
works perfectly but
Actually this does not work as expected. The font does not change to
monotype. Is that delebrate?
no, a bug
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bug with type .. ?
Aditya Mahajan wrote:
On Fri, 28 Jul 2006, Aditya Mahajan wrote:
Isn't \type.. be supposed to be equivalent to \type{..} ?
\title{some \type{thing} }
works perfectly but
Actually this does not work as expected. The font does not change to
monotype. Is that delebrate?
rather nasty ...
in setupcommonverbatim you will see:
%\def\verbatimfont{\typingparameter\c!style\normalnoligatures\font}%
being replaced by
\def\verbatimfont{\dosetfontattribute{\currenttypingclass\currenttyping}\c!style\normalnoligatures\font}%
now, font attributed are ignored in titles and such so we need
\def\verbatimfont{\redoconvertfont\dosetfontattribute{\currenttypingclass\currenttyping}\c!style\normalnoligatures\font}%
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bug with type .. ?
On Fri, 28 Jul 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
On Fri, 28 Jul 2006, Aditya Mahajan wrote:
Isn't \type.. be supposed to be equivalent to \type{..} ?
\title{some \type{thing} }
works perfectly but
Actually this does not work as expected. The font does not change to
monotype. Is that delebrate?
rather nasty ...
in setupcommonverbatim you will see:
%\def\verbatimfont{\typingparameter\c!style\normalnoligatures\font}%
being replaced by
\def\verbatimfont{\dosetfontattribute{\currenttypingclass\currenttyping}\c!style\normalnoligatures\font}%
now, font attributed are ignored in titles and such so we need
\def\verbatimfont{\redoconvertfont\dosetfontattribute{\currenttypingclass\currenttyping}\c!style\normalnoligatures\font}%
Thanks. This works correctly.
Aditya
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bug with type .. ?
On Fri, 28 Jul 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
Isn't \type.. be supposed to be equivalent to \type{..} ?
\title{some \type{thing} }
works perfectly but
\title{some \typething}
will not work in commands that get an argument because it is
related to catcode changes
Ah. Makes sense.
we could use \scantokens if there was not this space-creeps-in-after
\cs problem)
Well, found a workaround. Not sure if this one is a bug or a feature
(is a feature to me)
\title{some \type{\thing\{and\}}}
However, things get real weird.
\title{\type{$\Pr\{A\}$}}
gives me
! Extra }, or forgotten $.
recently read }
argument ...tofoneargument {\type {$\Pr \{A\}$}}
\endstrut }\xdef
\localhe...
\@@ko::normal ...box {\localheadsetup \noindent #2
}\fi
\doplaceheadtext ...attributes \dostopattributes }
}\fi
\endheadplacement {#1...
\dodododoconstructhead ...arking [#1\v!number ]{}}
\writesection
{#1}{-}{#4}\...
l.69 \title{\type{$\Pr\{A\}$}}
which I think is the currect behaviour.
There is really no need to change anything. I am happy with Do not
use \type inside argument. The unexpected can happen.
Aditya
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
