Jonathan Leech-Pepin writes:
> For @xref{} I would need to know if it was at the start of a sentence and
> followed
> by a comma or period.
> For @pxref{} I would need to determine if it was at end of sentence,
> mid sentence followed by a comma or within parentheses, and not preceeded by
> "see
Hello
On 25 February 2013 16:48, Subhan Tindall wrote:
> I don't think there is a specific context that can clearly separate
> them. The differences are largely semantic, not syntactic. What is
> needed is some sort of marker on the tag in the original file telling
> it what kind of link is to b
Hello
On 25 February 2013 16:34, Subhan Tindall wrote:
> I noticed you left out @inforef, was that by design? It actually does
> behave quite differently than other members of the @*ref family, and
> the more arguments it gets the more different it looks IE Here's an
> example with a full 5 argu
I don't think there is a specific context that can clearly separate
them. The differences are largely semantic, not syntactic. What is
needed is some sort of marker on the tag in the original file telling
it what kind of link is to be used.
On Mon, Feb 25, 2013 at 1:38 PM, Nicolas Goaziou wrote
Hello,
Jonathan Leech-Pepin writes:
> I had to compare these possible outcomes when working on the texinfo
> exporter. Since links are parsed before being included in their
> paragraphs, I did not have a way to obtain context and therefore
> attempt to guess (and be successful) at which type of
I noticed you left out @inforef, was that by design? It actually does
behave quite differently than other members of the @*ref family, and
the more arguments it gets the more different it looks IE Here's an
example with a full 5 arguments:
REF *note Arg2: (Arg4)Lore Ipsum.
INFOREF *note Arg2: (Arg
(Here are the attached files, forgot to add them)
On 25 February 2013 15:24, Jonathan Leech-Pepin <
jonathan.leechpe...@gmail.com> wrote:
> Hello,
>
> On 25 February 2013 14:01, Subhan Tindall
> wrote:
>
>> The point being that compiling .texinfo source into an Info file
>> treats references dif
The point being that compiling .texinfo source into an Info file
treats references differently. For example:
(@pxref{my_node_name}). will compile just fine.
(@ref{my_node_name}). will not. There are also differences in case
(see v. See, note v. Note), and differences in output by ref type
dependi
Hello,
On 25 February 2013 13:40, Subhan Tindall wrote:
> There are 4 different ref commands, all with slightly syntactic
> requirements and outputs when compiled using makeinfo. I for one use
> @pxref{} a lot, and it has different requirements for placement than
> @ref or @xref (namely those tw
There are 4 different ref commands, all with slightly syntactic
requirements and outputs when compiled using makeinfo. I for one use
@pxref{} a lot, and it has different requirements for placement than
@ref or @xref (namely those two MUST have a . or , following the end
of the ref)
8.1 Different C
Hello Tom,
On 25 February 2013 12:52, Thomas S. Dye wrote:
> Aloha all,
>
> IIUC, there is currently no support for @pxref{} in the texinfo
> exporter. This is a texinfo @-command that does one thing in the info
> output and another in the LaTeX output.
>
Ultimately there is actually no real d
Aloha all,
IIUC, there is currently no support for @pxref{} in the texinfo
exporter. This is a texinfo @-command that does one thing in the info
output and another in the LaTeX output.
My idea is to create a custom link type, something like this:
(org-add-link-type
"pxref" nil
(lambda (
12 matches
Mail list logo
