From: Drew Adams <drew.adams@oracle.com>
To: Karl Fogel <kfogel@red-bean.com>, Leo Liu <sdl.web@gmail.com>
Cc: 15746@debbugs.gnu.org
Subject: bug#15746: 24.3; [PATCH] bookmark should confirm when overwrite
Date: Tue, 29 Oct 2013 19:26:27 -0700 (PDT) [thread overview]
Message-ID: <ba3a0de1-c8b7-4389-80d0-9afa6dae5aba@default> (raw)
In-Reply-To: <87iowg9bqw.fsf@floss.red-bean.com>
> I would probably also change the `user-error' behavior along the
> lines Drew suggested.
Uh, I did not suggest any change wrt the use of `user-error', here.
Unfortunately, it is the appropriate type of error to use in this case.
There has been abundant discussion of `user-error' in other threads.
Its meaning is not a user error. The meaning is any error except a
coding error, i.e., except something that the code never expects to
happen. That's OK as a category, perhaps, but it should not have the
name "user-error". But it does, and we live with it.
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11999#35
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15670#11
next prev parent reply other threads:[~2013-10-30 2:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 3:32 bug#15746: 24.3; [PATCH] bookmark should confirm when overwrite Leo Liu
2013-10-29 14:20 ` Drew Adams
2013-10-29 18:24 ` Karl Fogel
2013-10-29 20:09 ` Drew Adams
2013-10-29 20:51 ` Karl Fogel
2013-10-29 22:16 ` Drew Adams
2013-10-30 4:31 ` Karl Fogel
2013-10-30 14:07 ` Drew Adams
2013-10-30 2:11 ` Stefan Monnier
2013-10-30 2:35 ` Drew Adams
2013-10-30 2:56 ` Leo Liu
2013-10-30 3:14 ` Stefan Monnier
2013-10-30 3:36 ` Leo Liu
2013-10-30 3:57 ` Stefan Monnier
2013-10-30 14:07 ` Drew Adams
2013-10-30 18:17 ` Stefan Monnier
2013-10-30 1:28 ` Leo Liu
2013-10-30 2:26 ` Drew Adams [this message]
2015-11-08 19:27 ` bug#15746: Fix committed to master Karl Fogel
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=ba3a0de1-c8b7-4389-80d0-9afa6dae5aba@default \
--to=drew.adams@oracle.com \
--cc=15746@debbugs.gnu.org \
--cc=kfogel@red-bean.com \
--cc=sdl.web@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.