Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wes@hardakers.net>
To: ding@gnus.org
Subject: Re: Highlight words in the subject line?
Date: Sat, 08 Mar 2008 19:12:18 -0800	[thread overview]
Message-ID: <sd8x0sfv59.fsf@wes.hardakers.net> (raw)
In-Reply-To: <v94pbi5fh3.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 07 Mar 2008 23:36:24 +0100")

>>>>> "RS" == Reiner Steib <reinersteib+gmane@imap.cc> writes:

RS> In 2004, we discussed to include it in Gnus.  I'd still like to
RS> include it, but some issues have not been addressed yet.

Yeah...  I'll take the blame for that.  I haven't had time to fix the
issues.

RS> | - `gnus-summary-highlight-expressions' and
RS> |   `gnus-article-highlight-expressions' are declared with defcustom,
RS> |   but cannot be customized (custom type declarations are missing).

RS> This hasn't been addressed.  Any volunteer?

Yep, they were place holders.  I do it via variables but knew eventually
they should be customs.

RS> | - Shouldn't the initialization part (and *-treat-* variables) be moved
RS> |   to `gnus-art.el' (or`gnus-sum.el')?

RS> This can be done after the integration.

Obviously, I can't do that easily.  I'd need to create a patch instead
of a separate file (which I haven't done).
 
RS> | - How about text for the manual (texi/gnus.texi) and the NEWS file
RS> |   (texi/gnus-news.texi)?

RS> We need text for the manual.  Something like the documentation of
RS> `gnus-summary-highlight-expressions', at least.

Ah, always documentation...  That's always the last thing to be done.
-- 
"In the bathtub of history the truth is harder to hold than the soap,
 and much more difficult to find."  -- Terry Pratchett



      reply	other threads:[~2008-03-09  3:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 14:26 Bastien
2008-03-06 14:02 ` Wes Hardaker
2008-03-06 14:29   ` Bastien
2008-03-07 20:38     ` Wes Hardaker
2008-03-07 22:36   ` Reiner Steib
2008-03-09  3:12     ` Wes Hardaker [this message]

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=sd8x0sfv59.fsf@wes.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).