unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Oleksandr Gavenko <gavenkoa@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Reporting error to user...
Date: Mon, 04 Mar 2013 01:09:33 +0530	[thread overview]
Message-ID: <87k3po1de2.fsf@gmail.com> (raw)
In-Reply-To: <87fw0cmht6.fsf@gavenkoa.example.com> (Oleksandr Gavenko's message of "Sun, 03 Mar 2013 20:58:29 +0200")



Last couple of sentences down below may interest you.

,---- From (info "(elisp) Signaling Errors")
|
|  -- Function: user-error format-string &rest args
|      This function behaves exactly like `error', except that it uses
|      the error symbol `user-error' rather than `error'.  As the name
|      suggests, this is intended to report errors on the part of the
|      user, rather than errors in the code itself.  For example, if you
|      try to use the command `Info-history-back' (`l') to move back
|      beyond the start of your Info browsing history, Emacs signals a
|      `user-error'.  Such errors do not cause entry to the debugger,
|      even when `debug-on-error' is non-`nil'.  *Note Error
|      Debugging::.
|
`----

Oleksandr Gavenko <gavenkoa@gmail.com> writes:

> I wrote blogging program in Elisp and have to report errors to users (when
> required file not found or network authorisation failed).
>
> How to report error to users?
>
> I think that showing *Backtrace* buffer from '(error ...)' is not good way to
> do this (I have filling that such behavior indicates bug or "not yet
> implemented" condition in program).
>
> (message "...") is better but sometimes another modes hide minibufer text
> (like semantic when showing symbol type).
>
> Would like to hear suggestions...

-- 



  reply	other threads:[~2013-03-03 19:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03 18:58 Reporting error to user Oleksandr Gavenko
2013-03-03 19:39 ` Jambunathan K [this message]
2013-03-04 19:23   ` Oleksandr Gavenko
2013-03-05  4:51     ` Dmitry Gutov
2013-03-05 21:32       ` Oleksandr Gavenko

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k3po1de2.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=gavenkoa@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).