From: Andreas Schwab <schwab@linux-m68k.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 7291@debbugs.gnu.org
Subject: bug#7291: 24.0.50; `non-essential' is incomprehensible
Date: Fri, 29 Oct 2010 10:36:16 +0200 [thread overview]
Message-ID: <m362wls8e7.fsf@hase.home> (raw)
In-Reply-To: <jwvr5fagkg2.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 28 Oct 2010 16:12:16 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Honestly, I can't think of any way someone who has the least bit of
> familiarity with Elisp can wonder "whether `non-essential'=nil or
> `non-essential'=t means performing a non-essential task (whatever that
> in turn might mean)".
The variable is badly named. It should be using a positive form, like
allow-whatever.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-10-29 8:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 22:30 bug#7291: 24.0.50; `non-essential' is incomprehensible Drew Adams
2010-10-28 0:52 ` Stefan Monnier
2010-10-28 16:22 ` Drew Adams
2010-10-28 17:14 ` Stefan Monnier
2010-10-28 18:43 ` Michael Albinus
2010-10-28 18:51 ` Drew Adams
2010-10-28 20:12 ` Stefan Monnier
2010-10-28 21:58 ` Drew Adams
2010-10-29 16:20 ` Stefan Monnier
2010-10-29 16:47 ` Drew Adams
2010-10-29 17:36 ` Stefan Monnier
2010-10-29 8:36 ` Andreas Schwab [this message]
2010-10-29 16:03 ` Stefan Monnier
2010-10-29 16:21 ` Andreas Schwab
2010-10-29 18:29 ` Eli Zaretskii
2010-10-29 23:00 ` Andy Moreton
2010-10-30 6:52 ` Eli Zaretskii
2010-10-30 16:16 ` Drew Adams
2010-10-30 17:53 ` Michael Albinus
2010-10-30 20:05 ` Drew Adams
2010-10-29 18:56 ` Alan Mackenzie
2010-10-28 17:33 ` James Cloos
2010-10-28 18:53 ` Drew Adams
2011-07-14 14:35 ` Lars Magne Ingebrigtsen
2010-10-31 2:34 ` MON KEY
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=m362wls8e7.fsf@hase.home \
--to=schwab@linux-m68k.org \
--cc=7291@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.