From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 34678@debbugs.gnu.org
Subject: bug#34678: 26.1; (elisp) `Minor Mode Conventions'
Date: Wed, 27 Feb 2019 11:22:40 -0800 (PST) [thread overview]
Message-ID: <7d09ffca-fcce-425f-b271-012842276714@default> (raw)
In-Reply-To: <<83r2btjazx.fsf@gnu.org>>
> > It also wouldn't hurt to add a reference to node
> > `Minor Mode Conventions' from node `Major Mode
> > Conventions'.
> >
> > Perhaps add a mention in node `Major Mode Conventions'
> > similar to this one in (elisp) `Minor Mode Conventions':
> >
> > In addition, several major mode conventions
> > apply to minor modes as well: those regarding
> > the names of global symbols, the use of a hook
> > at the end of the initialization function, and
> > the use of keymaps and other tables.
>
> I don't see why: cross-references don't have to be symmetrical.
Did someone say that cross-references have to be
symmetrical?
> We refer to another node for details of something mentioned in passage,
> but that other node doesn't have to provide a cross-reference back.
Did someone say that it had to?
next parent reply other threads:[~2019-02-27 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<e63063dd-58cd-4dc6-b8de-3b23ce4ccc6d@default>
[not found] ` <<54960e92-89bb-40b1-ba82-1dbd7ff21b03@default>
[not found] ` <<83r2btjazx.fsf@gnu.org>
2019-02-27 19:22 ` Drew Adams [this message]
2019-02-27 19:56 ` bug#34678: 26.1; (elisp) `Minor Mode Conventions' Eli Zaretskii
2019-02-28 16:48 ` Richard Stallman
2019-03-02 22:35 ` Noam Postavsky
[not found] <<<e63063dd-58cd-4dc6-b8de-3b23ce4ccc6d@default>
[not found] ` <<<54960e92-89bb-40b1-ba82-1dbd7ff21b03@default>
[not found] ` <<<83r2btjazx.fsf@gnu.org>
[not found] ` <<7d09ffca-fcce-425f-b271-012842276714@default>
[not found] ` <<83pnrdj99c.fsf@gnu.org>
2019-02-27 20:51 ` Drew Adams
2019-02-27 18:56 Drew Adams
2019-02-27 19:09 ` Drew Adams
2019-02-27 19:18 ` Eli Zaretskii
2019-03-01 10: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=7d09ffca-fcce-425f-b271-012842276714@default \
--to=drew.adams@oracle.com \
--cc=34678@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.