From: Harry Putnam <reader@newsguy.com>
Subject: Bye bye fontlock
Date: Thu, 19 Jul 2001 17:35:06 -0700 [thread overview]
Message-ID: <m17kx4qvyd.fsf@reader.newsguy.com> (raw)
Has anyone else noticed that fontlocking in any of the message buffers
has went south. That is, kaput, gone, is no more.
I first noticed this in the last two days, following an cvs update.
Retreated back to a version of 03 to see if it was something of mine.
The 03 version works as expected. So pulled down a new cvs package
and built it. Here is what I see:
Pressing F in summary buffer opens the expected message buffer but
with out any fontlocking.
Ditto f R r and D e in drafts.
next reply other threads:[~2001-07-20 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-20 0:35 Harry Putnam [this message]
2001-07-20 12:28 ` Karl Kleinpaste
2001-07-20 14:45 ` Harry Putnam
2001-07-20 15:33 ` Norbert Koch
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=m17kx4qvyd.fsf@reader.newsguy.com \
--to=reader@newsguy.com \
/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).