From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Philippe Vaucher <philippe.vaucher@gmail.com>, 24555@debbugs.gnu.org
Subject: bug#24555: [PATCH] Remove unused variable `command-debug-status'
Date: Wed, 28 Sep 2016 20:16:26 -0400 [thread overview]
Message-ID: <jwvfuoj4l84.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83twczokd3.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 28 Sep 2016 23:11:20 +0300")
> In a nutshell, it's a variable provided for storing arbitrary data
> that persists for the duration of the current interactive command.
Can't think of any situation where I'd want/need that. The name seems
to indicate it could be used that way in the context of debugging, but
even in that kind of scenario I'm unable to come up with a use-case.
Stefan
next prev parent reply other threads:[~2016-09-29 0:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 12:39 bug#24555: [PATCH] Remove unused variable `command-debug-status' Philippe Vaucher
2016-09-28 14:58 ` Eli Zaretskii
2016-09-28 16:14 ` Stefan Monnier
2016-09-28 17:24 ` Philippe Vaucher
2016-09-28 20:11 ` Eli Zaretskii
2016-09-29 0:16 ` Stefan Monnier [this message]
2016-09-29 6:50 ` Philippe Vaucher
2016-09-29 15:04 ` Eli Zaretskii
2016-09-30 9:08 ` Philippe Vaucher
2016-10-01 13:09 ` Philippe Vaucher
2016-10-01 15:50 ` Eli Zaretskii
2016-10-01 16:12 ` Philippe Vaucher
2016-10-01 17:39 ` Eli Zaretskii
2016-10-02 17:08 ` Philippe Vaucher
2016-10-02 18:32 ` Noam Postavsky
2016-10-02 18:48 ` Philippe Vaucher
2016-10-02 19:41 ` Philippe Vaucher
2016-10-03 7:13 ` Eli Zaretskii
2016-10-03 7:37 ` Philippe Vaucher
2016-10-03 7:42 ` Philippe Vaucher
2016-10-04 14:43 ` Eli Zaretskii
2016-10-04 15:18 ` Philippe Vaucher
2016-10-04 15:46 ` Eli Zaretskii
2016-10-04 15:54 ` Philippe Vaucher
2016-09-28 20:05 ` Eli Zaretskii
2016-09-29 0:12 ` Stefan Monnier
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=jwvfuoj4l84.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=24555@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=philippe.vaucher@gmail.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.