From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12387@debbugs.gnu.org, emacs18@gmail.com
Subject: bug#12387: 24.2.50; File column printed by list-buffers is bad if done in dired-mode
Date: Fri, 14 Sep 2012 11:00:31 +0200 [thread overview]
Message-ID: <5052F22F.1060804@gmx.at> (raw)
In-Reply-To: <83txv1vokl.fsf@gnu.org>
> IMO, that's exactly what needs to be done. The attempts to avoid
> calling set_buffer_internal_1 are a classical case of premature
> optimization, since that function already knows how to avoid changing
> to the same buffer.
Installed.
martin
next prev parent reply other threads:[~2012-09-14 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 15:50 bug#12387: 24.2.50; File column printed by list-buffers is bad if done in dired-mode emacs18
2012-09-13 7:52 ` Glenn Morris
2012-09-13 9:37 ` martin rudalics
2012-09-13 17:07 ` Eli Zaretskii
2012-09-14 9:00 ` martin rudalics [this message]
2012-09-14 17:08 ` Glenn Morris
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=5052F22F.1060804@gmx.at \
--to=rudalics@gmx.at \
--cc=12387@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacs18@gmail.com \
/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).