From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: broken link in documentation
Date: Mon, 09 Mar 2020 20:48:33 +0200 [thread overview]
Message-ID: <835zfdbbzy.fsf@gnu.org> (raw)
In-Reply-To: <87k13t9xmn.fsf@ebih.ebihd> (message from Emanuel Berg via Users list for the GNU Emacs text editor on Mon, 09 Mar 2020 19:44:16 +0100)
> Date: Mon, 09 Mar 2020 19:44:16 +0100
> From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
>
> The link here
>
> https://www.gnu.org/software/emacs/manual/html_node/elisp/Keymaps-and-Minor-Modes.html
>
> to "Definition of minor-mode-map-alist", or
>
> https://www.gnu.org/software/emacs/manual/html_node/elisp/Definition-of-minor_002dmode_002dmap_002dalist.html#Definition-of-minor_002dmode_002dmap_002dalist
>
> seems to be br0ken.
Broken in what way?
next prev parent reply other threads:[~2020-03-09 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 18:44 broken link in documentation Emanuel Berg via Users list for the GNU Emacs text editor
2020-03-09 18:48 ` Eli Zaretskii [this message]
2020-03-09 20:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-03-09 21:31 ` Michael Heerdegen
2020-03-10 9:29 ` Colin Baxter
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835zfdbbzy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).