From: Jean Louis <bugs@gnu.support>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: daniela-spit@gmx.it, bug-gnu-emacs@gnu.org,
Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: org-capture user-error: Abort
Date: Sun, 13 Dec 2020 13:46:15 +0300 [thread overview]
Message-ID: <X9Xw98ueFBtQtnr/@protected.rcdrun.com> (raw)
In-Reply-To: <874kkq5d0n.fsf@localhost>
* Ihor Radchenko <yantar92@gmail.com> [2020-12-13 11:21]:
> Jean Louis <bugs@gnu.support> writes:
>
> > * daniela-spit@gmx.it <daniela-spit@gmx.it> [2020-12-12 23:19]:
> >> Emacs fires "user-error: Abort" after pressing "q" to abort org-capture.
> >
> > Those are error messages invented by programmers who never had any
> > project supervisor who thinks of users.
>
> (user-error "Action aborted") only prints "Action aborted".
Function is used wrongly. People do read source code.
(user-error FORMAT &rest ARGS)
Probably introduced at or before Emacs version 24.
Signal a user error, making a message by passing ARGS to ‘format-message’.
This is like ‘error’ except that a user error (or "pilot error") comes
from an incorrect manipulation by the user, not from an actual problem.
In contrast with other errors, user errors normally do not cause
entry to the debugger, even when ‘debug-on-error’ is non-nil.
This can be overridden by ‘debug-ignored-errors’.
Did user incorrectly manipulated anything? I don't think so.
There was definitely good intention to glue the things together and
make things function. But it was not made from viewpoint that software
will be used by people, maybe people read source code which is what we
want. Under certain condition that will come up as actual error, see
debug-ignored-errors.
Why tell to user that it was user error when it was not? It was one of
options.
Focus on technicality that causes the problem which does not fit
reasonably into human meanings. We like meanings, that is why we want
to fit meanings where they belong. Systems are not enough meaningful.
I can love my bicycle as I want, but it may not be usable by other
people due to all idiosyncratic enhancements I have made to it.
Jean
next prev parent reply other threads:[~2020-12-13 17:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 20:15 org-capture user-error: Abort daniela-spit
2020-12-13 1:07 ` Ihor Radchenko
2020-12-13 1:34 ` bug#45212: " daniela-spit
2020-12-13 1:39 ` daniela-spit
2020-12-13 2:51 ` Ihor Radchenko
2020-12-13 3:01 ` daniela-spit
2020-12-13 4:37 ` Ihor Radchenko
2020-12-13 5:16 ` daniela-spit
2020-12-13 5:46 ` Jean Louis
2020-12-13 8:55 ` Ihor Radchenko
2020-12-13 18:07 ` Diego Zamboni
2020-12-13 18:11 ` daniela-spit
2020-12-13 5:22 ` Jean Louis
2020-12-13 5:54 ` bug#45212: " daniela-spit
2020-12-13 8:24 ` Ihor Radchenko
2020-12-13 10:46 ` Jean Louis [this message]
2020-12-13 17:37 ` bug#45212: " Christopher Dimech
2020-12-13 8:25 ` Michael Albinus
2020-12-13 10:48 ` Jean Louis
2020-12-13 17:41 ` bug#45212: " daniela-spit
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X9Xw98ueFBtQtnr/@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=bug-gnu-emacs@gnu.org \
--cc=daniela-spit@gmx.it \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).