From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: How do you use gnus? really.
Date: Sun, 14 Sep 2014 12:13:10 +0200 [thread overview]
Message-ID: <87mwa2y0g9.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87iokrfjxy.fsf@gmail.com>
jenia.ivlev@gmail.com (jenia.ivlev) writes:
> One thing I constantly want to do is go to my sent messages and find
> the thread in the actual NNTP channels, like this channel.
I never do that - maybe because I can't, maybe because I have adapted to
how things work... I am not quite sure.
You can go to the newsgroup and find your own articles there by
searching for your name (/ a), and then you have the thread directly?
> I press ^ over the message in sent+archive:2014-09 folder and I get:
>
> No reference in article x" or "cant find article some-cryptic-id"
Does it help to configure the variable gnus-refer-article-method ?
> I can't believe for a second that I;m the only person that has that
> workflow.
I've never thought of doing that, but...
> How do you find the messages you sent in all the channels and then find
> the answers to those messages?
I usually read the newsgroups I am subscribed to, so I don't need to do
anything special to find the answers - they arrive as unread articles,
and I read them.
I highlight replies by using the trick of scoring on the constant part
of my Message-Id's in the References header.
I.e. I have in my ~/News/all.SCORE:
("references"
("<87[0-9a-z]+\\.fsf\\(_-_\\)?@.*koldfront.dk>" nil nil r))
(The constant part varies from user to user, of course).
> You scroll through every channel in which you;re interested?
Well, I only see the new articles, but yes. This only works well for
groups with groups with a reasonable traffic level; the all.SCORE trick
mentioned above helps on larger groups, but I guess huge groups, like
lkml, would be problematic in any case.
> I want to go to the sent folder, and press ^ or some other key and be
> sent to the corresponding thread in the corresponding channel for that
> message.
I wonder if the "warp" functionality can be used/expanded for your use.
Best regards,
Adam
--
"It must be a fallen angel! Generally they burn up Adam Sjøgren
in the atmosphere, but this one apparently asjo@koldfront.dk
vaporized on impact, leaving this angel-shaped
crater in the snow!"
next prev parent reply other threads:[~2014-09-14 10:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 18:34 jenia.ivlev
2014-09-14 6:29 ` Steinar Bang
2014-09-14 10:13 ` Adam Sjøgren [this message]
2014-09-14 10:23 ` Adam Sjøgren
2014-09-16 14:15 ` jenia.ivlev
2014-09-16 20:55 ` jenia.ivlev
2014-09-17 8:39 ` Eric S Fraga
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=87mwa2y0g9.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.org \
/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).