unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.com>,
	<1121@emacsbugs.donarmstrong.com>
Subject: bug#1121: 23.0.60; `buffer-list' returns buffers in wrong order
Date: Thu, 9 Oct 2008 09:10:25 -0700	[thread overview]
Message-ID: <00e401c92a29$8a57ded0$c2b22382@us.oracle.com> (raw)
In-Reply-To: <f7ccd24b0810090055y41b1c2ablcc8323d4539f7d2a@mail.gmail.com>

> > emacs -Q
> > (setq enable-recursive-minibuffers t)
> > (find-file "/dir/buf001.txt")
> > (find-file-other-frame "/dir/buf002.txt")
> > (switch-to-buffer-other-frame "buf001.txt")
> >
> > M-x M-: (buffer-list)
> 
> How are you running these commands?

Put them (after emacs -Q) in a buffer, visit the buffer, `eval-buffer'. But the
way you used will work also. The key, however, is the last line above: evaluate
(buffer-list) from the minibuffer - e.g. during M-x or C-x C-f. Use `M-x M-:',
not just `M-:'. (That was the point of setting `enable-recursive-minibuffers' to
t.)

The real use would be from a command bound to a key in a minibuffer keymap. If
it examines the `buffer-list' the result is very different in Emacs 23 from
Emacs 20, 21, and 22.

> I've done:
>  emacs -Q
>  M-: (setq enable-recursive-minibuffers t) <ENTER>
>  C-x f /dir/buf001.txt <ENTER>
>  C-x 5 f /dir/buf002.txt <ENTER>
>  C-x 5 b buf001.txt <ENTER>
>  M-: (buffer-list) <ENTER>
> 
> > This returns:
> > (#<buffer  *Minibuf-1*> #<buffer  *Minibuf-2*>
> >  #<buffer buf002.txt> #<buffer buf001.txt>...)
> >
> > In previous Emacs releases (e.g. 22.3) it returns this:
> > (#<buffer  *Minibuf-1*> #<buffer buf001.txt>
> >  #<buffer buf002.txt> ... #<buffer  *Minibuf-0*>...)
> 
> I get
> 
> (#<buffer buf001.txt> #<buffer  *Minibuf-1*> #<buffer buf002.txt>
> #<buffer *scratch*> #<buffer  *Minibuf-0*> ...)
> 
> M-x emacs-version
> 
> "GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-10-08 on JUANMAB"







  reply	other threads:[~2008-10-09 16:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49214515.6090300@gmx.at>
2008-10-08 19:00 ` bug#1121: 23.0.60; `buffer-list' returns buffers in wrong order Drew Adams
2008-10-09  7:55   ` Juanma Barranquero
2008-10-09 16:10     ` Drew Adams [this message]
2008-10-09 18:23       ` Juanma Barranquero
2008-10-10 15:08         ` martin rudalics
2008-10-10 15:36           ` Drew Adams
2008-10-10 15:42             ` martin rudalics
2008-10-10 16:03               ` Drew Adams
2008-10-10 18:22                 ` martin rudalics
2008-11-04  7:49                   ` martin rudalics
2008-11-04  9:16                     ` Juanma Barranquero
2008-11-04  9:56                       ` martin rudalics
2008-11-04 14:32                         ` Drew Adams
2008-11-17 10:30   ` bug#1121: marked as done (23.0.60; `buffer-list' returns buffers in wrong order) Emacs bug Tracking System

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='00e401c92a29$8a57ded0$c2b22382@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=1121@emacsbugs.donarmstrong.com \
    --cc=lekktu@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).