From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>
Cc: 'Joost Kremers' <joostkremers@fastmail.fm>, 14191-done@debbugs.gnu.org
Subject: bug#14191: 24.3.50; (buffer-list) returns list with non-current buffer as its firstelement
Date: Mon, 15 Apr 2013 09:10:59 +0200 [thread overview]
Message-ID: <516BA803.3050506@gmx.at> (raw)
In-Reply-To: <F2ECCAC220B847348941E8355F1782D0@us.oracle.com>
> But `record-window-buffer' is apparently quite a bit more than just
> (select-window (selected-window)).
More and less, I think.
> Should `record-window-buffer' be used in its place at this occurrence? If not,
> should another function be defined to do only (select-window (selected-window))
> - essentially an alias to better communicate the intention?
>
> You're the expert here, not I. My feeling is just that using (select-window
> (selected-window)) to take advantage of a less-than-obvious side effect is
> obfuscating, not clever or wise.
>
> Without an informative alias for this action, the code really needs to be
> commented to indicate the unobvious intention/effect, at the least. But is
> probably better to have a function name & doc string communicate this than code
> comments and bug reports.
As Andreas already remarked, the behavior of Emacs in this regard was
never clearly documented. Unfortunately, I don't know more about its
"unobvious intention/effect" than you.
martin
next prev parent reply other threads:[~2013-04-15 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 12:34 bug#14191: 24.3.50; (buffer-list) returns list with non-current buffer as its first element Joost Kremers
2013-04-12 17:32 ` Stefan Monnier
2013-04-12 17:51 ` bug#14191: 24.3.50; (buffer-list) returns list with non-current buffer as its firstelement Drew Adams
2013-04-13 8:02 ` martin rudalics
2013-04-13 15:08 ` Drew Adams
2013-04-15 7:10 ` martin rudalics [this message]
2013-04-12 18:59 ` bug#14191: 24.3.50; (buffer-list) returns list with non-current buffer as its first element Andreas Schwab
2013-04-14 12:46 ` Joost Kremers
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=516BA803.3050506@gmx.at \
--to=rudalics@gmx.at \
--cc=14191-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=joostkremers@fastmail.fm \
/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).