Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wes@hardakers.net>
Cc: ding@gnus.org
Subject: Re: smiley problems (and a patch to fix them)
Date: Mon, 14 Jan 2002 10:24:18 -0800	[thread overview]
Message-ID: <sdvge4g59p.fsf@wanderer.hardakers.net> (raw)
In-Reply-To: <878zb18kgg.fsf@inanna.rimspace.net> (Daniel Pittman's message of "Mon, 14 Jan 2002 18:23:27 +1100")

>>>>> On Mon, 14 Jan 2002 18:23:27 +1100, Daniel Pittman <daniel@rimspace.net> said:

Daniel> If it's possible to extract the original text of the smiley
Daniel> from the buffer at this stage, which it /probably/ is, you
Daniel> should put that in as the textual form of the glyph.

Thats what the patch did.  It's a question of whether or not the glyph
should be made at all or if just the original text (unmodified and
un-glyphed) should be left.  Either way, it'll look the same.

-- 
"Ninjas aren't dangerous.  They're more afraid of you than you are of them."



  reply	other threads:[~2002-01-14 18:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14  6:24 Wes Hardaker
2002-01-14  7:23 ` Daniel Pittman
2002-01-14 18:24   ` Wes Hardaker [this message]
2002-01-19 22:35 ` Lars Magne Ingebrigtsen
2002-01-25 16:26   ` Wes Hardaker

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=sdvge4g59p.fsf@wanderer.hardakers.net \
    --to=wes@hardakers.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).