From: Ted Zlatanov <tzz@lifelogs.com>
To: Miles Bader <miles@gnu.org>
Cc: ding@gnus.org
Subject: Re: variable-pitch font in article buffer
Date: Thu, 03 Jul 2008 15:59:51 -0500 [thread overview]
Message-ID: <86od5ek7js.fsf@lifelogs.com> (raw)
In-Reply-To: <873amt1c64.fsf@catnip.gol.com> (Miles Bader's message of "Wed, 02 Jul 2008 07:18:11 +0900")
On Wed, 02 Jul 2008 07:18:11 +0900 Miles Bader <miles@gnu.org> wrote:
MB> Ted Zlatanov <tzz@lifelogs.com> writes:
MB> However some articles really need a fixed-pitch font, thus the
MB> easy-to-hit summary-buffer binding to toggle variable-pitch mode in the
MB> article buffer.
>>
>> This might make sense as a group/topic property that's also triggered by
>> article contents, etc. How do you use it, always manually?
MB> I just toggle it "manually" (my hook turns it on by default).
MB> Variable-pitch seems to work well (and is generally more readable) for
MB> about 99% of articles; I rarely turn it off even in technical groups
MB> where people post patches and code etc.
MB> [Even ascii art tables are a bit of a wash these days since half the
MB> time the author apparent sent it using a MUA using a variable-width
MB> font, and aligned things accordingly!!]
So maybe a keymap would be appropriate so users can toggle it back, plus
a variable called gnus-article-variable-pitch-mode that defaults to nil
and, when enabled, turns v-p-m on.
I wouldn't use it personally, I like the fixed width spacing better, but
I imagine a lot of user would appreciate it. It also looks jarringly
inconsistent with the thread display IMO.
Opinions, anyone?
Ted
next prev parent reply other threads:[~2008-07-03 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 6:10 Miles Bader
2008-07-01 20:41 ` Ted Zlatanov
2008-07-01 22:18 ` Miles Bader
2008-07-03 20:59 ` Ted Zlatanov [this message]
2008-07-03 21:10 ` Miles Bader
2008-07-04 12:55 ` James Cloos
2008-07-04 14:13 ` Miles Bader
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=86od5ek7js.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=miles@gnu.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;
as well as URLs for NNTP newsgroup(s).