From: "Meer, Hans van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: typebuffer different from typefile
Date: Sun, 24 Apr 2016 15:20:13 +0000 [thread overview]
Message-ID: <EC67C6D9-B1D8-447B-9AE7-2B7EE3F22A96@uva.nl> (raw)
In-Reply-To: <571CE08C.9010004@gmx.es>
The point is not that I am without options for a practical solution here.
My point is that the difference between \typebuffer and \typefile breaks the strict and so much appreciated congruence between like macro calls.
Therefore my post must rather be seen as a plea to the maintainer(s) of these to consider a change in the given direction.
Hans van der Meer
> On 24 Apr 2016, at 17:04, Pablo Rodriguez <oinos@gmx.es> wrote:
>
> On 04/24/2016 10:31 AM, dr. Hans van der Meer wrote:
>> Why is there a difference in syntax between typing buffers and typing files?
>> For files enclosure in {} for buffers in [], for files optional
>> parameters, for buffers not.
>> Is it possible to make the syntax of these two the same, because their
>> usage parallels each other?
>
> Hi Hans,
>
> I wonder whether any of these two options may help you:
>
> \setuptyping[buffer][style=\ttx]
> \startbuffer[test]
> content of buffer
> \stopbuffer
> \starttext
> \typebuffer[test][style=\ss\red]
> \typefile[style=\ttx\blue]{test.txt}
> \stoptext
>
> Again, just in case it might help,
>
> Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2016-04-24 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 8:31 dr. Hans van der Meer
2016-04-24 15:04 ` Pablo Rodriguez
2016-04-24 15:20 ` Meer, Hans van der [this message]
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=EC67C6D9-B1D8-447B-9AE7-2B7EE3F22A96@uva.nl \
--to=h.vandermeer@uva.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).