Completion, navigation, and refactoring

Complete in the right context#

In the workshop’s introduction, try completion after \ref{, \cite{, or \begin{. Candidates should reflect the active document’s labels, reachable bibliography, and known environments.

\newcommand{\projectname}{Authoring workshop}
\section{Methods}\label{sec:methods}
\projectname{} follows Section~\ref{sec:introduction}.

Navigate from \projectname to its definition and from the label reference to its target. Find Usages shows supported references before you rename a declaration. Labels, citations, commands, environments, packages, and included files have different reference contexts; a plain text search does not distinguish them.

Inspect parameters and docs#

Invoke Parameter Info inside a command such as \href{...}{...} or \includegraphics[...]{...}. Quick Documentation describes known signatures and packages. LaTeX: Open Package Documentation uses local texdoc when available for authoritative installed-package documentation.

Package intelligence combines bundled metadata with configured distribution indexing. Locally declared commands take precedence where they can be resolved. Static analysis does not expand arbitrary TeX macros or unusual category-code changes.

Rename one concept#

Rename sec:introduction in the workshop, inspect its usages, and apply. The results chapter’s reference should follow. Repeat with knuth1984 in the .bib file to see citation updates, then undo.

For an include-file move or rename, inspect relative \input paths and root comments together. Keep source and generated output directories separate so generated files are not mistaken for a second source tree.

Review unknown-command warnings#

Check that a required package is declared and the correct main file is selected. A missing-package quick fix can add a known package to the preamble; the generated editor action does not silently install a TeX package. Confirm with a real build after accepting it.