5,010 reputation
2834
bio website
location England
age
visits member for 1 year, 11 months
seen 9 hours ago

I've been using LaTeX since I started university 6 years ago, and grateful to everyone ever involved in the kernel, or in the various packages, distributions and websites, those who introduced me to it and those who answer related questions!

I'm following with interest the developments on LaTeX3 and also the alternative engines, which I hope to one-day be able to exploit more!


Jul
5
comment \autoref subsections in appendix
@RhysUlerich: Yes, but it is not as robust to new releases of hyperref. Simply find the definition \def\hyper@makecurrent in hyperref.sty, copy and paste in place of the \patchcmd and perform the replacement yourself. If you get stuck, let me know. There are also other packages providing commands that can do the same job as \patchcmd. Perhaps you could explain why it is that you wish to avoid etoolbox, as I understand that to be a fairly common and robust package?
Jul
2
awarded  Curious
Jun
26
comment What does “running in backwards compatibility mode” mean and what should I fix to get rid of it?
If you don't specify any compat then you get compat=default which is the same as pre 1.3. Obviously pgfplots cannot suggest a version newer than the version of the pgfplots package that is installed, but I don't know the specifics of how pgfplots suggests a version. Perhaps if there have been important bugfixes, it suggests newer versions even if it hasn't detected use of certain new features. If you want your document to look close to how it used to look, then find the date of the old document and try the latest pgfplots version that was available then!
Jun
26
comment What does “running in backwards compatibility mode” mean and what should I fix to get rid of it?
If the pgfplots manual doesn't help you, then I'm not sure I can either. The only time pgfplots guesses a version is when you request compat=newest and it tries to estimate which new features you are using and which you are not, to encourage you to request a specific version instead of newest. There have been some bugfixes etc that have not preserved compatibility, so loading compat=X may not be the same as loading version X of the package file as it was when released. For more help, I suggest that you start a new question with a MWE where someone more knowledgeable may find it.
Jun
11
comment Vertical loop/block lines in algorithmicx with 'noend' option
@CommuSoft: I was always aware of that problem, sorry that I seemed to neglect to mention it in my answer. I have posted an update that is probably the best I can do in regards to trying to solve that particular issue. Hope it is of some use.
Jun
11
revised Vertical loop/block lines in algorithmicx with 'noend' option
attempt to cope with taller lines
Jun
10
comment Vertical loop/block lines in algorithmicx with 'noend' option
@CommuSoft: Sorry, I am not quite sure what you have tried nor can I anticipate what might be the problem. Perhaps this would be worth a new question of its own?
Mar
30
revised standard order for bold+italic?
No such thing as \fontweight; \fontseries was meant
Mar
23
answered Back accent or grave accent in listings
Mar
12
answered Navigation circles shown for title page with patch for no-subsections
Mar
12
awarded  Necromancer
Feb
23
comment Vertical loop/block lines in algorithmicx with 'noend' option
@sazr: Yes, sorry, this solution does not work well in many cases. This is a due to both the \addvspace{-3pt} and the rule parameters height .75\baselineskip depth .25\baselineskip, which don't account for the actual height of the current line. Accounting for that is extremely difficult. I attempted to give a tikz/zref solution at Problems with vertical lines in algorithmicx but it is still not perfect and I'm unable to further improve it as I wouldn't know how.
Feb
22
comment Vertical loop/block lines in algorithmicx with 'noend' option
@sazr: Sounds like it might be a \makeatletter problem? Can you confirm that this MWE works for you? Would probably need a bit more to go on otherwise.
Jan
20
reviewed Approve suggested edit on Using latexdiff with git
Jan
8
awarded  Revival
Dec
13
answered \autoref subsections in appendix
Dec
6
revised Ploblems with vertical lines in algorithmicx
added 81 characters in body
Dec
6
answered Ploblems with vertical lines in algorithmicx
Dec
3
comment Is it a bad idea to use \begin{section} … \end{section} in LaTeX?
To complete Bruno's suggestion, one needs to add \advance\ss@sec\m@ne to \endrelsec (actually \endsect in Will's newsec package) before the \begingroup.
Dec
3
revised Viewer-independent copyable spaces at the beginning of a line?
improve clarity by adding note that Philippe's idea doesn't use real spaces