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 #17 received at 13339 <at> debbugs.gnu.org (full text, mbox):
"Drew Adams" <drew.adams <at> oracle.com> writes:
> 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?
Looking at the code, it's absolutely all frames on that terminal. I've
now adjusted the doc string and the manual.
"Drew Adams" <drew.adams <at> oracle.com> writes:
> BTW, the doc of `other-frame' says that it includes _visible_ frames.
> And its code calls `next-frame' with a nil value for argument
> MINIFRAME. So if the doc of `other-frame' is correct then the
> `next-frame' with nil MINIFRAME must include only visible frames, not
> all frames except minibuffer-only frames and not all visible or
> iconified frames except minibuffer-only frames.
I haven't dug into the code history here, but the code today says:
(while (> arg 0)
(setq frame (next-frame frame))
(while (and (not (eq frame sframe))
(not (eq (frame-visible-p frame) t)))
(setq frame (next-frame frame)))
(setq arg (1- arg)))
So the doc string of `other-frame' is correct.
--
(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.