From: Ed Reingold <edward.reingold@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Printer definition
Date: Fri, 6 May 2011 15:19:36 -0700 (PDT) [thread overview]
Message-ID: <d1370633-24e8-4277-92ef-249aff6e7f43@24g2000yqk.googlegroups.com> (raw)
In-Reply-To: jwvei4b239x.fsf-monnier+gnu.emacs.help@gnu.org
On May 6, 11:40 am, Stefan Monnier <monn...@iro.umontreal.ca> wrote:
> > The best thing would be to trap the error (the way it does with pr)
> > and signal the user.
>
> I don't know what trapping you're referring to.
I meant that when pr fails, the failure message gets printed (in my
debugging
I got the the flags wrong once time, which is how I discovered that).
I think that anytime call-process-region (or similar) is called and
fails, the failure
should sent on to the user.
prev parent reply other threads:[~2011-05-06 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 19:10 Printer definition Ed Reingold
2011-05-03 15:10 ` Ed Reingold
2011-05-04 0:50 ` Stefan Monnier
2011-05-06 0:26 ` Ed Reingold
2011-05-06 16:40 ` Stefan Monnier
2011-05-06 22:19 ` Ed Reingold [this message]
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=d1370633-24e8-4277-92ef-249aff6e7f43@24g2000yqk.googlegroups.com \
--to=edward.reingold@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).