From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/58583 Path: main.gmane.org!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.gnus.general Subject: How nndir works Date: Sat, 25 Sep 2004 06:02:27 -0500 Organization: Still searching... Sender: ding-owner@lists.math.uh.edu Message-ID: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1096136165 31677 80.91.229.6 (25 Sep 2004 18:16:05 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 25 Sep 2004 18:16:05 +0000 (UTC) Original-X-From: ding-owner+M7121@lists.math.uh.edu Sat Sep 25 20:15:51 2004 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13] ident=mail) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CBH5K-0007G0-00 for ; Sat, 25 Sep 2004 20:15:50 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1CBH52-0001xN-00; Sat, 25 Sep 2004 13:15:32 -0500 Original-Received: from util2.math.uh.edu ([129.7.128.23]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1CBH4u-0001xH-00 for ding@lists.math.uh.edu; Sat, 25 Sep 2004 13:15:24 -0500 Original-Received: from justine.libertine.org ([66.139.78.221] ident=postfix) by util2.math.uh.edu with esmtp (Exim 4.30) id 1CBH4v-0007A4-7q for ding@lists.math.uh.edu; Sat, 25 Sep 2004 13:15:25 -0500 Original-Received: from main.gmane.org (main.gmane.org [80.91.229.2]) by justine.libertine.org (Postfix) with ESMTP id 151C33A0038 for ; Sat, 25 Sep 2004 13:15:21 -0500 (CDT) Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CBGyj-0001m6-00 for ; Sat, 25 Sep 2004 20:09:01 +0200 Original-Received: from adsl-68-74-78-8.dsl.emhril.ameritech.net ([68.74.78.8]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 25 Sep 2004 20:09:00 +0200 Original-Received: from reader by adsl-68-74-78-8.dsl.emhril.ameritech.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 25 Sep 2004 20:09:00 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: ding@gnus.org Original-Lines: 56 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: adsl-68-74-78-8.dsl.emhril.ameritech.net User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux) Cancel-Lock: sha1:NhEuXBvxuek4eSfn3dQOro+QNww= Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:58583 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:58583 I'm using a little scripting to grab namazu output and generate symlinks to the filenames it generates in a certain directory. Also puts the namzu summaries into a numbered file and inserts URL to each symlink created so that one browsing the summary file can use those links to jump to the full message when needed. I access this directory from gnus using nndir. The directory name stays the same but on my next namazu search, different messages are symlinked in there. So far so good. I just alt-g the nndir group and see the new messages. Here's the rub: My scripting creates numbered symlinks by checking the directory and getting the highest numbered message adding 1 then increment for each new link. The summary message mentioned above is just thrown into the directory with next highest number too. Sometimes that summary message will end up with the same number it had the previous time. When that happens gnus shows me the old message. (Which is actually deleted at that point). Even if I CTRL - k the nndir group and recreate it with `G d'. then run alt-g, the newly inserted messages are there but if the summary message happens to be the same number.... it still will have the content of the previous (now deleted message). Looking back at what I wrote it looks really confusing... let me summarize again for clarity. 1) I create a directory populated with symlinks pointing to the files namazu has found hits in. View it from gnus with nndir. 2) I delete the directory and symlinks with rm -rf dir 3) Recreate directory and different symlinks behind gnus back with a new namazu search In the created directory there is always a message with the ame headers inserted that contains namazu output, line for line, along with an URL to what ever symlink each section is about. The symlinks are arrows to the files namazu has searched and found a hit in. They might change with each search. Now if it happens that the message containing namazu summury ends up with the same filename it had in previous search. Gnus shows me the previous file it seems. Gnus must have kept it in memory or something. So my question is how to make gnus clear its memory or meta data so that it displays the newest version of the namazu summary message.