9:46 AM
@ClaudioFiandrino I've just pushed the latest code to launchpad and that included the tikzmark_example.pdf file. Also refactored the highlighting - please test!

10:34 AM
@AndrewStacey sure :)
but for the moment I still see the revision 167 of 2012-11-27 10:14:33 UTC

11:03 AM
I have a basic question (really basic): am I missing something? When I try this simple document:

\documentclass[a4paper]{article}
\usepackage{tikz}
\usetikzlibrary{tikzmark}
\usetikzmarklibrary{highlight}
\begin{document}
text
\end{document}
I get: ! Undefined control sequence.l.4 \usetikzmarklibrary I've installed the library in my personal tree as a usual package.

Bother! I committed the code but didn't push it. Oops. I'll fix that later today. The command is \usetikzmarkextra Do you think that "library" would be better?

11:28 AM
I think "library" is more in the TikZ spirit. :) But I've used \usetikzmarklibrary because I found it in the doc: "Some of these have been gathered into extra libraries that are loaded via \usetikzmarklibrary."

I've just pushed the code to launchpad. Sorry about that. Yes, probably "library" is what folk would expect.

@AndrewStacey I've seen it (also the tikzmark_example.pdf).

11:48 AM
BTW: just a curiosity about the shadings (after the question tex.stackexchange.com/questions/85743/… ); I've seen in tikz.code.tex that when defining \tikz@finish the shading is actually disabled:
\iftikz@mode@shade%
\pgfsyssoftpath@getcurrentpath\tikz@temppath
\pgfprocessround{\tikz@temppath}{\tikz@temppath}% change the path
\pgfsyssoftpath@setcurrentpath\tikz@temppath%
\fi%
@ClaudioFiandrino The reason for that is that there are actually two places where the shading might occur, depending on what other options are set (patterns is the key, I think). So if the first works then the second mustn't and the \tikz@mode@shadefalse is to ensure that that happens - note that that assignment is local to the path group so doesn't apply to anything other than the current path.
@AndrewStacey I asked because I've seen \tikz@finish when is defined \tikz@fig@continue; after that transformations are applied to the nodes it is called, so I didn't understand why all operations (shading comprise) do not "switch off" automatically.