From: Matthijs Kooijman <matthijs@stdin.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Why are pretty printer names uppercased?
Date: Wed, 26 Aug 2009 11:37:04 +0200 [thread overview]
Message-ID: <20090826093704.GQ12901@katherina.student.utwente.nl> (raw)
In-Reply-To: <4A94FC5E.9000203@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1178 bytes --]
Hi Hans,
>> according to the wiki, and the current code, the arguments to
>> \installprettytype should be uppercased. E.g.:
>>
>> \installprettytype [PHP] [PHP]
> because want uppercase
>
> \startTEX
> \stopTEX
Well, those would be coming from the first argument of definetyping. AFAIU,
neither argument to installprettytype is related to these commands.
>> \definetyping[PHP] [option=PHP]
> indeed. as i don't like casing in filenames, and function names
Agreed, me neither.
> actually, the advice is that user definitions use uppercase
>
> \definehead[MySection][section]
>
> etc, just to avoid clashes with built in commands
That makes sense for commands, which is not what I'm proposing to change. I
would propose making it look like the following:
\installprettytype [php] [php]
\definetyping [PHP] [option=php]
Here, the second "php" refers to "pret-php.lua", the first and last "php"
refer to each other and to the "php" in newvisualizer("php").
The command defined is still \startPHP, but now the values that refer to other
lowercase things (filename, pretty printer name) are lowercase consistently.
How's this?
Gr.
Matthijs
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-08-26 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 8:52 Matthijs Kooijman
2009-08-26 9:11 ` Hans Hagen
2009-08-26 9:37 ` Matthijs Kooijman [this message]
2009-08-26 9:47 ` 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=20090826093704.GQ12901@katherina.student.utwente.nl \
--to=matthijs@stdin.nl \
--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).