From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Concerning marks and the back end.
Date: Fri, 03 Jan 2003 14:34:25 -0500 [thread overview]
Message-ID: <86of6ym3i6.fsf@asfast.com> (raw)
In-Reply-To: <843coa9h4m.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Fri, 03 Jan 2003 20:18:33 +0100")
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
>> Like I said originally, I'd like to be able to put a special mark
>> (managed through the .marks file, not the back end) on my articles, such
>> that all of those already read articles that have this special mark are
>> NOT seen; and such that all of those already read articles WITHOUT that
>> special mark are still visible.
>
> You could tick the articles you want to see, and mark as read those
> you don't want to see.
Did you try this before suggesting it?
A tick mark doesn't help. If you've been following this thread, you'll
know that I'm talking about the case where I enter a group with no
unread articles. All the ticked and non-ticked articles show up when I
enter a group with no unread articles.
> You could also mark as dormant the articles you want to see. Then `Y
> d' will show the dormant articles.
Thanks. Soon I'll be off to investigate dormant-izing the articles.
I'll report back a little later.
> You can frob gnus-select-article-hook and/or gnus-mark-article-hook
> to put marks other than `read' onto articles that you read.
Would those marks get stored in the back end, or in the .marks file?
If they're stored in the back end, I don't know that they would
help me.
> --
> Ambibibentists unite!
>
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~2003-01-03 19:34 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 22:23 Lloyd Zusman
2003-01-02 16:57 ` Kai Großjohann
2003-01-02 18:23 ` Lloyd Zusman
2003-01-02 18:46 ` Lars Magne Ingebrigtsen
2003-01-03 2:23 ` Lloyd Zusman
2003-01-03 2:45 ` Simon Josefsson
2003-01-03 2:56 ` Lloyd Zusman
2003-01-03 3:01 ` Lloyd Zusman
2003-01-03 4:11 ` Simon Josefsson
2003-01-03 4:59 ` Lloyd Zusman
2003-01-03 14:57 ` Simon Josefsson
2003-01-04 18:23 ` Lloyd Zusman
2003-01-13 18:47 ` A solution that's better than my ugly hack? Lloyd Zusman
2003-01-13 18:53 ` Lars Magne Ingebrigtsen
2003-01-13 19:00 ` Lloyd Zusman
2003-01-13 19:18 ` Lars Magne Ingebrigtsen
2003-01-13 19:26 ` Lloyd Zusman
2003-01-13 19:30 ` Lars Magne Ingebrigtsen
2003-01-13 19:33 ` Lloyd Zusman
2003-01-13 21:04 ` Lloyd Zusman
2003-01-13 19:32 ` Lloyd Zusman
2003-01-03 17:54 ` Concerning marks and the back end Kai Großjohann
2003-01-03 18:20 ` Lloyd Zusman
2003-01-03 17:53 ` Kai Großjohann
2003-01-03 18:15 ` Lloyd Zusman
2003-01-03 19:18 ` Kai Großjohann
2003-01-03 19:34 ` Lloyd Zusman [this message]
2003-01-03 19:43 ` Lloyd Zusman
2003-01-03 21:03 ` Kai Großjohann
2003-01-03 21:24 ` Lloyd Zusman
2003-01-04 14:52 ` Kai Großjohann
2003-01-04 16:19 ` Lloyd Zusman
2003-01-03 20:17 ` Lars Magne Ingebrigtsen
2003-01-03 20:41 ` Lloyd Zusman
2003-01-03 20:45 ` Lars Magne Ingebrigtsen
2003-01-03 20:52 ` Lloyd Zusman
2003-01-03 21:05 ` Kai Großjohann
2003-01-03 21:05 ` Kai Großjohann
2003-01-04 4:50 ` Lloyd Zusman
2003-01-03 20:53 ` Paul Jarc
2003-01-03 20:58 ` Lloyd Zusman
2003-01-03 21:02 ` Kai Großjohann
2003-01-02 19:14 ` Simon Josefsson
2003-01-03 2:25 ` Lloyd Zusman
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=86of6ym3i6.fsf@asfast.com \
--to=ljz@asfast.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).