From: Paul Stevenson <p.stevenson@surrey.ac.uk>
Subject: Re: Very unhappy (again). What happened? "B r" marked all unread as read.
Date: 07 Feb 2001 11:38:53 +0000 [thread overview]
Message-ID: <i5kzofypvsi.Dunlap@gromit.ph.surrey.ac.uk> (raw)
In-Reply-To: <vafitmm3f67.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "07 Feb 2001 12:28:48 +0100")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> I agree that a way to save marks along with the backend is a
> goodidea. I wonder if it is difficult to do. Hm.
M3 T0)!!1!. I've lost things like 'answered' marks before
which was a pain. Can I just say to whoever wants to implement the
Great Mark Plan:
· User-defined marks would be nice
· Is it necessary to differentiate between primary and secondary
marks? It'd at least be nice to add some functionality to secondary
marks, like limiting to them.
--
. Paul Stevenson . Research Fellow . University of Surrey .
. phone: +44 (0) 1483 876795 . fax +44 (0) 1483 876781 .
. p.stevenson@surrey.ac.uk . http://www.ph.surrey.ac.uk/~phs3ps .
. I dream in beige .
prev parent reply other threads:[~2001-02-07 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-21 19:58 Rob Browning
2001-01-22 5:19 ` Very unhappy (again). (Apologies) Rob Browning
2001-02-07 11:28 ` Very unhappy (again). What happened? "B r" marked all unread as read Kai Großjohann
2001-02-07 11:38 ` Paul Stevenson [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=i5kzofypvsi.Dunlap@gromit.ph.surrey.ac.uk \
--to=p.stevenson@surrey.ac.uk \
/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).