From: Stephen Berman <stephen.berman@gmx.net>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: sebastian_rose@gmx.de, 27879@debbugs.gnu.org
Subject: bug#27879: Bad behavior with sr-speedbar package
Date: Sun, 30 Jul 2017 21:55:10 +0200 [thread overview]
Message-ID: <877eypem3l.fsf@rosalinde> (raw)
In-Reply-To: <912f1be4-1d2c-1a97-5e3f-fbb0b1e004c9@alice.it> (Angelo Graziosi's message of "Sun, 30 Jul 2017 19:23:09 +0200")
On Sun, 30 Jul 2017 19:23:09 +0200 Angelo Graziosi <angelo.graziosi@alice.it> wrote:
> OK, I found the commit that causes this issue:
>
>
> committer Stephen Berman
> commit 8e394b082bd6ecd9ba212cb3ca07cbace66767a6
>
> Preserve point under 'dired-auto-revert-buffer' (third case)
> * lisp/files.el (find-file): Use pop-to-buffer-same-window
> instead of switch-to-buffer. This preserves Dired window
> point when dired-auto-revert-buffer is non-nil. (Bug#27243)
As Martin Rudalics noted, sr-speedbar advises pop-to-buffer. I executed
your recipe, but before calling sr-speedbar-toggle I deactivated the
advice (M-x ad-deactivate). This still creates a speedbar in the frame,
but now C-x C-f visits the file in the same window instead of splitting
the window. Whether other sr-speedbar functionality is impaired by not
advising pop-to-buffer, I don't know, but Martin's advice in surely
appropriate, and sr-speedbar should take it.
Steve Berman
next prev parent reply other threads:[~2017-07-30 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 14:56 bug#27879: Bad behavior with sr-speedbar package Angelo Graziosi
2017-07-30 17:23 ` Angelo Graziosi
2017-07-30 19:55 ` Stephen Berman [this message]
2017-07-30 18:38 ` martin rudalics
2017-07-30 21:43 ` Angelo Graziosi
2017-07-31 1:59 ` Glenn Morris
2017-07-31 11:13 ` Angelo Graziosi
2017-07-31 6:20 ` martin rudalics
2017-07-31 11:15 ` Angelo Graziosi
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=877eypem3l.fsf@rosalinde \
--to=stephen.berman@gmx.net \
--cc=27879@debbugs.gnu.org \
--cc=angelo.graziosi@alice.it \
--cc=sebastian_rose@gmx.de \
/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).