From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com>,
21032@debbugs.gnu.org
Subject: bug#21032: package.el acts pecularly
Date: Sun, 12 Jul 2015 09:06:23 +0100 [thread overview]
Message-ID: <CAAdUY-+iQ4CdFJqw+ePtBBwBJGQpfX8Th636jcCr8s1iN2mMKw@mail.gmail.com> (raw)
In-Reply-To: <jwvwpy6w1pt.fsf-monnier+emacsbugs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
On Jul 12, 2015 3:28 AM, "Stefan Monnier" <monnier@iro.umontreal.ca> wrote:
>
> > The 404 error is so well known that I'm not too worried about confusing
the
> > user.
>
> No, 404 is not well-known enough. I for one have no idea which kind of
> error this is (other than "the host itself was OK since got a reply, but
> the file part of the URL lead to some kind of problem", and I wouldn't
> assume every user to know that much).
Actually, I think in that instance it was the server part that led to the
problem. However, I _think_ package.el (or url.el) doesn't have the
information to say that. That is, we would get the same error whether it's
an issue in the server part or the file part, wouldn't we?
Anyway, like I said, I'm fine with improving the error message. I just
meant I prefer the message to still say 404 somewhere (or whatever the
error code was).
[-- Attachment #2: Type: text/html, Size: 1095 bytes --]
next prev parent reply other threads:[~2015-07-12 8:06 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 [this message]
2015-07-12 15:03 ` Stefan Monnier
2015-07-12 15:16 ` Artur Malabarba
2015-07-12 5:37 ` Vaidheeswaran C
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=CAAdUY-+iQ4CdFJqw+ePtBBwBJGQpfX8Th636jcCr8s1iN2mMKw@mail.gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=21032@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=vaidheeswaran.chinnaraju@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).