LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
David Carlisle <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Thu, 22 May 2014 20:42:09 +0100
text/plain (43 lines)
On 22/05/2014 17:09, Joseph Wright wrote:
> Hello all,
> Currently, we have \ior_open:Nn for reading from a file, but no defined
> interface for using the 'pipe' shell escape provided by pdfTeX. As we
> forbid spaces in file names,

why do we do that? Spaces in filenames always seem like an abomination 
to me.
But that seems to be a relic on the 1970s I've noticed that people who 
started using
computers this century don't seem to think anything of using a 
descriptive phrase
as a filename...

Shouldn't we just allow spaces (and leading | or any other system 
dependent special
syntax) just surrounding any user supplied name by " " to keep it together?

> something like
>    \ior_open:Nn \g_some_ior {"|kpsewhich~-all~file.tex"}

why not simply

ior_open:Nn \g_some_ior {|kpsewhich~-all~file.tex}

and let web2c worry about the fact it isn't a real file?

> fails with an error. A defined interface("\ior_pipe:Nn") has been
> suggested
> (
> Thoughts on the concept/naming/etc.? Note that this is opening a
> pseudo-file so does need to be related in some way to \ior_open:Nn.