From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 26623@debbugs.gnu.org
Subject: bug#26623: 24.5; bad variable name: `inside-post-command-hook'
Date: Wed, 26 Apr 2017 10:19:33 -0700 (PDT) [thread overview]
Message-ID: <48339b7a-7888-4712-8ce7-3cc395117ce8@default> (raw)
In-Reply-To: <<83lgqnnpsr.fsf@gnu.org>>
> > > I think the name of this variable speaks very clearly for its purpose,
> >
> > No, it does not speak clearly for its purpose.
Reasons given elided, not addressed.
> We disagree, that's all.
No reasons given.
Ever use an `apropos' command on variables whose names end in
`-hook'? Do you expect to see only hook variables for that?
Ever use regexp-matching completion with `C-h v' for `-hook$'?
Do you expect to see only hook variables for that?
Is there an actual reason why you will not add a suffix (or
make another suitable name change) to indicate clearly that
this is not a hook variable?
next parent reply other threads:[~2017-04-26 17:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<88ab0589-09f2-496d-aa02-553ab60d1d58@default>
[not found] ` <<<83h91bpw7w.fsf@gnu.org>
[not found] ` <<07ad96c0-1fe7-4997-8607-837288075411@default>
[not found] ` <<83lgqnnpsr.fsf@gnu.org>
2017-04-26 17:19 ` Drew Adams [this message]
2017-04-26 19:32 ` bug#26623: 24.5; bad variable name: `inside-post-command-hook' Eli Zaretskii
2017-05-10 2:10 ` npostavs
2017-05-10 6:25 ` Glenn Morris
2017-05-10 6:33 ` Glenn Morris
[not found] <<88ab0589-09f2-496d-aa02-553ab60d1d58@default>
[not found] ` <<83h91bpw7w.fsf@gnu.org>
2017-04-26 13:39 ` Drew Adams
2017-04-26 15:37 ` Eli Zaretskii
2017-04-23 17:00 Drew Adams
2017-04-26 5:35 ` Eli Zaretskii
2017-04-26 17:18 ` Richard Stallman
2017-04-26 18:42 ` Eli Zaretskii
2017-04-27 10:19 ` Richard Stallman
2017-05-20 23:16 ` npostavs
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=48339b7a-7888-4712-8ce7-3cc395117ce8@default \
--to=drew.adams@oracle.com \
--cc=26623@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).