Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: How to open a summary buffer reliable?
Date: Wed, 10 Dec 2008 21:45:35 +0100	[thread overview]
Message-ID: <873agvg3o0.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <871vwfg6bg.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 10 Dec 2008 20:48:19 +0100")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

Hi Reiner,

> I'm not sure if that there is a 100% reliable way (e.g. for empty
> groups I'm not aware of any possibility).

There cannot be a (working) link to a message in an empty group, so
that's no issue here.

> Are you sure that you really need to enter the group?  Maybe it
> someone can come up with an idea if you describe what you want to
> achieve in org-mode finally.  (I don't use org-mode myself (yet), so
> my questions might be silly.)

I have a group name (i.e. "nnimap+Foo:bar.baz") and a message-id.  Now I
want to open a summary buffer which contains the article with that
message-id, and the article should be displayed in an article buffer.

The message-id is optional.  If none is given only the group's summary
should be shown.  In that case the "how many articles" question is ok,
of course.

> Maybe also gnus-group-quick-select-group and

Nice (because it's quick), but it has the same problem as the "slow"
version.

> gnus-group-select-group-ephemerally are useful.

No, that one's not good.  The user should be able to modify the linked
article.  (Maybe someone makes "delete that message on christmas"
links.)

Bye,
Tassilo



  reply	other threads:[~2008-12-10 20:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 19:14 Tassilo Horn
2008-12-10 19:48 ` Reiner Steib
2008-12-10 20:45   ` Tassilo Horn [this message]
2008-12-10 21:52 ` David Engster
2008-12-11  8:11   ` Tassilo Horn
2008-12-11 16:39     ` Tassilo Horn
2008-12-11 18:30       ` David Engster
2008-12-11 19:21         ` Tassilo Horn

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=873agvg3o0.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.org \
    --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).