From: grant@antiflux.org (Grant Hollingworth)
Subject: [sup-talk] [PATCH] mode.focus not called when buffer killed
Date: Thu, 29 Nov 2007 10:50:36 -0500 [thread overview]
Message-ID: <1196351158-sup-2243@spooky.local> (raw)
In-Reply-To: <1196270440-sup-7754@south>
Excerpts from William Morgan's message of Wed Nov 28 12:21:59 -0500 2007:
> Applied, thanks.
I noticed that you used 'focus_on buf' instead of 'focus_on @buffers.last'. I assumed that if @buffers.last.force_to_top? was true, that you'd want to focus on the last buffer instead of the one just moved to @buffers[-2]. Or do you just want to make sure that the force_to_top buffer stays at the end of @buffers?
next prev parent reply other threads:[~2007-11-29 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 22:18 Grant Hollingworth
2007-11-28 17:21 ` William Morgan
2007-11-29 15:50 ` Grant Hollingworth [this message]
2007-11-29 18:18 ` 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=1196351158-sup-2243@spooky.local \
--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