From: David Abrahams <dave@boostpro.com>
To: Miles Bader <miles@gnu.org>
Cc: ding@gnus.org
Subject: Re: variable-width font in summary buffer?
Date: Sat, 05 Jul 2008 23:25:44 -0400 [thread overview]
Message-ID: <87mykv7kxz.fsf@mcbain.luannocracy.com> (raw)
In-Reply-To: <878wwf4sk1.fsf@catnip.gol.com> (Miles Bader's message of "Sun, 06 Jul 2008 12:09:34 +0900")
on Sat Jul 05 2008, Miles Bader <miles-AT-gnu.org> wrote:
> David Abrahams <dave@boostpro.com> writes:
>> I'd like to use a variable-width font in my summary buffers, but it
>> seems that, especially when displaying threads, much of what Gnus does there
>> depends on a monospaced font.
>>
>> Is anyone successfully using a variable-pitch font in the summary
>> buffer, and if so, do you have any configuration tips?
>
> It shouldn't be that hard if gnus maintains lets you add text-properties
> to the summary-buffer format string. If it does, you could add display
> properties like (space :align-to COLUMN) instead of using spaces for
> padding.
Hi Miles,
That's an interesting idea. Do you have any pointers that might help me
discover how to do that? I'm a longtime emacs user but this sounds like
a bit of a stretch for me to figure out on my own.
> Actually, gnus probably ought to have a format spec that allows doing
> this simply.
>
> E.g., it could use %N| to add a space which aligns to column N ("%45|"
> would align to column 45).
>
> Perhaps just "%|" (without a column) could auto-calculate the column
> based on the calculated "fixed-width" position.
That sounds like a neat feature idea, but probably not much use to
someone not equipped to develop Gnus features(?)
Thanks for replying,
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2008-07-06 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 12:48 David Abrahams
2008-07-06 3:09 ` Miles Bader
2008-07-06 3:25 ` David Abrahams [this message]
2008-07-06 12:49 ` Johan Bockgård
2009-03-16 21:37 ` David Abrahams
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=87mykv7kxz.fsf@mcbain.luannocracy.com \
--to=dave@boostpro.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).