Reputation
606
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
1 6 20
Newest
 Yearling
Impact
~35k people reached

  • 0 posts edited
  • 1 helpful flag
  • 68 votes cast
Jun
18
comment MacTeX 2015: TeX Live Utility stuck on “Validating Server…”
@UlrikeFischer and Herbert Thanks for the help, please mark as duplicate.
Jun
18
comment MacTeX 2015: TeX Live Utility stuck on “Validating Server…”
@Herbert It crashes, but before it does, it now shows a message saying that this URL has TeX Live version 2015 while I have TeX Live version 18446744073709551615. That can't be right! :-) Do you know how TeX Live Utility determines the TeX Live version? dropbox.com/s/8ar8ysll635x3jg/…
Jun
18
awarded  Yearling
Jun
18
comment MacTeX 2015: TeX Live Utility stuck on “Validating Server…”
@Pouya There are no updates available either for tlmgr or for the TeX Live Utility GUI program.
Jun
18
asked MacTeX 2015: TeX Live Utility stuck on “Validating Server…”
Apr
3
comment Simplest way to extract errors from log files
@David There's no ? because of -interaction=nonstopmode. Is it possible to put in a marker where the ? would be or preserve the ? while making sure that TeX will never try to read any input?
Apr
3
comment Simplest way to extract errors from log files
@SeanAllred Regardless, I need to extract a human readable concise error from a mess of a log file. There is no possibility to display a log file. I don't understand your comment about editors. There are no editors involved.
Apr
3
comment Simplest way to extract errors from log files
@SeanAllred Neither grep, not an editor is involved. Think of something similar to LaTeXiT, which makes it necessary to report readable errors to the user.
Apr
3
comment Simplest way to extract errors from log files
Do you have any comments on question 1., i.e. is the ! a reliable indicator that something went wrong? I'm going to try reading from the ! line up to the next empty line as an imperfect but useful solution, with some limitation on the number of lines just in case that empty line is missing.
Apr
3
comment Simplest way to extract errors from log files
In my application, one-line math-mode snippers are being auto-converted to vector graphics and then used in another software (similar to LaTeXiT). Given the application and workflow, showing the full log file, with all the irrelevant part (most of it) is counterproductive (although I understand that it's hard to see why this is the case without having used the application). So I still need to extract the errors, or perhaps only the very first error. Currently I am only extracting a single line (with the !), which is still better than the full log. But I'm hoping to do a little better.
Apr
3
revised Simplest way to extract errors from log files
added 2 characters in body
Apr
3
revised Simplest way to extract errors from log files
added 42 characters in body
Apr
3
comment Simplest way to extract errors from log files
Please re-tag the question if necessary, I couldn't find many relevant already existing tags.
Apr
3
asked Simplest way to extract errors from log files
Feb
26
accepted Using 10pt fonts with the fourier package actually gives me 9.17pt
Feb
26
accepted Enter 2 by n matrix (permutation notation) as inline math without taking up much space
Feb
3
awarded  Popular Question
Oct
24
awarded  Self-Learner
Oct
24
comment Enter 2 by n matrix (permutation notation) as inline math without taking up much space
@percusse I made the answer community wiki, so please feel free to add this information (or your own separate answer if you wish).
Oct
24
revised Enter 2 by n matrix (permutation notation) as inline math without taking up much space
added 530 characters in body