unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, stevey@google.com, 4041@debbugs.gnu.org
Subject: bug#4041: 23.0.92; Emacs 23: buffer point is no longer frame-local
Date: Sat, 08 Oct 2011 17:55:59 +0200	[thread overview]
Message-ID: <4E90728F.4010001@gmx.at> (raw)
In-Reply-To: <83r52nebv9.fsf@gnu.org>

 > How inconvenient can "M-x <up> RET" be?

Very because it's not auto-repeatable.

 >> In my experience, the buffer isn't too far away, usually.
 >
 > Maybe so, but I don't want to waste my time wading through buffers I
 > am not interested in.  If I need to see dispextern.h, I want to get
 > there, pronto.

It's not about "If I need to see dispextern.h".  It's about "If I need
to see the dispextern.h where I left off in the same window."

 >>  > What is necessary is a way to switch to a buffer by name and have the
 >>  > window remember its previous window-point.  If the buffer was never
 >>  > displayed in this window, "C-x b" should choose some value of
 >>  > window-point that was used before and is not already displayed in some
 >>  > other window.  (If there's a window for every possible value of
 >>  > window-point for the buffer, i.e. the user opens yet another window
 >>  > with the same buffer, just choose one of the values, e.g., the first
 >>  > or the last.)  For the important use case of having 2 windows with the
 >>  > same buffer, this strategy will do _exactly_ what the user wants.
 >>
 >> Using the window-point from some other window will be utterly
 >> disconcerting if you later want to display the buffer in _that_ other
 >> window.
 >
 > Are you talking about the rare case in parentheses?

No.  I was talking about choosing "some value of window-point that was
used before" when switching to a buffer that was not shown in the
selected window yet.  If you next switch to the buffer in the window
where window-point was stolen from, you get the window-point from yet
another window.

 > That's a marginal
 > use case.  Let's not destroy convenience in 90% of cases for the sake
 > of 10%.
 >
 >> Recording window-points of deleted windows to implement the "used
 >> before" approach might be expensive - these are markers into that
 >> buffer.
 >
 > So let's record only a few, up to a limit.  Again, having a lot of
 > such deleted windows is a rare case.

So we record only a few but `switch-to-prev-buffer' isn't good enough to
get you to your buffer quickly.

 >>  > Yes, but it works satisfactorily only if you switch between 2 buffers
 >>  > in the same window.  Switch to a third, and you are screwed.
 >>
 >> Try them.
 >
 > I did, before I responded.

If you have auto-repeatable bindings it works very well.  I use them for
quite some time now and never had any complaints from my side so far.

martin





  reply	other threads:[~2011-10-08 15:55 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05  0:17 bug#4041: 23.0.92; Emacs 23: buffer point is no longer frame-local Steve Yegge
2009-08-06  9:33 ` martin rudalics
2011-09-17  7:04 ` Lars Magne Ingebrigtsen
2011-09-17  8:43   ` martin rudalics
2011-09-18  8:03     ` Lars Magne Ingebrigtsen
2011-10-06 22:14     ` Lars Magne Ingebrigtsen
2011-10-07  7:07       ` martin rudalics
2011-10-07 10:46         ` Lars Magne Ingebrigtsen
2011-10-07 17:00           ` martin rudalics
2011-10-07 21:09             ` Steve Yegge
2011-10-08  6:23               ` Eli Zaretskii
2011-10-08  6:32                 ` Drew Adams
2011-10-08  6:23               ` Leo
2011-10-08 13:23               ` martin rudalics
2011-10-08 14:12                 ` Eli Zaretskii
2011-10-08 15:00                   ` martin rudalics
2011-10-08 15:34                     ` Eli Zaretskii
2011-10-08 15:55                       ` martin rudalics [this message]
2011-10-08 17:07                         ` Eli Zaretskii
2011-10-08 17:53                           ` martin rudalics
2011-10-08 20:35                             ` Eli Zaretskii
2011-10-09  8:33                               ` martin rudalics
2011-10-09 17:45                                 ` Eli Zaretskii
2011-10-10 12:57                                   ` martin rudalics
2011-10-11 12:45               ` Stefan Monnier
2011-10-12  0:35                 ` Steve Yegge
2011-10-12  1:19                   ` Stefan Monnier
2011-10-12  3:52                     ` Steve Yegge
2011-10-12  9:48                     ` martin rudalics
2011-10-12 13:11                       ` Stefan Monnier
2011-10-12 13:39                         ` Stefan Monnier
2011-10-12 14:25                           ` martin rudalics
2012-10-05 10:08                         ` martin rudalics
2012-10-10 10:22                           ` martin rudalics
2011-10-12  6:52                   ` 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=4E90728F.4010001@gmx.at \
    --to=rudalics@gmx.at \
    --cc=4041@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=stevey@google.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).