meta user
network profile
| bio | website | navarroj.com/latex |
|---|---|---|
| location | London, United Kingdom | |
| age | 32 | |
| visits | member for | 2 years, 10 months |
| seen | May 22 at 14:08 | |
| stats | profile views | 958 |
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.
|
Nov 8 |
answered | Filtering options with pgfkeys |
|
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 7 |
asked | Filtering options with pgfkeys |
|
Nov 4 |
awarded | Good Answer |
|
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 |
revised |
Save choice and execute later in pgfkeys? added 1571 characters in body |
|
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 |
revised |
Save choice and execute later in pgfkeys? added 41 characters in body |
|
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. |
|
Nov 1 |
asked | Save choice and execute later in pgfkeys? |
|
Oct 31 |
awarded | Popular Question |
|
Oct 29 |
awarded | Notable Question |
|
Oct 29 |
awarded | Enlightened |
|
Oct 29 |
awarded | Nice Answer |
|
Oct 20 |
awarded | Nice Answer |
|
Oct 20 |
awarded | Famous Question |
|
Oct 17 |
comment |
\dots versus \ldots - is there a difference?\dots is magic! ... when using amsmath ;-) |
|
Oct 17 |
awarded | Nice Question |
|
Oct 15 |
revised |
How can I use BibTeX to cite a web page? Added urldate for biblatex |
