unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre-Yves Luyten <py@luyten.fr>
To: martin rudalics <rudalics@gmx.at>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Emacs-devel <emacs-devel-bounces+py=luyten.fr@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: Documenting buffer display
Date: Tue, 23 Oct 2018 13:26:43 +0200	[thread overview]
Message-ID: <9d49eb351c5c1fa93cfde20bcffb116c@luyten.fr> (raw)
In-Reply-To: <5BCEE2B5.9090205@gmx.at>

Le 2018-10-23 10:58, martin rudalics a écrit :

> 
> An earlier approach to provide such behavior was to add functions like
> 'find-dired-other-window' and 'find-dired-other-frame' maybe with
> appropriate key bindings.  The shortcomings of that approach are:
> 
> (1) The number of predefined functions to display a buffer is usually
>     tripled.
> 
> (2) The user may have to memorize key bindings for three functions
>     instead of one.
> 
> (3) These three functions still do not cover the entire spectrum of
>     behaviors users want like showing the buffer on a specific side of
>     the selected window or frame.
> 

Looks to me above shortcomings list assumes user always want (1) to 
invoke the same behavior, ie always use other-frame or always 
other-windows,  or (2) to customize behavior regarding specific buffers 
(buffer names).

While i rather assume user wants to invoke specific action based on the 
context. for example while working on email i would invoke other-frame ; 
while working on markdown i would most often call other-window, both for 
the same bookmark or the same file.

Regards
Pierre-Yves



  reply	other threads:[~2018-10-23 11:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-20 12:20 Documenting buffer display martin rudalics
2018-10-20 13:21 ` Eli Zaretskii
2018-10-20 18:02   ` martin rudalics
2018-10-21 12:56     ` Eli Zaretskii
2018-10-22  9:06       ` martin rudalics
2018-10-22 13:55         ` Eli Zaretskii
2018-10-22 19:14           ` martin rudalics
2018-10-22 19:27             ` Eli Zaretskii
2018-10-23  8:58               ` martin rudalics
2018-10-23 11:26                 ` Pierre-Yves Luyten [this message]
2018-10-23 13:45                   ` martin rudalics
2018-10-23 17:40                   ` Stefan Monnier
2018-10-23 14:04                 ` Drew Adams
2018-10-23 18:18                   ` martin rudalics
2018-10-23 15:18                 ` Eli Zaretskii
2018-10-23 18:23                   ` martin rudalics
2018-10-23 19:07                     ` Eli Zaretskii
2018-10-24  9:44                       ` martin rudalics
2018-10-24 14:48                         ` Eli Zaretskii
2018-10-24 17:40                           ` martin rudalics
2018-10-24 18:25                             ` Eli Zaretskii
2018-10-25 20:42                             ` Juri Linkov
2018-10-23 15:52                 ` Alan Mackenzie
2018-10-23 18:25                   ` martin rudalics
2018-11-08 19:25                   ` martin rudalics
2018-10-22  1:39   ` Michael Welsh Duggan
2018-10-22  5:54     ` Eli Zaretskii
2018-10-20 15:22 ` Drew Adams
2018-10-20 18:02   ` martin rudalics
2018-10-20 18:24     ` Drew Adams
2018-10-21  8:22       ` martin rudalics
2018-11-04  9:06 ` martin rudalics

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=9d49eb351c5c1fa93cfde20bcffb116c@luyten.fr \
    --to=py@luyten.fr \
    --cc=eliz@gnu.org \
    --cc=emacs-devel-bounces+py=luyten.fr@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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).