all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: raman@google.com (T.V Raman)
To: michael_heerdegen@web.de
Cc: larsi@gnus.org, emacs-devel@gnu.org, raman@google.com,
	tino.calancha@gmail.com
Subject: Re: HowTo: Search emacs-devel using gnus
Date: Fri, 24 Feb 2017 15:37:15 -0800	[thread overview]
Message-ID: <22704.50091.404109.234179@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <871sunduyy.fsf@drachen>

could someone automate this away with an elisp function:-)

Michael Heerdegen writes:
 > Hi Tino!
 > 
 > Thanks for your answer, it probably saved me a lot of time to invent
 > this myself.
 > 
 > > You can use `eww' to get the message-id:
 > > I)
 > > M-x: eww https://lists.gnu.org/archive/html/emacs-devel/ RET
 > > ;; Do a search of some words related with the topic you are looking for.
 > > ;; For instance,
 > > Search emacs-devel using gnus
 > >
 > > ;; Let's pick up the first result:
 > > M-x eww-view-source RET
 > 
 > Aka v in my eww version.
 > 
 > > ;; 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
 > 
 > Yip, works like a charm!
 > 
 > > 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.
 > 
 > 
 > Thanks again,
 > 
 > Michael.

-- 

-- 



  reply	other threads:[~2017-02-24 23:37 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 [this message]
2017-02-25  1:16           ` Michael Heerdegen
2017-02-25  2:11         ` Tino Calancha
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22704.50091.404109.234179@retriever.mtv.corp.google.com \
    --to=raman@google.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=michael_heerdegen@web.de \
    --cc=tino.calancha@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.