GNU bug report logs -
#13339
24.3.50; doc of `next-frame'
Previous Next
Reported by: "Drew Adams" <drew.adams <at> oracle.com>
Date: Wed, 2 Jan 2013 18:59:02 UTC
Severity: minor
Found in version 24.3.50
Fixed in version 28.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #11 received at 13339 <at> debbugs.gnu.org (full text, mbox):
"Drew Adams" <drew.adams <at> oracle.com> writes:
> The doc (both doc string and Elisp manual) is unclear for the default
> case where argument MINIFRAME/MINIBUF is nil. (BTW, the same parameter
> name should be used here for the doc string and the manual.)
>
> What is unclear is which frames are _included_ in this case. The only
> thing we are told is that minibuffer-only frames are _excluded_. Does
> that mean that all other frames are included? Or only visible frames?
> Or only visible or iconified frames?
>
> Other values of this argument make clear which frames are included, but
> the doc for a nil value of the argument is incomplete.
Uhm... yeah... clear. >"?
Do you have a suggestion as to what the nil case should say?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
This bug report was last modified 3 years and 275 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.