Reputation
1,419
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
6 20
Impact
~39k people reached

  • 0 posts edited
  • 0 helpful flags
  • 33 votes cast
Aug
20
awarded  Popular Question
Jun
2
awarded  Popular Question
Feb
18
awarded  Notable Question
Dec
6
awarded  Yearling
Aug
28
awarded  Popular Question
Jul
2
awarded  Curious
Jun
6
awarded  Notable Question
Jan
13
awarded  Popular Question
Dec
6
awarded  Yearling
Nov
23
awarded  Notable Question
Oct
14
awarded  Nice Question
Oct
10
awarded  Popular Question
Aug
20
awarded  Popular Question
Aug
18
awarded  Popular Question
May
22
awarded  Popular Question
Dec
6
awarded  Yearling
Nov
25
comment Reducing output garbage
@MikaelVejdemo-Johansson Because I don't wanna see garbage that is irrelevant to the project. those lines I mentioned are absolutely useless. Why do I need to know that some .fd is included? What's the point? To let me know I included the file? Do I need to see it every compilation and have it break the flow of the console output just to let me know each time it was included? (I think I got it the first time) If I need more verbose output I'll enable it by not using batchmode.
Nov
25
revised Reducing output garbage
added 85 characters in body
Nov
25
asked Reducing output garbage
Sep
18
comment Consume/absorb a token
@BrunoLeFloch You say it has already converted tokens before \InsertToken appears. But I thought TeX processed tokens one at a time and made decisions based on what the previous token or token group was? The way I see it, \InsertToken{\}mymacro first calls \InsertToken{\} and the macro can do what it wants(insert or remove stuff in the token stream. THEN whatever the "output" of the macro was gets substituted for the call. So we end up with xxxxmymacro where xxx is the "output" of the macro call. Now maybe TeX already parsed xxxx and won't reparse xxxxmymacro as a whole?