On Thu, Jun 03, 2021 at 12:03:04PM +0200, Augusto Stoffel wrote:
> On Thu, 3 Jun 2021 at 10:45, Patrice Dumas wrote:
>
> > On Tue, Jun 01, 2021 at 06:18:57PM +0200, Augusto Stoffel wrote:
> >>
> >> Moreover, the above is not due to any fundamental issue, but rather to
> >> the very prosaic prob
On Thu, 3 Jun 2021 at 10:45, Patrice Dumas wrote:
> On Tue, Jun 01, 2021 at 06:18:57PM +0200, Augusto Stoffel wrote:
>>
>> Moreover, the above is not due to any fundamental issue, but rather to
>> the very prosaic problem that Texinfo is missing a plain cross-reference
>> markup.
>
> I may be m
On Tue, Jun 01, 2021 at 06:18:57PM +0200, Augusto Stoffel wrote:
>
> Moreover, the above is not due to any fundamental issue, but rather to
> the very prosaic problem that Texinfo is missing a plain cross-reference
> markup.
I may be missing something, but it seems to me that @ref{} is more or
le
On 6/2/21 11:53 AM, Augusto Stoffel wrote:
However, generating HTML files that look okay on anything other than a
full-fledged browser is much harder than converting some documentation
source to info with Pandoc, Sphinx or the like.
I disagree. I think the output in eww is quite decent and
On Tue, 1 Jun 2021 at 11:38, Per Bothner wrote:
> On 6/1/21 5:23 AM, Eli Zaretskii wrote:
>> If we are after an Emacs-only solution,
>
> If we want an Emacs-only solution, why not use eww-mode on an HTML file?
> It works tolerably well - try: M-x eww ENTER https://domterm.org ENTER
> Viola - you
On 6/1/21 5:23 AM, Eli Zaretskii wrote:
If we are after an Emacs-only solution,
If we want an Emacs-only solution, why not use eww-mode on an HTML file?
It works tolerably well - try: M-x eww ENTER https://domterm.org ENTER
Viola - you're browsing a texinfo manual with rich text and images.
Of
> From: Augusto Stoffel
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Tue, 01 Jun 2021 18:18:57 +0200
>
> The point is that Texinfo is a perfectly capable system, but you can't
> convert documents made in other markup languages to Texinfo (and
> therefore Info) format. Consequentl
> From: Augusto Stoffel
> Date: Tue, 01 Jun 2021 18:15:25 +0200
> Cc: Texinfo
>
> > Of course you can invent new syntax but I really question if it is
> > worth it. For one thing, what if a node name contains a #?
>
> What if it contains "," or "."?
this is already documented as invalid, see "
On Tue, 1 Jun 2021 at 15:23, Eli Zaretskii wrote:
>> From: Augusto Stoffel
>> Date: Mon, 31 May 2021 22:38:30 +0200
>> Cc: Texinfo
>>
>> Emacs can be easily adapted to handle this new case in Info files:
>>
>> 1. "*note title: place." will remain being rendered as "see title.",
>> whe
On Mon, 31 May 2021 at 22:35, Gavin Smith wrote:
>> So I'll flesh out my suggestion a bit further. Define a new macro, say
>> @yref, which works as follows:
>
>> *Note Lightning: Electrical Effects#
>
> Of course you can invent new syntax but I really question if it is
> worth it. For one
> Sent: Wednesday, June 02, 2021 at 12:15 AM
> From: "Eli Zaretskii"
> To: "Augusto Stoffel"
> Cc: bug-texinfo@gnu.org
> Subject: Re: Unadorned cross-references
>
> > From: Augusto Stoffel
> > Cc: bug-texinfo@gnu.org
> > Date: Mon, 31 May
> From: Augusto Stoffel
> Date: Mon, 31 May 2021 22:38:30 +0200
> Cc: Texinfo
>
> Emacs can be easily adapted to handle this new case in Info files:
>
> 1. "*note title: place." will remain being rendered as "see title.",
> where the word "title" has the link face and a button to "place"
ike to suggest adding a command to Texinfo, as well as some
> >> markup in the .info file format, to create unadorned cross-references,
> >> that is, without the assumption that the cross reference fits in a
> >> phrase like "see such and such".
> >
> >
On Mon, May 31, 2021 at 9:38 PM Augusto Stoffel wrote:
> Well, yes, it _explains_ the issue. But why not solve the issue?
It explains why it is hard to solve the issue.
> > Yes, but how do I get a plain link, with no extra markup?
> >
> > You can't. Info is a plain text format that is dis
On Mon, 31 May 2021 at 19:05, Eli Zaretskii wrote:
>> From: Augusto Stoffel
>> Date: Mon, 31 May 2021 09:56:33 +0200
>>
>> I would like to suggest adding a command to Texinfo, as well as some
>> markup in the .info file format, to create unadorned cross-refer
On Mon, 31 May 2021 at 20:17, Gavin Smith wrote:
> This question comes up again and again and the following was added to
> the manual to address this. I hope it explains the issue.
Well, yes, it _explains_ the issue. But why not solve the issue?
> Yes, but how do I get a plain link, with no ex
> Sent: Tuesday, June 01, 2021 at 7:17 AM
> From: "Gavin Smith"
> To: "Augusto Stoffel"
> Cc: "Texinfo"
> Subject: Re: Unadorned cross-references
>
> This question comes up again and again and the following was added to
> the manual to ad
nt more, you are recommended to use the HTML output from
'texi2any' instead.
On Mon, May 31, 2021 at 3:06 PM Augusto Stoffel wrote:
>
> I would like to suggest adding a command to Texinfo, as well as some
> markup in the .info file format, to create unadorned cross-reference
> From: Augusto Stoffel
> Date: Mon, 31 May 2021 09:56:33 +0200
>
> I would like to suggest adding a command to Texinfo, as well as some
> markup in the .info file format, to create unadorned cross-references,
> that is, without the assumption that the cross reference fits
I would like to suggest adding a command to Texinfo, as well as some
markup in the .info file format, to create unadorned cross-references,
that is, without the assumption that the cross reference fits in a
phrase like "see such and such".
Currently, it seems to be more or less imp
20 matches
Mail list logo
