From: Mekeor Melire <mekeor@posteo.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 68970@debbugs.gnu.org
Subject: bug#68970: 30.0.50; Info.el: Info-url-alist should support format-sequence that encodes "Top" node as "index"
Date: Wed, 07 Feb 2024 19:52:15 +0000 [thread overview]
Message-ID: <87bk8s3usi.fsf@posteo.de> (raw)
In-Reply-To: <867cjgz5rm.fsf@gnu.org>
2024-02-07 16:51 eliz@gnu.org:
> Sorry, I don't think I understand: "https://example.com/" stands for
> "https://example.com/index.html", AFAIK. This is why %e produces an
> empty string for the Top node. So why would users want to specify
> "https://example.com/%e.html" instead of just "https://example.com/%e"?
>
> IOW, I don't see why users will need to use the .html extension in the
> alist, it works without the extension.
>
> What am I missing?
Let's assume we have a manual with "Top" node as well as a node called
"Foo". Let's further assume the webserver is configured so that
example.com/Foo does not resolve to example.com/Foo.html but rather
results in "not found". This is why the user must choose to use
example.com/%e.html as URL-specification currently. But then they have
the problem that the "Top" node is translated to example.com/.html.
I suggested to add another format-sequence, %i, that translates the
"Top" node as "index". Thus, example.com/%i.html would translate to
example.com/index.html in case of "Top".
We could also instead provide a format-sequence, %s, that includes the
".html" suffix -- except in case of the "Top" node which would be
translated to the empty string. Thus, the user would use example.com/%s.
"Foo" would be translated to example.com/Foo.html; and "Top" would be
translated to "example.com/".
next prev parent reply other threads:[~2024-02-07 19:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 13:27 bug#68970: 30.0.50; Info.el: Info-url-alist should support format-sequence that encodes "Top" node as "index" Mekeor Melire
2024-02-07 14:51 ` Eli Zaretskii
2024-02-07 19:52 ` Mekeor Melire [this message]
2024-02-07 20:18 ` Eli Zaretskii
2024-02-07 22:10 ` Mekeor Melire
2024-02-08 6:26 ` Eli Zaretskii
2024-02-08 20:20 ` Mekeor Melire
2024-02-09 7:02 ` Eli Zaretskii
2024-02-09 22:00 ` bug#68970: [PATCH] In Info-url-alist, add .html extension to %e format-sequence Mekeor Melire
2024-02-10 7:46 ` Eli Zaretskii
2024-02-10 13:16 ` Mekeor Melire
2024-02-10 13:56 ` Eli Zaretskii
2024-02-10 22:41 ` bug#68970: [PATCH v2] " Mekeor Melire
2024-02-11 7:27 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bk8s3usi.fsf@posteo.de \
--to=mekeor@posteo.de \
--cc=68970@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.