From: Stephen Berman <stephen.berman@gmx.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 25522-done@debbugs.gnu.org
Subject: bug#25522: 26.0.50; (hl-line-maybe-unhighlight): (error "Selecting deleted buffer")
Date: Sat, 28 Jan 2017 20:52:56 +0100 [thread overview]
Message-ID: <87vasz9d2f.fsf@rosalinde> (raw)
In-Reply-To: <87h94k26n0.fsf@web.de> (Michael Heerdegen's message of "Fri, 27 Jan 2017 10:29:07 +0100")
On Fri, 27 Jan 2017 10:29:07 +0100 Michael Heerdegen <michael_heerdegen@web.de> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> I think I found out what triggers the error: when you kill a buffer in
>> whose mode hl-line-mode is enabled and the mode of the next (now
>> current) buffer does not have hl-line-mode enabled, and then you change
>> (or Emacs changes) to another buffer in whose mode hl-line-mode is
>> enabled -- that raises the error. Can you confirm this?
>
> Could be. In my posted recipes, when I turn off hl-line-mode in the
> buffer I end up in, there is indeed no error. An experiment with three
> buffers as you described and switching manually to the third also
> confirms your assumption.
>
>> Just out of curiosity, because I think the above fix is good enough
>> and it's simple, so unless someone sees a problem with it, I'll commit
>> it to master.
>
> Yes, it's obvious that it isn't harmful.
>
>
> Thanks,
>
> Michael
Pushed as commit d12e1dd and closing the bug.
Steve Berman
prev parent reply other threads:[~2017-01-28 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 23:26 bug#25522: 26.0.50; (hl-line-maybe-unhighlight): (error "Selecting deleted buffer") Michael Heerdegen
2017-01-24 23:39 ` Michael Heerdegen
2017-01-25 12:16 ` Stephen Berman
2017-01-26 1:14 ` Michael Heerdegen
2017-01-26 1:21 ` Michael Heerdegen
2017-01-26 2:07 ` Michael Heerdegen
2017-01-26 9:54 ` Stephen Berman
2017-01-26 10:15 ` Michael Heerdegen
2017-01-26 19:45 ` Stephen Berman
2017-01-27 9:29 ` Michael Heerdegen
2017-01-28 19:52 ` Stephen Berman [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=87vasz9d2f.fsf@rosalinde \
--to=stephen.berman@gmx.net \
--cc=25522-done@debbugs.gnu.org \
--cc=michael_heerdegen@web.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).