Gnus development mailing list
 help / color / mirror / Atom feed
From: Frank Schmitt <ich@frank-schmitt.net>
To: ding@gnus.org
Subject: Re: [PATCH] Replace subst-char-in-region by subst-char-in-region
Date: Mon, 20 Sep 2010 11:02:47 +0200	[thread overview]
Message-ID: <87tylk4wjs.fsf@mid.gehheimdienst.de> (raw)
In-Reply-To: <sa3sk14vmdi.fsf@cigue.easter-eggs.fr>

Julien Danjou <julien@danjou.info> writes:

> On Mon, Sep 20 2010, Reiner Steib wrote:
>
>> Can you suggest which Unicode characters are nicer replacements for
>> the ASCII defaults (of gnus-FOO-mark)?
>
> This is what I currently use:
>
> (setq gnus-score-over-mark ?↑)          ; ↑ ☀
> (setq gnus-score-below-mark ?↓)         ; ↓ ☂
> (setq gnus-ticked-mark ?⚑)
> (setq gnus-dormant-mark ?⚐)
> (setq gnus-expirable-mark ?♻)
> (setq gnus-read-mark ?✓)
> (setq gnus-del-mark ?✗)
> (setq gnus-killed-mark ?☠)
> (setq gnus-replied-mark ?⟲)
> (setq gnus-forwarded-mark ?⤳)
> (setq gnus-cached-mark ?☍)
> (setq gnus-recent-mark ?★)
> (setq gnus-unseen-mark ?✩)
> (setq gnus-unread-mark ?✉)

Those look nice. Only the killed mark looks like the front of a bus for
me? (I'm running Gnus in a screen session on a remote server connected
via ssh, terminal is the almighty, rocking, rocking, rocking,
rxvt-unicode. Default font Terminus but for unicode I think it
automatically falls back to something sensible)

-- 
Have you ever considered how much text can fit in eighty columns?  Given that a
signature typically contains up to four lines of text, this space allows you to
attach a tremendous amount of valuable information to your messages.  Seize the
opportunity and don't waste your signature on bullshit that nobody cares about.




  reply	other threads:[~2010-09-20  9:02 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 [this message]
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
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=87tylk4wjs.fsf@mid.gehheimdienst.de \
    --to=ich@frank-schmitt.net \
    --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).