From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] Be less overzealous in moving text to the left column
Date: Thu, 03 Sep 2009 10:12:25 -0700 [thread overview]
Message-ID: <1251997795-sup-8368@masanjin.net> (raw)
In-Reply-To: <1251323127-sup-5162@yoom.home.cworth.org>
Reformatted excerpts from Carl Worth's message of 2009-08-26:
> And I still haven't figured out what loose_alignment means and which
> actions will cause loose vs. non-loose layout.
Yeah, it's not really clear where I was going with that. The whole thing
was in need of some rethinking and additional comments. I've made a
branch 'alignment-tweaks', merged into next, which I think has the
behavior you were looking for: left-column movement is minimized when
using 'n' and 'p' to jump between messages. You can also use 'z' to
align the left column with the current message.
Check it out and let me know what you think. If this bugs people, also
let me know. :)
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-09-03 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 6:31 Carl Worth
2009-08-23 17:55 ` William Morgan
2009-08-26 21:53 ` Carl Worth
2009-09-03 17:12 ` William Morgan [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1251997795-sup-8368@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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