meta user
network profile
| bio | website | igm.univ-mlv.fr/~alabarre |
|---|---|---|
| location | Belgium | |
| age | 31 | |
| visits | member for | 2 years, 9 months |
| seen | 19 hours ago | |
| stats | profile views | 63 |
Don't really know what to say, but have a look at what I'm currently working on: http://harpy.sourceforge.net/
I'll be more talkative when inspiration strikes me ;-)
|
May 14 |
accepted | Forbidding keywords in listings |
|
May 14 |
comment |
Forbidding keywords in listings "The keyword is float without dot, not float. (...)": yes, but the one with the dot was the one I wanted to remove. Other than that, the literate trick works perfectly, thanks! |
|
May 14 |
asked | Forbidding keywords in listings |
|
May 8 |
comment |
Automated removal of unneeded packages Thanks, this seems like a good option. |
|
Apr 15 |
comment |
Make one author's name bold every time it shows up in the bibliography Works great, thanks! (although bold fonts seem to be ignored when using \textsc or \sc, but that might be related to something else I do in my bst) |
|
Apr 14 |
comment |
Reusing the current argument's number with xparse @JosephWright: then I suppose my question shows you how shallow my knowledge of the inner workings of a LaTeX package is ;-) |
|
Apr 11 |
accepted | Reusing the current argument's number with xparse |
|
Apr 11 |
comment |
Reusing the current argument's number with xparse Thanks, I'll try using that. Of course, if I were really interested in a list, I'd use enumerate (and would actually have no use for xparse), but I just wanted a simple example to work on. I actually need this feature to draw things using TikZ. |
|
Apr 11 |
asked | Reusing the current argument's number with xparse |
|
Nov 28 |
awarded | Popular Question |
|
Oct 16 |
comment |
Crossing out sentences I tried both solutions, and my preference goes to ulem because its \sout command can handle "special" characters (such as é, è, à, ...) commonly used in some languages, whereas \st fails. |
|
Sep 21 |
awarded | Popular Question |
|
Sep 5 |
comment |
Highlighting specific lines with lstinputlisting Thanks, I missed it. I'm voting to close my question as an exact duplicate. |
|
Sep 5 |
comment |
Highlighting specific lines with lstinputlisting Thanks, but not good enough for me, the terms I would highlight also appear elsewhere in the source code and I really need a single line to be highlighted. |
|
Sep 5 |
asked | Highlighting specific lines with lstinputlisting |
|
Aug 4 |
awarded | Yearling |
|
Aug 1 |
awarded | Nice Question |
|
Jun 8 |
awarded | Constituent |
|
Jun 8 |
awarded | Caucus |
|
Dec 20 |
comment |
cleveref gets names wrong when using the SIAM document class I'm considering it, but I'm currently hesitating between that and simply dropping cleveref when the manuscript is ready, because I'm not sure the folks at SIAM will be too happy about a submission that redefines their macros (I know other publishers aren't, at least). Thanks for your suggestion anyway. |
