From: Amin Bandali <aminb@gnu.org>
To: Van L <van@scratch.space>, Bob Proulx <bob@proulx.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: shorter URL for to docs
Date: Sat, 04 Aug 2018 10:21:26 -0400 [thread overview]
Message-ID: <87sh3ujjq1.fsf@aminb.org> (raw)
In-Reply-To: <CCC6FFE3-C61E-4BCE-8656-EF7FCF9A0FEA@scratch.space>
Van L <van@scratch.space> writes:
>>> Is there a chance for the docs' URL to be shorter? compare the following.
>>>
>>> http://mathworld.wolfram.com/Integer.html
>>> https://www.gnu.org/software/emacs/manual/html_node/elisp/Integer-Type.html
>>
>> Not really. You can use "s" instead of "software" but that is about
>> it. That "s" part is really meant as a typing aide and little more.
>> It isn't meant to be used as a canonical name for the page.
>>
>> https://www.gnu.org/s/emacs/manual/html_node/elisp/Integer-Type.html
>
> That's too bad. I had my fingers crossed for
>
> https://emacs.gnu.org/elisp/Integer-Type.html
Indeed, as Bob said, the /s/ seems to be the only shorthand
currently available. But I agree that having shorter urls would
be nice.
I'll raise this with webmasters@ and see if we could maybe set up
redirects like these for GNU package manuals:
https://man.gnu.org/pkgname/node/* → https://www.gnu.org/s/pkgname/manual/html_node/*
https://man.gnu.org/pkgname/mono/* → https://www.gnu.org/s/pkgname/manual/html_mono/*
https://man.gnu.org/pkgname/* → https://www.gnu.org/s/pkgname/manual/*
A subdomain per package might make sense too (as in your example
for emacs), though it'll require more work (either manual or
automatic DNS updates) and may not scale too well.
-amin
prev parent reply other threads:[~2018-08-04 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 10:04 shorter URL for to docs Van L
2018-08-04 1:47 ` Bob Proulx
2018-08-04 7:42 ` Van L
2018-08-04 14:21 ` Amin Bandali [this message]
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=87sh3ujjq1.fsf@aminb.org \
--to=aminb@gnu.org \
--cc=bob@proulx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=van@scratch.space \
/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.