From: Greg Stark <gsstark@MIT.EDU>
Subject: smileys on fsf emacs
Date: 26 Jun 1996 23:42:38 -0400 [thread overview]
Message-ID: <ycqn31p9akx.fsf@lola-granola.MIT.EDU> (raw)
In-Reply-To: Katsumi Yamaoka's message of 27 Jun 1996 08:57:42 +0900
Hmm, it should be possible to make a font containing each of the smileys and
use that font to show smileys on the FSF Emacs. The only limitation would be
the multicolourness of some of the smileys. But i can imagine somebody might
be able to hack something using font metrics, zero width characters, and two
character glyphs... Besides, most of them would do ok with just a foreground
and background colour and this would have the benefit of scaling up to match
the size font being used in the document.
I don't know enough about X fonts to do this myself,
but i might start experimenting if no one else does.
greg
PS I know RMS doesn't like the term ``FSF Emacs''
but i can't imagine what else to call it.
next reply other threads:[~1996-06-27 3:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-27 3:42 Greg Stark [this message]
1996-06-27 13:50 ` 'FSF Emacs' Richard Pieri
1996-06-27 15:01 ` William Perry
1996-06-27 14:58 ` Richard Pieri
1996-06-27 14:13 ` smileys on fsf emacs Colin Rafferty
1996-06-27 14:46 ` William Perry
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=ycqn31p9akx.fsf@lola-granola.MIT.EDU \
--to=gsstark@mit.edu \
/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).