From: grant@antiflux.org (Grant Hollingworth)
Subject: [sup-talk] [PATCH] keep buffer-list-mode up-to-date
Date: Wed, 21 Nov 2007 13:41:28 -0700 [thread overview]
Message-ID: <1195677515-sup-8177@spooky> (raw)
If you kill or create buffers, but leave buffer-list-mode open, the list of buffers will no longer be correct. If you then select a buffer that has been killed, Sup will crash at BufferManager.raise_to_front.
This patch just reloads the buffer list every time you switch back to it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sup-buffer-list-focus-reload.diff
Type: application/octet-stream
Size: 467 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071121/24fcd1c0/attachment.obj
next reply other threads:[~2007-11-21 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 20:41 Grant Hollingworth [this message]
2007-11-24 17:41 ` William Morgan
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=1195677515-sup-8177@spooky \
--to=grant@antiflux.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox