From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, 19421@debbugs.gnu.org
Subject: bug#19421: 25.0.50; doc string of `browse-url' must describe parameter ARGS
Date: Sun, 27 Dec 2015 08:55:18 -0800 (PST) [thread overview]
Message-ID: <9b7eea53-ecf4-47f8-b153-9d80ac3557a0@default> (raw)
In-Reply-To: <<83h9j3ho5r.fsf@gnu.org>>
>> > I fail to see how it is called interactively, since it is not a
> > command - it has no `interactive' spec.
>
> It describes what will happen with the functions it calls, depending
> on the platform. Those functions do have an interactive spec.
That is something entirely different from "when called interactively".
Such language is quite misleading. At least it misled and confused me.
And is this doc string really the place to describe that? (I don't
say that it is not, but certainly such info is secondary to describing
this function and its own arguments.)
> > And it refers to an "optional second argument NEW-WINDOW", but
> > the lambda list is (URL &rest ARGS), and the doc string in no
> > way introduces NEW WINDOW in terms of those parameters.
>
> Please look at the current sources, you are talking about stuff I
> changed already.
OK great. Please ignore any such ignorance. I was referring to
the state before your changes, which I have not seen.
prev parent reply other threads:[~2015-12-27 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 23:06 bug#19421: 25.0.50; doc string of `browse-url' must describe parameter ARGS Drew Adams
2014-12-20 23:49 ` Drew Adams
2015-12-25 19:02 ` Lars Ingebrigtsen
2015-12-25 23:07 ` Drew Adams
2015-12-26 9:11 ` Eli Zaretskii
[not found] ` <<8db0a3c8-08b4-40c3-93a8-23ec9fcd8174@default>
[not found] ` <<83bn9dk208.fsf@gnu.org>
2015-12-26 16:40 ` Drew Adams
2015-12-26 18:53 ` Eli Zaretskii
[not found] ` <<<8db0a3c8-08b4-40c3-93a8-23ec9fcd8174@default>
[not found] ` <<<83bn9dk208.fsf@gnu.org>
[not found] ` <<41cee0e8-d5b7-4b6d-8f5b-314c01142f3a@default>
[not found] ` <<8337uphwi4.fsf@gnu.org>
2015-12-26 22:19 ` Drew Adams
2015-12-27 16:06 ` Eli Zaretskii
[not found] ` <<<<8db0a3c8-08b4-40c3-93a8-23ec9fcd8174@default>
[not found] ` <<<<83bn9dk208.fsf@gnu.org>
[not found] ` <<<41cee0e8-d5b7-4b6d-8f5b-314c01142f3a@default>
[not found] ` <<<8337uphwi4.fsf@gnu.org>
[not found] ` <<10972dc0-33fa-4ff0-974e-96156500da7f@default>
[not found] ` <<83h9j3ho5r.fsf@gnu.org>
2015-12-27 16:55 ` Drew Adams [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=9b7eea53-ecf4-47f8-b153-9d80ac3557a0@default \
--to=drew.adams@oracle.com \
--cc=19421@debbugs.gnu.org \
--cc=eliz@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).