[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?
From: |
Eli Zaretskii |
Subject: |
bug#21305: 25.0.50; `get-buffer-window-list' doc - what order? |
Date: |
Fri, 21 Aug 2015 18:21:18 +0300 |
> Date: Fri, 21 Aug 2015 08:08:25 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 21305@debbugs.gnu.org
>
> > > > The order is unspecified, which means the caller should not
> > > > depend on it. I don't think there's anything wrong with that;
> > > > do you?
> > >
> > > Well, it's certainly the prerogative of designers to decide that
> > > the order is undefined and that users cannot depend on it. In
> > > that case, you can close the bug now.
> > >
> > > But as one user I'm disappointed. I was hoping for a usable
> > > window order.
> >
> > It's the order of traversing the window tree depth-first (as
> > described in the ELisp manual under "Cyclic Window Ordering").
>
> If so, then the order is not undefined.
I didn't say "undefined", I said "unspecified".
> > I don't see how saying that would be of any help to users of this
> > function.
>
> Well, it apparently won't help me in my quest for a chronological
> ordering of windows for the same buffer by access time.
>
> But I think it would be helpful to tell users that the order is
> the same as that described in `Cyclic Window Ordering'.
What can the users do with that information? (It is already in the
ELisp manual; I'm talking about the doc string here.)
> > Describing the order would require a non-trivial amount of text, so
> > without a good reason, I don't think we should add it.
>
> How is it more difficult than saying that the order is the same as
> that specified in `Cyclic Window Ordering', and xreffing that node?
I consider references to the manual in doc strings a bad habit.
I'm closing the bug.
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Drew Adams, 2015/08/20
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Eli Zaretskii, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Drew Adams, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Eli Zaretskii, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Drew Adams, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?,
Eli Zaretskii <=
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Drew Adams, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Eli Zaretskii, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Drew Adams, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, martin rudalics, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Drew Adams, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, martin rudalics, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Drew Adams, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Drew Adams, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Drew Adams, 2015/08/21
- bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?, Drew Adams, 2015/08/21