G D in the group buffer almost does what I want...
I'm sure someone else out there has done this before, or has a good
idea on how to view directories full of mbox folders. These are for
archive purposes, so read-only is OK.
Any ideas?
--
Josh Huber
Or do you want one group per file? That's easy, just use `G f' for
all of them.
kai
--
The passive voice should never be used.
> How do you want to view them? As a single group? Then maybe doing a
> directory group, then marking them all, then C-M-d?
>
> Or do you want one group per file? That's easy, just use `G f' for
> all of them.
That will give you nndoc groups, which lack some functionality (delete
and move at least), so I've switched to nnfolder groups. There was a
thread here on it recently:
--
--Ed Cashin PGP public key:
eca...@terry.uga.edu http://www.terry.uga.edu/~ecashin/pgp/
> Kai.Gro...@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
> > How do you want to view them? As a single group? Then maybe doing a
> > directory group, then marking them all, then C-M-d?
> > Or do you want one group per file? That's easy, just use `G f' for
> > all of them.
I'd like one group per file, but what I wanted to avoid was having to
create a group for every file in the subdirectory (there are 79
folders in there now).
> That will give you nndoc groups, which lack some functionality (delete
> and move at least), so I've switched to nnfolder groups. There was a
> thread here on it recently:
Okay, but is there a way to browse a directory of files, and have gnus
create the group on demand? I'd really like to avoid having to
subscribe to each folder individually.
Thanks for the help,
--
Josh Huber
> Okay, but is there a way to browse a directory of files, and have
> gnus create the group on demand? I'd really like to avoid having to
> subscribe to each folder individually.
I think nneething is what you want. Just create an nneething group
for the directory, then hit RET on a file, then you should get a
sub-group for the file.
> I think nneething is what you want. Just create an nneething group
> for the directory, then hit RET on a file, then you should get a
> sub-group for the file.
This doesn't seem right. It looks a lot like what an nndoc group
shows me when I create one.
I also found this reference to exactly what I'm doing:
<URL:http://www.gnus.org/list-archives/ding/199711/msg00099.html>
So, is the only option to create a bunch of nnfolder groups, and
bundle them together with nnvirtual, as is said in the referenced
article?
I'm willing to write some lisp, but I still don't quite understand the
inner workings of Gnus. (does anyone? :) Maybe someone has an hint?
> I'm willing to write some lisp, but I still don't quite understand
> the inner workings of Gnus. (does anyone? :) Maybe someone has an
> hint?
Well, you COULD do
cd /directory/with/lotsa/mbox/files/
cat * > ../single-file
And then `G f' on /path/to/single-file. But that would be cheating
:-)
> Well, you COULD do
>
> cd /directory/with/lotsa/mbox/files/
> cat * > ../single-file
>
> And then `G f' on /path/to/single-file. But that would be cheating
> :-)
Hehe, that would be fine with me, but that's *not* what I want. I
tried out the nnvirtual deal, and that's really not what I'm looking
for. I don't want all the articles in one group.
I guess what I really want is just a directory listing, and when I
select a file, I want gnus to open it as a folder.
Perhaps I can coerce dired into doing this?
--
Josh Huber
> I guess what I really want is just a directory listing, and when I
> select a file, I want gnus to open it as a folder.
In what way is `G D' not the right thing? I thought it was just what
you wanted.
> In what way is `G D' not the right thing? I thought it was just what
> you wanted.
Well, maybe it's not configured right on my end here, but when I do
this, I get a listing of all the mailboxes, but Gnus tries to be smart
and view each one as a single message (I even get a couple that are
threaded). When I view one of the 'messages' it shows the whole
contents of the mbox file in the lower pane of the frame.
This isn't really what I want...
--
Josh Huber
> Well, maybe it's not configured right on my end here, but when I do
> this, I get a listing of all the mailboxes, but Gnus tries to be
> smart and view each one as a single message (I even get a couple
> that are threaded). When I view one of the 'messages' it shows the
> whole contents of the mbox file in the lower pane of the frame.
I see. I thought this would happen, but I didn't have mbox files to
try it out with.
What happens when you `C-d' on such a message?
> I see. I thought this would happen, but I didn't have mbox files to
> try it out with.
Ah. :)
> What happens when you `C-d' on such a message?
Pretty odd. I see a whole bunch of messages with author (none) and no
subject, which contain the signature of one message plus the headers
and body of the next message...clearly messed up...
ttyl,
--
Josh Huber
If you use nnfolder and then run the nnfolder-generate-active-file
command, you'll be able to use tab completion to subscribe to a
folder.
You could also go through all the folders in the directory in emacs
lisp, subscribing to them, if there are thousands of them or
something.
> Kai.Gro...@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> I see. I thought this would happen, but I didn't have mbox files
>> to try it out with.
>
> Ah. :)
Silly me. I just used `O m' twice on a couple of articles, and soon I
had a directory with two mbox files. And indeed, `G D' gets mightily
confused. That's bad.
kai
--
~/.signature: No such file or directory
Odd indeed. Hm. I think that nneething should grok dir-of-mbox. How
about submitting a feature request?
> Silly me. I just used `O m' twice on a couple of articles, and soon I
> had a directory with two mbox files. And indeed, `G D' gets mightily
> confused. That's bad.
Yeah...perhaps I'll take a look at the nnething code, but I'll also
submit a feature request...how does one do that?
Thanks,
--
Josh Huber
> Yeah...perhaps I'll take a look at the nnething code, but I'll also
> submit a feature request...how does one do that?
If you think no discussion is needed, abuse a bug report. For
discussions, a post in the Gnus mailing list (pointer at www.gnus.org)
might be better.