From: Tino Calancha <tino.calancha@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Emacs developers <emacs-devel@gnu.org>, raman <raman@google.com>,
Tino Calancha <tino.calancha@gmail.com>
Subject: Re: HowTo: Search emacs-devel using gnus
Date: Sat, 25 Feb 2017 11:11:01 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1702251059280.1870@calancha-pc> (raw)
In-Reply-To: <871sunduyy.fsf@drachen>
On Sat, 25 Feb 2017, Michael Heerdegen wrote:
>> ;; Go to beginning of buffer. You can get the Message-id and
>> ;; several cross reference.
>>
>> II)
>> Now, you can call `gnus-summary-goto-article' with first arg
>> the message ID in I).
>>
>> j MESSAGE-ID RET
Sometimes i choose a message-id which Gnus cannot fetch.
Usually after inspection i find that message-id has embedded html.
E.g. see '&45;' below:
047a67ec-9e29-7e4e-0fb0-24c3e59b5886@dancol.org
You must translate '-' to '-', then the article is found:
047a67ec-9e29-7e4e-0fb0-24c3e59b5886@dancol.org
(It must exist one Emacs function translating those '&#foo;' somewhere)
>> For short threads is OK, but for long threads, sometimes is time
>> consuming to get the right message id.
>
> Once I have the id of one message from that thread, I can use A T
> (`gnus-summary-refer-thread': "Fetch all articles in the current
> thread.") and search from within Gnus.
That greatly improve the receipt! Thank you!
next prev parent reply other threads:[~2017-02-25 2:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 4:08 HowTo: Search emacs-devel using gnus raman
2016-12-16 13:54 ` Lars Ingebrigtsen
2016-12-16 16:17 ` raman
2017-02-24 1:31 ` Michael Heerdegen
2017-02-24 3:49 ` raman
2017-02-24 7:05 ` Tino Calancha
2017-02-24 23:34 ` Michael Heerdegen
2017-02-24 23:37 ` T.V Raman
2017-02-25 1:16 ` Michael Heerdegen
2017-02-25 2:11 ` Tino Calancha [this message]
2017-02-27 0:58 ` Michael Heerdegen
2017-02-27 16:19 ` raman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1702251059280.1870@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
--cc=raman@google.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).