Gnus development mailing list
 help / color / mirror / Atom feed
From: Nikolaus Rath <Nikolaus@rath.org>
Subject: Re: Use images instead of glyphs for fancy threading?
Date: Tue, 13 Jun 2006 09:53:13 +0200	[thread overview]
Message-ID: <87zmgh5w5y.fsf@nokile.rath.org> (raw)
In-Reply-To: <wshd2pixzl.fsf@stone.tss.usg.edu>

Mark Plaksin <happy@mcplaksin.org> writes:
> When graphics are available, does it make sense to use images
> instead of glyphs for fancy thread display? I don't know anything
> about using images in Emacs but it seems like this would be a lot
> easier than making glyphs work.
>
> I finally got nice thread glyphs working in X by following these
> hints: http://www.emacswiki.org/cgi-bin/wiki/GnusFormatting

Why not just use unicode characters? This works fine here:

 gnus-summary-line-format "%U%R%z%4L %(%[%-20,20f%]%) %B%s\n" 
 gnus-sum-thread-tree-root "● "
 gnus-sum-thread-tree-single-indent "◎ "
 gnus-sum-thread-tree-leaf-with-other "├─► "
 gnus-sum-thread-tree-vertical "│"
 gnus-sum-thread-tree-single-leaf "╰─► "
 gnus-sum-thread-tree-indent "  "
 gnus-sum-thread-tree-false-root "○ "
 gnus-summary-same-subject ""

> I don't understand much about fonts and such but the whole process
> seems unnecessarily hard and fragile. If I change fonts, I think my
> fancy glyphs might break. And I assume I need a separate setup if I
> want to to have fancy glyphs when I log in via ssh and run Emacs (or
> multi-tty's [1] emacslient) on a tty.

As long as your font has the necessary characters, AFAIK there should
be no problems.

   --Nikolaus

-- 
Eines der Geheimnisse des Usenet ist es eben, dass Anspielungen,
die in Kneipen und auf nicht-einschlaegigen Feten nur stumpfes
Unverstaendniss hervorrufen, endlich auf Verstaendnis treffen.
                                    -- Juergen Ernst Guenther in dafu




  reply	other threads:[~2006-06-13  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-13  2:35 Mark Plaksin
2006-06-13  7:53 ` Nikolaus Rath [this message]
2006-06-29 16:31   ` Mark Plaksin
2006-06-30  7:02     ` Frank Schmitt

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=87zmgh5w5y.fsf@nokile.rath.org \
    --to=nikolaus@rath.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).