From: Richard Copley <rcopley@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 25735@debbugs.gnu.org
Subject: bug#25735: 26.0.50; url-retrieve errors are peculiar
Date: Thu, 16 May 2019 09:11:24 +0100 [thread overview]
Message-ID: <CAPM58ogucL2J6oKCK026nTXRVui7o9Aa4SqTAqumeYjBA1m7iw@mail.gmail.com> (raw)
In-Reply-To: <m3y337m4mi.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
On Thu, 16 May 2019 at 04:59, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Richard Copley <rcopley@gmail.com> writes:
>
> > If there's a way to use that data to format an error message,
> > it would be good to provide an example, or a "see info node X",
> > if it's a common idiom.
> >
> > I think usually if you're looking at a docstring it's because you
> > want to know how to use the function (as well as what it is for
> > and what exactly it does, which I think are covered in this case).
>
> Well, I think we should assume that people know what arguments `error'
> takes, and the structure of the error data is now documented correctly.
> So I think that should be sufficient.
>
OK. It's (error STRING &rest ARGS), by the way.
[-- Attachment #2: Type: text/html, Size: 1309 bytes --]
next prev parent reply other threads:[~2019-05-16 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 21:21 bug#25735: 26.0.50; url-retrieve errors are peculiar Richard Copley
2019-05-15 6:04 ` Lars Ingebrigtsen
2019-05-15 7:01 ` Richard Copley
2019-05-15 7:16 ` Lars Ingebrigtsen
2019-05-15 7:46 ` Lars Ingebrigtsen
2019-05-15 20:59 ` Richard Copley
2019-05-16 3:59 ` Lars Ingebrigtsen
2019-05-16 8:11 ` Richard Copley [this message]
2019-05-15 7:17 ` Lars Ingebrigtsen
2019-05-15 7:19 ` 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=CAPM58ogucL2J6oKCK026nTXRVui7o9Aa4SqTAqumeYjBA1m7iw@mail.gmail.com \
--to=rcopley@gmail.com \
--cc=25735@debbugs.gnu.org \
--cc=larsi@gnus.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.
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).