From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 10144@debbugs.gnu.org
Subject: bug#10144: 24.0.91; `pop-up-frames' with dedicated windows is broken: `C-x C-f'
Date: Mon, 28 Nov 2011 09:25:41 -0800 [thread overview]
Message-ID: <A0C3506E540E48929C73E7EDE549B55F@us.oracle.com> (raw)
In-Reply-To: <jwvlir0chgo.fsf-monnier+emacs@gnu.org>
> >> You mean in Emacs-23 only.
> > No, I meant in all Emacs versions prior to 24 (with my setup).
^^^^^^^^^^^^^^^
> > And in 24 too, back when Martin's code was used.
>
> I can't imagine how that could be the case: find-file has always used
> switch-to-buffer and switch-to-buffer in Emacs<23 never did anything
> else than use the selected window (and hence fail in minibuffer-only
> frames and dedicated windows).
Did you actually read my mail? Did you read the part about this being the case
for _my setup_ but not for emacs -Q? Did you see where I show my redefinition
of `switch-to-buffer'?
That's the point of my clarification in that message: the new problem was with
my setup only, and I suspect (seems pretty clear, but untested) that it is due
to my not doing the same thing for Emacs 24 as I do for other versions. I used
different code for 24 because, prior to some recent change in Emacs (?), Emacs
24 (unlike previous versions) DTRT _without_ my needing that tweak to
`switch-to-buffer' for dedicated windows.
> > What's the point of such an error message when Emacs could DTRT and
> > show the user the buffer s?he asked to see?
>
> The user decided to use RET rather than `o', so the user explicitly
> indicated that she wants to display the buffer in the selected window
> rather than in another window. So it's not obvious that displaying
> the buffer in another window is the right thing to do.
I agree that such should be a user choice - it's not obvious a priori what the
best thing to do is.
IOW, let users choose what Emacs should do when there is an attempt to show
another buffer in a dedicated window: raise an error or use another window. To
me (from long use), the latter is a much better behavior, but I agree that users
should be able to decide.
I still ask the general question: What good is such an error? What am I
missing? For instance, why would you, as one user, prefer faising the error to
displaying the buffer in another window? I know you're used to the error
behavior, but why, given the choice, would you actually prefer it?
> OTOH I do agree that find-file is not quite like switch-to-buffer, in
> that the indication "use current window" is not as clear cut.
`find-file' is just one example. The point of my redefinition of
`switch-to-buffer' (besides fitting the frame) is to use another window when the
target window is dedicated.
To me that makes sense, and I've used it for a very long time now, with no
problems. I will, as I said, try to adjust my code so it works for Emacs 24
too.
I haven't had a chance yet to check this and make that change, but assuming I'm
right about the cause of the problem then (a) you can close this bug (please
wait for me to confirm my supposition), but (b) please consider a user option to
let users get the behavior I expect: use another window when the target window
is dedicated.
next prev parent reply other threads:[~2011-11-28 17:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 18:27 bug#10144: 24.0.91; `pop-up-frames' with dedicated windows is broken: `C-x C-f' Drew Adams
2011-11-26 19:14 ` martin rudalics
2011-11-26 19:26 ` Drew Adams
2011-11-27 10:41 ` martin rudalics
2011-11-27 14:17 ` Drew Adams
2011-11-28 4:37 ` Stefan Monnier
2011-11-28 13:33 ` martin rudalics
2011-11-28 16:56 ` Stefan Monnier
2011-11-28 17:01 ` Drew Adams
2011-11-28 19:40 ` Stefan Monnier
2011-11-29 10:48 ` martin rudalics
2011-11-29 14:03 ` Stefan Monnier
2011-11-29 10:48 ` martin rudalics
2011-11-29 14:04 ` Stefan Monnier
2011-11-28 15:30 ` Drew Adams
2011-11-28 17:07 ` Stefan Monnier
2011-11-28 17:25 ` Drew Adams [this message]
2011-11-28 19:45 ` Stefan Monnier
2011-11-29 5:26 ` Chong Yidong
2011-11-29 14:01 ` Stefan Monnier
2011-11-30 18:22 ` Drew Adams
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=A0C3506E540E48929C73E7EDE549B55F@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=10144@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).