Tag Info

New answers tagged

2

There is package kvoptions-patch. It tries to be much more conservative than xkvltxp. It only assumes that there might be key=value pairs to protect the value part (from expansion, category code changes, ...). The following example works \RequirePackage{kvoptions-patch} \documentclass[myoption={val1,val2}]{article} \usepackage[backend=biber, ...


1

The glossaries package uses the xkeyval package to define the key=value options. The key family used by \printglossary is called printgloss, so you can define a new key using any of the xkeyval commands, such as \define@choicekey. The difficulty is how to interface the option with \printglossary. The \onecolumn part after the glossary can be achieved by ...


8

Not every key sets a value. A key can execute arbitrary code. If we look in tikz.code.tex then we see that when you invoke \tikzset{line width=2pt} then it doesn't set a value, it invokes \tikz@semiaddlinewidth{2pt}. This, in turn, expands to \tikz@addoption{\pgfsetlinewidth{2pt}}\pgfmathsetlength\pgflinewidth{2pt}. There are two things going on here. ...



Top 50 recent answers are included