From: Vincent Bernat <bernat@scientist.com>
Subject: Re: Some tips for LISP programming with Gnus
Date: Sun, 11 Nov 2001 14:51:12 +0100 [thread overview]
Message-ID: <m3hes1v2jz.fsf@neo.loria> (raw)
In-Reply-To: <m33d3oaqzs.fsf@multivac.cwru.edu>
OoO Vers la fin de l'après-midi du vendredi 09 novembre 2001, vers
16:44, prj@po.cwru.edu (Paul Jarc) disait:
>> Placing a special mark which is equivalent to a read mark but which is
>> none of the existing marks.
> Equivalent in what way? Tell us what end effect you're trying to
> accomplish, rather than how you want to go about it; maybe there's an
> easier way.
The "read" mark is an R, I would like to achieve a "read" mark with an
A (for example). But it will be considered like a read mark.
next prev parent reply other threads:[~2001-11-11 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 14:37 Vincent Bernat
2001-11-08 15:21 ` Stainless Steel Rat
2001-11-09 7:52 ` Vincent Bernat
2001-11-09 15:44 ` Paul Jarc
2001-11-11 13:51 ` Vincent Bernat [this message]
2001-11-11 16:28 ` Kai Großjohann
2001-11-11 19:24 ` Paul Jarc
2001-11-12 12:36 ` Per Abrahamsen
2001-11-08 16:46 ` Andreas Fuchs
2001-11-08 16:55 ` Jody Klymak
2001-11-08 17:58 ` Andreas Fuchs
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=m3hes1v2jz.fsf@neo.loria \
--to=bernat@scientist.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).