unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Steve Schooler <sgschooler@gmail.com>
Cc: 33424-done@debbugs.gnu.org
Subject: bug#33424: pop-to-buffer-same-window in emacs 26-1
Date: Tue, 20 Nov 2018 17:47:59 +0200	[thread overview]
Message-ID: <831s7fkaxc.fsf@gnu.org> (raw)
In-Reply-To: <CAOxkcC6T_d6EfvsX4fGREik8qAQ_xk8OL1c9E8zX88QLqGh2zQ@mail.gmail.com> (message from Steve Schooler on Mon, 19 Nov 2018 13:18:53 -0800)

[Please use "Reply to All" to reply to these messages, otherwise you
are only replying to myself.]

> From: Steve Schooler <sgschooler@gmail.com>
> Date: Mon, 19 Nov 2018 13:18:53 -0800
> 
> Thank you very much for the thorough analysis.  I just installed the latest version of neotree, and the behavior
> of emacs 26-1 is just as you described.  This covers most but (perhaps) not all of the bug-issue that I
> suspected.  
> 
> I thought that I had also noticed unusual behavior, where (sometimes) opening a file would result in splitting
> the current frame into 2 windows, rather than dedicating the entire frame to the new file.  Unfortunately, I could
> not detect a pattern to this, so I can not report a reproducible situation, EXCEPT FOR ONE THING.
> 
> Suppose that you re-create the situation where at the end of your emacs initialization, you use the find-file
> command to load a few files, then use the neotree command.  You would then be simulating the tail end of my
> initialization.
> 
> Suppose that immediately after emacs comes up, you take the <menu><buffer> menu option to display the
> list of (some of ) the buffers.  If you then mouse-select one of these buffers, the frame will split into two
> windows.  I suspect that this is BECAUSE the pop-to-buffer-same-window function is REGARDING THE
> FRAME AS BELONGING TO NEOTREE.
> 
> This is just a heads-up.  You might reasonably construe this to NOT BE A BUG.  If so, then I think the
> bug-ticket can be closed.  However, this may serve as a warning that in some situations,
> pop-to-buffer-same-window will behave unusually, based on who pop-to-buffer-same-window believes is the
> "owner" of the frame.

If you invoke find-file from the menu bar with the neotree's directory
in the selected window, you will always see this behavior, because
find-file is unable to reuse the selected window, due to its being
dedicated to the neotree buffer.

I'm therefore closing the bug.





      parent reply	other threads:[~2018-11-20 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-18 23:54 bug#33424: pop-to-buffer-same-window in emacs 26-1 Steve Schooler
2018-11-19 15:59 ` Eli Zaretskii
     [not found]   ` <CAOxkcC6T_d6EfvsX4fGREik8qAQ_xk8OL1c9E8zX88QLqGh2zQ@mail.gmail.com>
2018-11-20 15:47     ` Eli Zaretskii [this message]

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=831s7fkaxc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33424-done@debbugs.gnu.org \
    --cc=sgschooler@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).