meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 9 months |
| seen | May 16 at 12:01 | |
| stats | profile views | 57 |
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.
|
May 3 |
accepted | Custom titlemarks |
|
May 3 |
answered | Custom titlemarks |
|
May 3 |
accepted | Prevent overlapping of elements on page |
|
May 3 |
answered | Prevent overlapping of elements on page |
|
May 3 |
answered | Selfhosted collaborative webbased LaTeX editor |
|
May 1 |
revised |
titlesec titlemarks not working with pdfcolparallel removed unnecessary package reference |
|
Apr 30 |
revised |
titlesec titlemarks not working with pdfcolparallel made it neater |
|
Apr 30 |
revised |
titlesec titlemarks not working with pdfcolparallel Added missing code |
|
Apr 30 |
asked | titlesec titlemarks not working with pdfcolparallel |
|
Mar 27 |
comment |
Background gradient Pardon me, but the following quote just seemed appropriate. "...I have discovered a truly marvelous demonstration of this proposition that this margin is too narrow to contain." - Fermat :) |
|
Mar 11 |
accepted | Execute command stored in aux file |
|
Mar 11 |
revised |
Execute command stored in aux file added 187 characters in body |
|
Mar 4 |
comment |
Execute command stored in aux file Could the problem of it not executing be related to the fact that according to the TeXbook p. 217 it reads it into a control sequence "and the control sequence is defined to be a parameterless macro..."? Whatever that might entail. |
|
Mar 4 |
revised |
Execute command stored in aux file added 8 characters in body |
|
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? |
