From: Evgeny Roubinchtein <zhenya1007@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Alan Mackenzie <acm@muc.de>, 24891@debbugs.gnu.org
Subject: bug#24891: 25.1: Falsehood on page "Major Modes" of Emacs manual.
Date: Sun, 6 Nov 2016 18:55:29 -0500 [thread overview]
Message-ID: <CAGYXaSa=b_Mj6BAkse3_vOX6HzNgdvd8c1iii09fewAou8tx5A@mail.gmail.com> (raw)
In-Reply-To: <71941c5f-0c6c-4edd-99ab-134cf6fdce96@default>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Is it the case that the modes that do run prog-mode-hook are exactly the
modes derived from prog-mode?
On Sun, Nov 6, 2016 at 6:19 PM, Drew Adams <drew.adams@oracle.com> wrote:
> > In the Emacs manual, page "Major Modes" appears the following:
> >
> > all programming language modes run `prog-mode-hook', prior to
> > running their own mode hooks.
> >
> > I suggest amending this sentence to something like:
> >
> > many programming language modes (including all these distributed
> > with Emacs) run `prog-mode-hook', prior to runnuing their own
> > mode hooks.
>
> +1.
>
> But: these -> those,
> runnuing -> running,
> and we can drop the comma before "prior".
>
> And I'm not sure why we need to or should say "(including...)". Why?
>
> I'd suggest just this:
>
> many programming language modes run `prog-mode-hook' before
> running their own mode hooks
>
> Or even "some" instead of "many". What does it matter how
> many do this?
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1553 bytes --]
next prev parent reply other threads:[~2016-11-06 23:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 22:18 bug#24891: 25.1: Falsehood on page "Major Modes" of Emacs manual Alan Mackenzie
2016-11-06 23:19 ` Drew Adams
2016-11-06 23:55 ` Evgeny Roubinchtein [this message]
2016-11-07 20:29 ` Alan Mackenzie
2016-11-07 20:39 ` Alan Mackenzie
2016-11-07 20:51 ` Drew Adams
2016-11-07 22:14 ` Alan Mackenzie
2016-11-07 0:05 ` Dmitry Gutov
2016-11-07 14:43 ` Richard Stallman
2016-11-07 19:46 ` Alan Mackenzie
2016-11-07 22:03 ` Alan Mackenzie
2016-11-10 21:26 ` Alan Mackenzie
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='CAGYXaSa=b_Mj6BAkse3_vOX6HzNgdvd8c1iii09fewAou8tx5A@mail.gmail.com' \
--to=zhenya1007@gmail.com \
--cc=24891@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=drew.adams@oracle.com \
/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.