all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Theodor Thornhill <theo@thornhill.no>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "Stefan Kangas" <stefan@marxist.se>,
	"Simen Heggestøyl" <simenheg@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: master 432c1aa: Use `pop-to-buffer-same-window' in `project-eshell'
Date: Sat, 20 Mar 2021 20:29:57 +0100	[thread overview]
Message-ID: <1BE350C3-A516-4752-8997-91C252F7E9AD@thornhill.no> (raw)
In-Reply-To: <833481ce-5f13-77d5-deef-8d9f0c51cdd4@yandex.ru>


>> When I first implemented those functions I made eshell behave more like shell, and also made shell behave more sensibly (to me... which also is the reason universal argument acts differently from mx shell). Right now I am thinking we should let display-buffer decide.
> 
> Meaning not use pop-to-buffer-same-window?
> 

Too often i feel emacs places buffers or windows in seemingly arbitrary places, destroying my window setup. To circumvent this, my default display-buffer behavior is to always reuse same window. If we make more and more parts of emacs decide this on their own, I have to add more and more edge cases to make emacs behave. 


>> Should we force one behavior over another?
> 
> FWIW, my (moderate) preference is Eshell's behavior because it's also consistent with IELM or Dired. And I use it more.
> 

Yeah, Im inclined to agree, though I dont think we should force it.

—
Theodor


  reply	other threads:[~2021-03-20 19:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210308115905.6593.76443@vcs0.savannah.gnu.org>
     [not found] ` <20210308115907.30AD520A10@vcs0.savannah.gnu.org>
2021-03-20  2:06   ` master 432c1aa: Use `pop-to-buffer-same-window' in `project-eshell' Stefan Kangas
2021-03-20 17:04     ` Dmitry Gutov
2021-03-20 17:21       ` Theodor Thornhill
2021-03-20 18:54         ` Dmitry Gutov
2021-03-20 19:29           ` Theodor Thornhill [this message]
2021-03-20 20:03             ` Dmitry Gutov
2021-03-20 20:21               ` Theodor Thornhill
2021-03-20 20:29                 ` Dmitry Gutov
2021-03-20 20:33                   ` Theodor Thornhill
2021-03-20 21:08                     ` Dmitry Gutov
2021-03-20 21:51                       ` Theodor Thornhill
2021-03-20 22:29                         ` Dmitry Gutov
2021-03-20 22:37                           ` Theodor Thornhill via Emacs development discussions.
2021-03-21  6:10                             ` Eli Zaretskii
2021-03-21  6:26                               ` Eli Zaretskii
2021-03-21  7:04                               ` Theodor Thornhill via Emacs development discussions.
2021-03-21 12:44                                 ` Dmitry Gutov
2021-03-20 22:10                   ` Juri Linkov
2021-03-21 19:47                     ` Dmitry Gutov
2021-03-20 17:31       ` Stefan Kangas
2021-03-20 18:55         ` Dmitry Gutov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1BE350C3-A516-4752-8997-91C252F7E9AD@thornhill.no \
    --to=theo@thornhill.no \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=simenheg@gmail.com \
    --cc=stefan@marxist.se \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.