meta user
network profile
| bio | website | navarroj.com/latex |
|---|---|---|
| location | London, United Kingdom | |
| age | 32 | |
| visits | member for | 2 years, 9 months |
| seen | May 15 at 21:05 | |
| stats | profile views | 951 |
A computer science lecturer at University College London. I do stuff in logic, theorem proving, program analysis and verification. I'm a very enthusiastic TeX/LaTeX user, most days.
I also run a small site for LaTeX beginners in spanish: LaTeX Fácil.
|
May 15 |
comment |
How to divide document for black and color printing? Nice one! Now, I think on draft mode \includegraphics already replaces the image with a corresponding box of the same size. Maybe looking at its code one could figure out how to put there an empty box instead? This will be better as it won't force you to always supply the width and height of the image. |
|
Apr 30 |
comment |
Some errors with a little document You'll get better answers if you first try to write a minimal example. |
|
Apr 9 |
comment |
LaTeX Editors/IDEs @rolve, it all depends on how you tend to write your code. I have seen very messy code mixing content/formatting within the body of the document, but by using semantically defined commands you can make the distinction very explicit. |
|
Mar 7 |
comment |
How can I test if a command is followed by an argument? but in the {\mycmd\token\mycmd} case, I wanted \token to be used as an argument to the first \mycmd. Here it seems that the argument is taken only if enclosed by braces? |
|
Jan 15 |
comment |
Automatic left and right commands I don't know if this is the issue, but now looking at my code (after more than two years!) all those \let's at the beginning should have been \def's. |
|
Jan 15 |
comment |
Automatic left and right commands I've just tried it now and it does seem to compile fine without problems. Are you getting some errors or unexpected behaviour? |
|
Jan 12 |
comment |
Automatic left and right commands I guess you could just drop \mleft instead of \left, etc. But probably you want it to sometimes use \left and sometimes \mleft, right? Then you have to come up with an interface that allows you to select between the two. |
|
Dec 17 |
comment |
Distinguish math symbols in the language and the meta-language Yes, that is a safe assumption. Although, if it is much more work (and then likely to break on unpredictable circumstances), perhaps I'll just stick with the other more “manual” solutions. Anyway, thanks a lot for your answers because I always learn a lot from them! |
|
Dec 17 |
comment |
Distinguish math symbols in the language and the meta-language This looks very nice! Just the small complaint that the subscript 1 of the F does not seem to catch the color for meta. |
|
Nov 22 |
comment |
Same node distance between levels in a tikz tree? Ah! A small addition, I realised that while the nodes are place appropriately, edges are still being drawn from the centers of nodes, this becomes obvious when branching. However adding the options parent anchor={south},child anchor={north} cause the edges to be drawn from the parents bottom to the children top. |
|
Nov 22 |
comment |
Same node distance between levels in a tikz tree? Amazing! It does work! I worried that this might require messing with the tree drawing internals, but it's great to see that changing a few simple options can do the trick! Thanks! |
|
Nov 21 |
comment |
Same node distance between levels in a tikz tree? Sure, now it's a complete minimal document :) |
|
Nov 8 |
comment |
Filtering options with pgfkeys Thanks for the comments. I've written some code which seems to do the work that I was looking for; would love if you could also tell me what you think about it. |
|
Nov 7 |
comment |
Filtering options with pgfkeys Yes, that is exactly what I want to do! As you say probably an .unknown handler is a better alternative than filtering, but I'm still a bit lost on how to do the “option collecting” bit. I'm also surprised that pgftikz doesn't seem to already have an option implemented for this. |
|
Nov 2 |
comment |
Save choice and execute later in pgfkeys?\pgfkeys@split@path splits the current key into path+name; by setting the path to the current key before calling this, effectively this moves the path “one level up”. And the “cyclic call” is no cyclic, precisely for the same reason, I do a .cd up to go one leve up before. |
|
Nov 2 |
comment |
Save choice and execute later in pgfkeys? @AhmedMusa, sorry for that. I guess I could have explained myself better. Anyway, thanks for your help, now I've updated my question with something that looks like a solution to me. Would you like to comment on that? |
|
Nov 2 |
comment |
Save choice and execute later in pgfkeys? And what should I use to call the last action selected by the user? |
|
Nov 1 |
comment |
Save choice and execute later in pgfkeys? Sure, that is what I want to achieve. However (1) I don't want to have to invent a new name ( \navaaction) for each similar option that I may want to define. It feels that something like /navarro/action/exec is already a good name that shouldn't clash with other packages. And (2) I'm lazy, if I do this over and over again, I don't want to be writing \def\navaaction all the time. That's why I think it would be better to define a handler that does all the work for me. |
|
Oct 17 |
comment |
\dots versus \ldots - is there a difference?\dots is magic! ... when using amsmath ;-) |
|
Sep 6 |
comment |
Different sorting schemes in different sections of bibliography @Audrey, thanks for the pointer. I've just added a post there. |
