Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
ots-doctools
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ots
ots-doctools
Commits
686676cf
Commit
686676cf
authored
1 year ago
by
Karl Fogel
Browse files
Options
Downloads
Patches
Plain Diff
Add \otsparenfullref, analogous to \otsparenref
parent
54d161ce
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
latex/ots.sty
+2
-1
2 additions, 1 deletion
latex/ots.sty
with
2 additions
and
1 deletion
latex/ots.sty
+
2
−
1
View file @
686676cf
...
...
@@ -252,10 +252,11 @@ trim=0cm 11cm 19.3cm 11cm, scale=0.09]{otslogo.pdf}}}
% could write "(\ref{sock}", but I trust I don't need to explain why
% that's not a pleasant thing to see in one's LaTeX source.
%
% Hence th
is
new command. The single left paren is still there, but
% Hence th
ese
new command
s
. The single left paren is still there, but
% at least it's isolated to the command definition so you won't see it
% when working with the LaTeX source text.
\newcommand
{
\otsparenref
}
[1]
{
(
\ref
{
#1
}}
\newcommand
{
\otsparenfullref
}
[1]
{
\otsparenref
{
#1
}
~``
\nameref
{
#1
}
''
}
% Create an indented, italicized, parenthesized green note.
%
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment