From: Thien-Thi Nguyen <ttn@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: ignore-errors in XEmacs
Date: Wed, 25 Sep 2013 07:36:09 +0200 [thread overview]
Message-ID: <87eh8d799y.fsf@zigzag.favinet> (raw)
In-Reply-To: <jwv1u4ducwg.fsf-monnier+gnu.emacs.help@gnu.org> (Stefan Monnier's message of "Tue, 24 Sep 2013 17:31:26 -0400")
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
() Stefan Monnier <monnier@iro.umontreal.ca>
() Tue, 24 Sep 2013 17:31:26 -0400
> Is [ignore-errors] likewise built in w/ XEmacs?
I don't know about that, but I do recommend you carefully consider
each use: throwing all errors to /dev/null is sometimes the right
thing to do, but if errors really shouldn't happen (and yet, you
want to protect yourself from bugs in other packages), then it's
better to use something like with-demote-errors, so errors don't
get in the way but they aren't hidden under the carpet.
I agree in principle.
If it were my code i would have avoided ‘ignore-errors’ from the
beginning, but here i am trying to honor the intent of mic (as far as
i can deduce), so the indicated path is necessarily more circumspect.
(This is not an argument against your recommendation, btw.)
Anyway, in case anyone is interested, i think XEmacs 21.5, available
many years now but still "beta", has ‘ignore-errors’, but it requires
cl.el:
http://www.xemacs.org/Documentation/21.5/html/cl_14.html
(thus, NOT "built in"). If anyone knows otherwise, please correct me.
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-09-25 5:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2561.1379668126.10748.help-gnu-emacs@gnu.org>
2013-09-24 21:31 ` ignore-errors in XEmacs Stefan Monnier
2013-09-25 5:36 ` Thien-Thi Nguyen [this message]
2013-09-20 9:11 Thien-Thi Nguyen
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=87eh8d799y.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=help-gnu-emacs@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.