From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 26623@debbugs.gnu.org
Subject: bug#26623: 24.5; bad variable name: `inside-post-command-hook'
Date: Wed, 26 Apr 2017 18:37:08 +0300 [thread overview]
Message-ID: <83lgqnnpsr.fsf@gnu.org> (raw)
In-Reply-To: <07ad96c0-1fe7-4997-8607-837288075411@default> (message from Drew Adams on Wed, 26 Apr 2017 06:39:18 -0700 (PDT))
> Date: Wed, 26 Apr 2017 06:39:18 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 26623@debbugs.gnu.org
>
> This is a perversion, which works against users.
It can only work in a few exceptional cases, I agree. And I think
this is one such case. If this were wide-spread, then yes, we should
have done something about it.
> > I think the name of this variable speaks very clearly for its purpose,
> > and see no reason for such formalism in this case.
>
> No, it does not speak clearly for its purpose.
We disagree, that's all.
next prev parent reply other threads:[~2017-04-26 15:37 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>
2017-04-26 13:39 ` bug#26623: 24.5; bad variable name: `inside-post-command-hook' Drew Adams
2017-04-26 15:37 ` Eli Zaretskii [this message]
[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
2017-04-26 19:32 ` Eli Zaretskii
2017-05-10 2:10 ` npostavs
2017-05-10 6:25 ` Glenn Morris
2017-05-10 6:33 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lgqnnpsr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26623@debbugs.gnu.org \
--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.