Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: It was raining
Date: 09 Aug 1996 10:49:15 +0200	[thread overview]
Message-ID: <x6wwz9rlgz.fsf@eyesore.no> (raw)


So I wrote some new stuff.

Let's see...

* A command for clearing out all article numbers from native groups

* Undo of some commands in the group buffer

* Score decay

* Scoring on the Date header using regexp matches, so you can now
say "....0401.23...." to score on all articles that were posted at
11PM on April 1st.  Neat!

* I've added that multi-document thingie -- `####' and then `M-C-d' to
open an nnvirtual group that has lots of document groups as component
groups. 

* Extended formatting variable syntax.  You may now say, in addition
to "%6,6s" things like "%~(pad 6)~(cut-left 2)~(max 20)~(ignore 0)s" 
to have a spec that's always at least 6 chars wide; that has had the
two leftmost characters chopped off; that is never longer than 20
characters; and that is blank if it is equal to "0".  That last part
is the important one -- it allows uncluttered buffers.  "%i" will, for
instance, in the summary buffer be the score.  Most articles have a
score of 0, and don't need to be inserted, really.  "%~(ignore 0)i"
will print out a blank field when the score is 0.

Yes, I really did try to make the syntax as ugly as possible, since
you asked.

Anybody have a better idea as to making the format a little prettier?

Oh, and I've also added a new spec -- "@".  You can say 
"%~(form (whatever-form))@" and the result from that form will be
inserted.  It's just a simpler way of doing the same things as the
user-defined function specs, but, like.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


                 reply	other threads:[~1996-08-09  8:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=x6wwz9rlgz.fsf@eyesore.no \
    --to=larsi@ifi.uio.no \
    /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).