Gnus development mailing list
 help / color / mirror / Atom feed
From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: gnus-cache redux
Date: 10 Dec 1995 16:15:58 +0100	[thread overview]
Message-ID: <w8sivjpkl01.fsf@surt.ifi.uio.no> (raw)
In-Reply-To: Sudish Joseph's message of 07 Dec 1995 21:48:56 -0500

Sudish Joseph <joseph@cis.ohio-state.edu> writes:

> All I remember is that the cache should be dissociated with ticking.
> Essentially, I'd prefer the cache to be a better way of doing what I
> currently do using gnus-summary-copy-article.

Yes, that's what was meant by "persistent article" -- you tap some
key, and the article will forever remain in the group, untouched by
the server expiry process.  (I.e., it's put in the cache.)

I agree with you that caching should be dissociated from the marks.
I'm currently leaning towards just adding two enter/exit commands, and
an "*" would be displayed in the second column of the screen (where
"#" and "A" are displayed.  A bit crowded, perhaps.  :-)  

So caching would be totally disconnected from the readedness marks.  

... hey, the `*' key is free!  Miracles of miracles... `*' to enter an
article into the cache and `M-*' to remove it?  

This would be in addition to the current way of doing things, of
course. 

-- 
Home is where the cat is.


  reply	other threads:[~1995-12-10 15:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-12-07 10:48 Lars Magne Ingebrigtsen
1995-12-08  2:48 ` Sudish Joseph
1995-12-10 15:15   ` Lars Magne Ingebrigtsen [this message]
1995-12-11 18:46     ` Scott Blachowicz
1995-12-12 20:59       ` Lars Magne Ingebrigtsen
1995-12-12 23:01         ` Scott Blachowicz
1995-12-13 17:30           ` Lars Magne Ingebrigtsen
1995-12-08 18:09 ` Luis Fernandes
1995-12-10 15:16   ` Lars Magne Ingebrigtsen
1995-12-08 21:08 ` Felix Lee
1995-12-13  8:21 ` Kai Grossjohann
1995-12-13 11:08   ` Lars Magne Ingebrigtsen

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=w8sivjpkl01.fsf@surt.ifi.uio.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).