From: Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com>
To: bruce.connor.am@gmail.com
Cc: 21032@debbugs.gnu.org
Subject: bug#21032: package.el acts pecularly
Date: Sun, 12 Jul 2015 11:07:04 +0530 [thread overview]
Message-ID: <55A1FD00.3060700@gmail.com> (raw)
In-Reply-To: <CAAdUY-+Mju_4JTHYAkDUHUtME2WrOdqgZhsqH4vJSWA7T20VwA@mail.gmail.com>
On Sunday 12 July 2015 04:28 AM, Artur Malabarba wrote:
>> Error contacting: http://blah.blah.blah:/archive-contents
>> error in process filter: peculiar error: 404 [2 times]
> The second error is saying that the page was not found.
Removing the second error and rewording the first error is good enough
for me. Actually speaking, there is no "second" error. There is only
one error.
The peculiar error is coming from `edebug-report-error'. I really
think that user doesn't care much about the "innermost" errors. So,
catching such errors and re-throwing it is a good idea. Even if one
(as a developer) wants to see the "inner" errors, the *Messages*
should reflect the "innerness" of the fact by (say) parenthesizing it.
> I imagine other things that can happen are request time-out and
> certificate issues.
(The following pertains to url-http and may not concern package.el)
One way to handle the 404 (or for that matter any error) is to replace
it with it's string counterpart in `url-http-codes'. If the error
code takes a "parameter", we can also convert entries like this:
(404 not-found "Not found")
to
(404 not-found "%s Not found")
etc.
next prev parent reply other threads:[~2015-07-12 5:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 6:49 bug#21032: package.el acts pecularly Vaidheeswaran C
2015-07-11 10:21 ` Artur Malabarba
2015-07-11 19:20 ` Vaidheeswaran C
2015-07-11 22:58 ` Artur Malabarba
2015-07-12 2:28 ` Stefan Monnier
2015-07-12 8:06 ` Artur Malabarba
2015-07-12 15:03 ` Stefan Monnier
2015-07-12 15:16 ` Artur Malabarba
2015-07-12 5:37 ` Vaidheeswaran C [this message]
2015-07-12 8:09 ` Artur Malabarba
2022-02-08 7:28 ` Lars Ingebrigtsen
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=55A1FD00.3060700@gmail.com \
--to=vaidheeswaran.chinnaraju@gmail.com \
--cc=21032@debbugs.gnu.org \
--cc=bruce.connor.am@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.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).