From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: gnus-summary-line-format: what if an article is both answered and saved?
Date: Sun, 20 Mar 2011 07:00:37 -0500 [thread overview]
Message-ID: <87bp16q9wa.fsf@lifelogs.com> (raw)
In-Reply-To: <87sjuilbxu.fsf@jidanni.org>
On Sun, 20 Mar 2011 11:15:25 +0800 jidanni@jidanni.org wrote:
j> Rather than resorting to images, or "Æ" U+00C6 LATIN CAPITAL LETTER AE
j> etc. Why not just let the letters agglutinate, so one can see both:
j> "AS"... and use the %widths if one want to make a fixed width for it.
You can do that using user functions. That's how
`gnus-registry-user-format-function-M' shows all the registry marks.
Ted
next prev parent reply other threads:[~2011-03-20 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 4:31 jidanni
2011-03-18 11:13 ` Julien Danjou
2011-03-18 14:34 ` Ted Zlatanov
2011-03-18 14:43 ` Julien Danjou
2011-03-18 14:55 ` Ted Zlatanov
2011-03-20 3:15 ` jidanni
2011-03-20 12:00 ` Ted Zlatanov [this message]
2011-03-20 8:03 ` Erik Colson
2011-03-21 10:54 ` Julien Danjou
2011-03-21 11:11 ` David Engster
2011-03-21 11:33 ` Julien Danjou
2011-03-21 12:51 ` David Engster
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=87bp16q9wa.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).