all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: emacs-pretest-bug@gnu.org, 2792@emacsbugs.donarmstrong.com
Subject: bug#2792: 23.0.90; doc string of switch-to-buffer
Date: Thu, 26 Mar 2009 17:53:03 -0700	[thread overview]
Message-ID: <000901c9ae76$62f33610$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <jwvtz5f7r24.fsf-monnier+emacsbugreports@gnu.org>

> From: Stefan Monnier Sent: Thursday, March 26, 2009 5:23 PM
> > Get rid of the word "WARNING" in the doc string. This is 
> > just helpful information, not a warning. Warnings are for
> > things that are inherently dangerous.
>  
> It's inherently dangerous, in the sense that if I see a call to
> `switch-to-buffer' in some Elisp code, I know it's a bug (the counter
> examples are so rare they're not worth mentioning).

No, danger has nothing to do with this.

Knowing that something is a bug is not knowing that there is a danger. A bug
does not imply danger. Using "WARNING" for something that is not a warning
dilutes its meaning.

Use stronger language, if you like. Say, even, that it is most likely a bug to
use it in Lisp code (or even a "****BUG!!!!****", if you're really so inclined).
But don't use "WARNING".

Use "WARNING" when you know that it is used in code that controls trains on the
same track or nuclear missiles or anthrax tests. ;-)







  reply	other threads:[~2009-03-27  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 20:39 bug#2792: 23.0.90; doc string of switch-to-buffer Drew Adams
2009-03-27  0:23 ` Stefan Monnier
2009-03-27  0:53   ` Drew Adams [this message]
2009-03-27  1:02   ` Drew Adams

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='000901c9ae76$62f33610$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=2792@emacsbugs.donarmstrong.com \
    --cc=emacs-pretest-bug@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.