825 reputation
724
bio website
location Earth
age
visits member for 3 years, 4 months
seen Dec 5 at 12:21

mcgafter noun

A makeshift instrument or tool (mechanical, electronic or otherwise) whereby one may gaff (poke, hook, hack) something to achieve the desired result. Works better when it gets attached to a mcgoerie*. Very common worldwide especially in parts of Africa where it has been known to be the tool of choice of even high level government officials for all governmental problems.


mcgoerie noun

A well designed tool similar in shape and function to a mcgafter* yet completely different in it's purpose. May also be used on it's own. Uses of this instrument are very rare and appears to only occur in the countries of Namibia, Zimbabwe, Lesotho and South Africa, as well as where former residents of those countries have dispersed abroad.


Mar
4
comment Execute command stored in aux file
I understand, but I want to read from the first file then write to a second file on the same run.
Mar
4
comment Execute command stored in aux file
Ok, Thanks. I've given a small clarification in the OP for what it's worth. The main issue at present is reading a command from an aux file and executing it on the same run.
Mar
4
revised Execute command stored in aux file
clarification
Mar
4
comment Execute command stored in aux file
Thanks but the \fromFile is really a replacement for writing out \writeVerse{A}{1}{F} etc. each time since due to other factors beyond the scope of the MWE the parameters will change for \writeVerse. So in reality you would not see \writeVerse{A}{1}{F} in there at all except in the aux files. This script gets called by an external OS script and might have to be run even up to a 1000 times before the layout would be satisfactory. But that's handled by the external script. This TeX file just need to be able to read an executable command from the first aux file and write to the second.
Mar
4
comment Execute command stored in aux file
@egreg Did you mean the input file? I've created the input file by some other means (manually in this case), that's why I've given the contents thereof separately. The output file gets created by the tex script. Both exists with contents after the xelatex run, although the output is shorting the first two lines, due to the write command not executing.
Mar
4
comment Execute command stored in aux file
@egreg Thanks, but I thought I circumvented that issue by using two files. A \jobname.yposIN.txt and a \jobname.yposOUT.txt. Did I miss something there?
Mar
4
asked Execute command stored in aux file
Feb
14
comment Unwanted code present in file output
Great this seems to solve the problem. I was not aware of the @ convention. Thanks. The pdflastxpos code was removed for the MWE.
Feb
14
accepted Unwanted code present in file output
Feb
14
revised Unwanted code present in file output
Added clarification
Feb
14
comment Unwanted code present in file output
@JosephWright Thanks, but your solution produces {1}{F} {\writeVerse }{F} in the output file. Please see question for clarification.
Feb
14
revised Unwanted code present in file output
added missing code
Feb
13
asked Unwanted code present in file output
Dec
20
comment pdfsavepos coordinates remains zero
I see, thanks. I have adapted the solution from somewhere else and misunderstood the usage of immediate in this context.
Dec
20
accepted pdfsavepos coordinates remains zero
Dec
20
asked pdfsavepos coordinates remains zero
Dec
17
accepted How to run TeX from the command line interface in Linux
Dec
17
asked How to run TeX from the command line interface in Linux
Dec
14
awarded  Quorum
Dec
14
comment How much text will end up on a page?
@DavidCarlisle I might be missing something, but I don't think the parallel actually syncs my texts properly.