From: Hans Hagen <j.hagen@xs4all.nl>
To: Aditya Mahajan <adityam@umich.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with Filter Module in latent context beta
Date: Mon, 16 Apr 2018 23:59:16 +0200 [thread overview]
Message-ID: <7b0e1844-8cb6-8c86-7639-942d8377be6e@xs4all.nl> (raw)
In-Reply-To: <nycvar.YAK.7.76.44.1804161724590.9612@ybpnyubfg.ybpnyqbznva>
On 4/16/2018 11:27 PM, Aditya Mahajan wrote:
> On Sun, 15 Apr 2018, Hans Hagen wrote:
>
>> On 4/15/2018 7:08 AM, Aditya Mahajan wrote:
>>> On Sun, 15 Apr 2018, Hans Hagen wrote:
>>>
>>>> On 4/14/2018 9:52 PM, Lutz Haseloff wrote:
>>>>> I get another error message:
>>>>>
>>>>> open source > level 4, order 5, name 't-module-catcodes.tex'
>>>>> loading > Module Catcodes (ver: 2011.12.17)
>>>>>
>>>>> tex error > tex error on line 96 in file t-module-catcodes.tex: !
>>>>> Undefined control sequence
>>>> why are special catcodes needed? an dif so, there are often easier
>>>> ways than low level hacking
>>>
>>> This is the commit (from 2011!) where I added this code:
>>>
>>> https://github.com/adityam/filter/commit/c34023fd1ede0909a056a10c6352202f2295fba4
>>>
>>> My guess is that I did not want multiple newlines to collapse in
>>> t-vim, so I had redefined \activeendoflinetoken to {\strut\par}. The
>>> offending lines are copied from catc-ini.mkiv from the same time:
>>>
>>> https://github.com/contextgarden/context-mirror/blob/5056d7a854142aa63032b0a3ca4d41c496e41faf/tex/context/base/catc-ini.mkiv
>>>
>>> to make sure that I use the same syntax for MkII and MkIV.
>>>
>>> A couple of years after that I split the MkII and MkIV code into
>>> separate files, but I never touched the catcode part (because it was
>>> working).
>>>
>>> I cannot test the latest beta right now; I'll test it on Monday. In
>>> the meanwhile, what is the current recommended method to alter the
>>> way literal newlines and tabs are shown.
>> \starttext
>>
>> \start
>> \def\obeyedline{\blank[line]} \obeylines
>>
>> line 1
>>
>>
>> line 2
>>
>> line 3
>>
>> \stop
>>
>> \stoptext
>>
>> blank will cleanup for you
>
> I don't want multiple empty lines to collapse (this is for code
> listing). Here is a minimal example showing what t-vim is doing:
(I always remove multiple empty lines in code as i consider it an error.)
> \newcatcodetable \MinimalCatcodes
>
> \startcatcodetable \MinimalCatcodes % for reading t-vim output
> \catcode\backslashasciicode = \escapecatcode
> \catcode\leftbraceasciicode = \begingroupcatcode
> \catcode\rightbraceasciicode = \endgroupcatcode
> \catcode\endoflineasciicode = \activecatcode
> \catcode\formfeedasciicode = \othercatcode
> \catcode\spaceasciicode = \othercatcode
> \stopcatcodetable
>
> \starttext
> \bgroup
> \def\obeyedline{\strut\par}
> %\def\obeyedline{\blank[line]}
> \setcatcodetable\MinimalCatcodes\letcharcode\endoflineasciicode\obeyedline
> This is a \color[red]{test}
>
>
>
>
> To check multiple lines as well as color
> \egroup
> \stoptext
>
>
>
> If I replace the {\strut\par} with {\blank[line]}, multiple empty lines
> are collapsed to a single line.
Ok, I though that you wanted to collapse. How about this:
\def\obeyedline{\forcestrutdepth\vskip\lineheight} \obeylines
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-04-16 21:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 12:21 Lutz Haseloff
2018-04-14 13:02 ` Aditya Mahajan
2018-04-14 15:59 ` Hans Hagen
2018-04-14 19:52 ` Lutz Haseloff
2018-04-14 22:07 ` Hans Hagen
2018-04-15 5:08 ` Aditya Mahajan
2018-04-15 10:21 ` Hans Hagen
2018-04-16 16:52 ` Aditya Mahajan
2018-04-16 17:55 ` Hans Hagen
2018-04-16 21:27 ` Aditya Mahajan
2018-04-16 21:59 ` Hans Hagen [this message]
2018-04-16 22:01 ` Aditya Mahajan
2018-04-17 8:09 ` Hans Hagen
2018-04-17 12:03 ` Aditya Mahajan
2018-04-17 17:19 ` Aditya Mahajan
2018-04-17 2:52 ` Aditya Mahajan
2018-04-17 3:48 ` Lutz Haseloff
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=7b0e1844-8cb6-8c86-7639-942d8377be6e@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=adityam@umich.edu \
--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).