As a postscript to my previous post
\newcommand{\SeeOnly}[2]{\index{#1@\protect\adjtext{#1}|seeonly{#2}}}
where \seeonly and \adjtext are as previously, does all that is aked of it.
The other way to get rid of the offending text-following comma is to use an index style (.ist) file containing ...
Search found 8 matches
- Fri Dec 21, 2012 4:53 pm
- Forum: MakeIndex, Nomenclature, Glossaries and Acronyms
- Topic: modified "see" command adds spurious page number
- Replies: 17
- Views: 18352
- Thu Dec 20, 2012 9:20 pm
- Forum: MakeIndex, Nomenclature, Glossaries and Acronyms
- Topic: modified "see" command adds spurious page number
- Replies: 17
- Views: 18352
modified "see" command adds spurious page number
Murraye wrote
No, your code produces an unwanted comma in the index entry for "additive identity", between "additive identity" and the parenthesized reference "(see zero elements)".
Murraye you are quite correct. The original post did not mention an unwanted comma (,) after the index entry ...
No, your code produces an unwanted comma in the index entry for "additive identity", between "additive identity" and the parenthesized reference "(see zero elements)".
Murraye you are quite correct. The original post did not mention an unwanted comma (,) after the index entry ...
- Thu Dec 20, 2012 4:30 pm
- Forum: MakeIndex, Nomenclature, Glossaries and Acronyms
- Topic: modified "see" command adds spurious page number
- Replies: 17
- Views: 18352
modified "see" command adds spurious page number
I have just seen your query today while investigating MakeIndex myself.
Is not your error to use \seeonly rather than |seeonly inside the \index parameter?
The following works well for me.
\documentclass{article}
\newcommand{\seeonly}[2]{(\emph{see} #1)}
\usepackage{makeidx}\makeindex ...
Is not your error to use \seeonly rather than |seeonly inside the \index parameter?
The following works well for me.
\documentclass{article}
\newcommand{\seeonly}[2]{(\emph{see} #1)}
\usepackage{makeidx}\makeindex ...
- Sat Nov 17, 2012 7:23 pm
- Forum: WinEdt
- Topic: Corrupted dvi2pdf output
- Replies: 0
- Views: 3509
Corrupted dvi2pdf output
I am using LaTeX in WinEdt v. 5.5 configured for MixTex 2.9 and Adobe Reader v. 8.3 running under Windows XP. This setup has been stable for a good number of years.
I have a source including EPS figures. DVI and PS outputs are fine. Using the dvi2pdf incorporated feature of WinEdt (which uses ...
I have a source including EPS figures. DVI and PS outputs are fine. Using the dvi2pdf incorporated feature of WinEdt (which uses ...
- Fri Sep 09, 2011 2:42 pm
- Forum: General
- Topic: Scope of a Command Declaration
- Replies: 6
- Views: 17475
Re: Scope of a Command Declaration
In the first paragraph of my reply to frabjous everything after the first sentence is based upon a misinterpretation of his post and should therefore be ignored. I apologise to him and others for this careless error. On the other hand frabjois' post did not answer my question fully and in consquence ...
- Fri Sep 09, 2011 12:16 pm
- Forum: General
- Topic: Scope of a Command Declaration
- Replies: 6
- Views: 17475
Scope of a Command Declaration
Thank you Frabjous for your response.
You write "To make a new command local …". The point is I don’t want to make the command \firstmacro local but use of the command name \temp to be local to command \firstmacro. In your code, \firstmacro does not run on calling \secondmacro. I want it to run but ...
You write "To make a new command local …". The point is I don’t want to make the command \firstmacro local but use of the command name \temp to be local to command \firstmacro. In your code, \firstmacro does not run on calling \secondmacro. I want it to run but ...
- Wed Sep 07, 2011 7:33 pm
- Forum: General
- Topic: Scope of a Command Declaration
- Replies: 6
- Views: 17475
Scope of a Command Declaration
Nicola thank you for taking an interest in my question. I note and understand what you write. It is, however, not altogether relevant to my question. At least I think not.
Here is a MWE of the sort of thing I want to be able to avoid happening.
\documentclass{minimal}%
%
\begin{document ...
Here is a MWE of the sort of thing I want to be able to avoid happening.
\documentclass{minimal}%
%
\begin{document ...
- Tue Sep 06, 2011 3:21 pm
- Forum: General
- Topic: Scope of a Command Declaration
- Replies: 6
- Views: 17475
Scope of a Command Declaration
Is the declaration of a command necessarily global to a document or can it be made local to a command (macro) which uses (calls?) it?
Here is a typical scenario schematically
\newcommand{\firstmacro}[…]%
{%
…
\newcommand{\temp}{…}%
…
\renewcommand{\temp}{…}%
…
}%
\newcommand{\secondmacro ...
Here is a typical scenario schematically
\newcommand{\firstmacro}[…]%
{%
…
\newcommand{\temp}{…}%
…
\renewcommand{\temp}{…}%
…
}%
\newcommand{\secondmacro ...