From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/10311 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.user Subject: Re: Automatically authenticating at local imap server Date: Tue, 05 Feb 2008 11:00:41 -0600 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <861w7ruyme.fsf@lifelogs.com> References: <87fxw9lr6x.fsf@gaura-nitai.dyndns.org> <87odax2jzi.fsf@member.fsf.org> <874pco7bot.fsf@member.fsf.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1202233251 15450 80.91.229.12 (5 Feb 2008 17:40:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 5 Feb 2008 17:40:51 +0000 (UTC) To: info-gnus-english@gnu.org Original-X-From: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Tue Feb 05 18:41:12 2008 Return-path: Envelope-to: gegu-info-gnus-english@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JMRn5-00018d-K7 for gegu-info-gnus-english@m.gmane.org; Tue, 05 Feb 2008 18:41:03 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JMRmd-00065p-Dr for gegu-info-gnus-english@m.gmane.org; Tue, 05 Feb 2008 12:40:35 -0500 Original-Path: shelby.stanford.edu!headwall.stanford.edu!newsfeed.news2me.com!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.freenet.de!news.albasani.net!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-Lines: 39 Original-X-Trace: news.albasani.net AmYIWXBLMJbGFqZmjL8/IKCxD7AmNYT6GfODvmrrDy4tTujOyFHdcyqXWZp/7movLdqJaV5Eb8YNRW7ma//ROLN9mNn8OXIfSTIPCE5i1Sec62Lm51VrwFdFBrKyjo84 Original-X-Complaints-To: abuse@albasani.net Original-NNTP-Posting-Date: Tue, 5 Feb 2008 16:59:01 +0000 (UTC) X-User-ID: UYgJlL+FrSjEK8lDIS3GfDtMABIA/IRK5RtTlsBcp4U= X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Cancel-Lock: sha1:atP8BFApZvJ5JjiHH16uimE1t0w= sha1:wyMlMl2vY5PC9y/w0v/T/trvqzA= User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/23.0.50 (gnu/linux) X-NNTP-Posting-Host: DbNCLykOWw7Z+4Ggacei6LnbqAw+10Wv2A8G51CowkU= Original-Xref: shelby.stanford.edu gnu.emacs.gnus:80521 X-BeenThere: info-gnus-english@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Errors-To: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.gnus.user:10311 Archived-At: On Mon, 04 Feb 2008 23:22:38 +0100 David wrote: D> Tassilo Horn writes: >> But one thing is left: Is there a way to jump from a message in the >> search result group to the original nnimap group? I often do a search >> to find a message I want to reply to and the reply has to be done from >> the original group so that posting styles and group parameters are >> considered. D> That's on the TODO list - I always wanted a function that jumps to the D> original message in the original group, but it's not trivial to do. My D> idea was to call mairix with "m:", where MID is the message-id of D> the article. Using the "-r" option, we get the full path of the mail D> file and it should be possible to uniquely identify the group from the D> path (the problem here is that the user might index several different D> mail back ends with one mairix installation). Jumping to the original D> message in this group is another problem since we only know the D> message-id but not the article number. nnmaildir and nnml support D> fetching articles by message-id, but AFAIK nnimap does not. Maybe it is D> somehow possible to apply the correct posting style even when replying D> from the nnmairix group, then we wouldn't have to get the original D> article in the first place. You could use the Gnus registry if it's loaded. It will tell you the last place a message ID was seen (it learns this by looking at the visible messages every time you enter a group, and by hooking into spool/move/copy/delete on each backend). It may not know the location for various reasons, e.g. the user limits the size of the registry or the message hasn't been seen yet, but when the location is available it's a very quick lookup in a hashtable, probably much faster than calling mairix to do a search. The registry doesn't currently record the article number, but it could. Currently a group name is always a string and anything not a string is extra (non-location) data, so this is not a trivial change. Since article numbers are stable in some backends and not in others, this may be quite a bit of work to do properly. Ted