From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: [PATCH] Replace subst-char-in-region by subst-char-in-region
Date: Mon, 20 Sep 2010 10:17:29 -0500 [thread overview]
Message-ID: <8762y0h2ba.fsf@lifelogs.com> (raw)
In-Reply-To: <sa37higv4xo.fsf@cigue.easter-eggs.fr>
On Mon, 20 Sep 2010 16:57:07 +0200 Julien Danjou <julien@danjou.info> wrote:
JD> On Mon, Sep 20 2010, Ted Zlatanov wrote:
>> I suggest constructing the list on startup, based on `gnus-use-unicode'
>> or some such which the user can customize (I would default it to t but
>> warn if the font doesn't support those characters).
JD> I could install such a change, but how warn if the font doesn't support
JD> those characters?
JD> We could do:
JD> (defcustom gnus-read-mark (if (font-has-unicode-p) ?✓ ?R))
That's hard to read. I think it's better to support sets of such
customizations, similar to how many people have structured thread
drawing characters. So Gnus will do on startup:
(gnus-install-visuals gnus-visuals) ; try each visual set in turn
and then in gnus.el:
(setq gnus-visuals 'unicode 'ascii)
(setq gnus-visual-sets '((ascii ...) (unicode ...)))
and in your personal customizations:
(add-to-list 'gnus-visual-sets '(julien ...))
(setq gnus-visuals (cons 'julien gnus-visual-sets))
WDYT? Of course, each set doesn't have to be complete, so they can
build on each other. A set can have any number of:
- mark characters
- thread drawing characters
- registry mark characters
- others?
Ted
next prev parent reply other threads:[~2010-09-20 15:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 12:46 Julien Danjou
2010-09-19 13:05 ` Lars Magne Ingebrigtsen
2010-09-19 13:42 ` Julien Danjou
2010-09-19 13:45 ` Lars Magne Ingebrigtsen
2010-09-19 13:54 ` Julien Danjou
2010-09-19 14:05 ` Lars Magne Ingebrigtsen
2010-09-19 14:24 ` Julien Danjou
2010-09-19 14:57 ` Lars Magne Ingebrigtsen
2010-09-20 6:50 ` Reiner Steib
2010-09-20 8:11 ` Lars Magne Ingebrigtsen
2010-09-20 8:41 ` Julien Danjou
2010-09-20 8:40 ` Julien Danjou
2010-09-20 9:02 ` Frank Schmitt
2010-09-20 9:29 ` Tassilo Horn
2010-09-20 14:46 ` Ted Zlatanov
2010-09-20 14:57 ` Julien Danjou
2010-09-20 15:17 ` Ted Zlatanov [this message]
2010-09-20 17:06 ` Julien Danjou
2010-09-20 17:21 ` Lars Magne Ingebrigtsen
2010-09-20 18:05 ` Ted Zlatanov
2010-09-20 21:41 ` Lars Magne Ingebrigtsen
2010-09-21 8:03 ` Julien Danjou
2010-09-21 16:15 ` Ted Zlatanov
2010-09-21 16:22 ` Lars Magne Ingebrigtsen
2010-09-21 17:02 ` Ted Zlatanov
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=8762y0h2ba.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).