make it easier to use nnml for archive groups

make it easier to use nnml for archive groups

[Dan Nicolaescu]

Can the configuration for using nnml as the archive method be made easier?

This is what's in my .gnus.el:

(setq gnus-message-archive-method
      '(nnml "archive"
             (nnml-directory "~/Mail/archive")
             (nnml-active-file "~/Mail/archive/active")
             (nnml-get-new-mail nil)
             (nnml-inhibit-expiry t)))

nnml is better as an archive method than nnfolder.  With nnfolder the
file gets very big if you send a few attachments.

With nnml one can use:

(setq gnus-message-archive-group
       (concat "sent-mail-" (format-time-string "%Y")))

and not suffer performance penalties when archiving sent mail.

Re: make it easier to use nnml for archive groups

[Lars Magne Ingebrigtsen]

Dan Nicolaescu <dann@gnu.org> writes:

> Can the configuration for using nnml as the archive method be made easier?
>
> This is what's in my .gnus.el:
>
> (setq gnus-message-archive-method
>       '(nnml "archive"
>              (nnml-directory "~/Mail/archive")
>              (nnml-active-file "~/Mail/archive/active")
>              (nnml-get-new-mail nil)
>              (nnml-inhibit-expiry t)))

Easier as in "fewer lines of method conf"?  I don't really think so...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: make it easier to use nnml for archive groups

[Dan Nicolaescu]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Dan Nicolaescu <dann@gnu.org> writes:
>
>> Can the configuration for using nnml as the archive method be made easier?
>>
>> This is what's in my .gnus.el:
>>
>> (setq gnus-message-archive-method
>>       '(nnml "archive"
>>              (nnml-directory "~/Mail/archive")
>>              (nnml-active-file "~/Mail/archive/active")
>>              (nnml-get-new-mail nil)
>>              (nnml-inhibit-expiry t)))
>
> Easier as in "fewer lines of method conf"?  I don't really think so...

How about documenting the nmml method in the manual?  It's not easy to
figure out what one needs to enable it.

How about just enabling archiving by default?  Most mailers do that,
so it won't be unexpected...

Re: make it easier to use nnml for archive groups

[Lars Magne Ingebrigtsen]

Dan Nicolaescu <dann@gnu.org> writes:

> How about just enabling archiving by default?  Most mailers do that,
> so it won't be unexpected...

Should we just default `gnus-message-archive-group' to "archive" or
something? 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: make it easier to use nnml for archive groups

[Dan Nicolaescu]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Dan Nicolaescu <dann@gnu.org> writes:
>
>> How about just enabling archiving by default?  Most mailers do that,
>> so it won't be unexpected...
>
> Should we just default `gnus-message-archive-group' to "archive" or
> something? 

IMHO, yes.  And , IMHO, he default archive method should be nmml.

Re: make it easier to use nnml for archive groups

[Lars Magne Ingebrigtsen]

Dan Nicolaescu <dann@gnu.org> writes:

>> Should we just default `gnus-message-archive-group' to "archive" or
>> something? 
>
> IMHO, yes.

What do y'all think?

> And , IMHO, he default archive method should be nmml.

I don't this should change.  nnfolder is an OK compromise between speed
and a (low) number of files.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: make it easier to use nnml for archive groups

[Ted Zlatanov]

On Mon, 18 Oct 2010 21:13:11 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Dan Nicolaescu <dann@gnu.org> writes:
>>> Should we just default `gnus-message-archive-group' to "archive" or
>>> something? 
>> 
>> IMHO, yes.

LMI> What do y'all think?

I sort of agree.  This is something I would expect to be asked to
customize the first time I start a MUA, but not to have enabled by
default.

Maybe this is a good use for assistant.el: if gnus-message-archive-group
is not set to 'no-thanks, run a simple assistant to configure the method.

>> And , IMHO, he default archive method should be nmml.

LMI> I don't this should change.  nnfolder is an OK compromise between speed
LMI> and a (low) number of files.

Depends on the user.  For me nnmaildir would be best.

Ted

Re: make it easier to use nnml for archive groups

[Lars Magne Ingebrigtsen]

Ted Zlatanov <tzz@lifelogs.com> writes:

> LMI> What do y'all think?
>
> I sort of agree.  This is something I would expect to be asked to
> customize the first time I start a MUA, but not to have enabled by
> default.

Yes.  Unfortunately, Gnus doesn't really start up with a selection pane,
so we just have to pick sensible defaults.

Unless somebody objects, I'm going to make the archive group default to
the following:

((concat "sent."
          (format-time-string
           "%Yw%U" (current-time))))

That'll create one folder per week.           
           
-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: make it easier to use nnml for archive groups

[Ted Zlatanov]

On Tue, 19 Oct 2010 20:22:59 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
LMI> What do y'all think?
>> 
>> I sort of agree.  This is something I would expect to be asked to
>> customize the first time I start a MUA, but not to have enabled by
>> default.

LMI> Yes.  Unfortunately, Gnus doesn't really start up with a selection pane,
LMI> so we just have to pick sensible defaults.

Why not?  One of the perpetual complaints is that Gnus is hard to
configure (just do a search outside the Gnus venues, like Emacs and
general MUA discussions).  Perhaps we can remedy that.  

I don't know how to use assistant.el well (it's been years since you
wrote it) but I think it's reasonable to check if this is the first time
someone starts Gnus and then run assistants accordingly.  We should
provide assistants to:

- set up mail servers (providing a fast path for GMail and other popular
  ones)

- set up NNTP servers (including GMane and GWene)

- set up archiving, expiry, spam.el, gnus-registry, gnus-sync, etc. (I'm
  listing just my ideas, this should be everything useful)

Ted

Re: make it easier to use nnml for archive groups

[Lars Magne Ingebrigtsen]

Ted Zlatanov <tzz@lifelogs.com> writes:

> I don't know how to use assistant.el well (it's been years since you
> wrote it) but I think it's reasonable to check if this is the first time
> someone starts Gnus and then run assistants accordingly.  We should
> provide assistants to:
>
> - set up mail servers (providing a fast path for GMail and other popular
>   ones)
>
> - set up NNTP servers (including GMane and GWene)
>
> - set up archiving, expiry, spam.el, gnus-registry, gnus-sync, etc. (I'm
>   listing just my ideas, this should be everything useful)

We should, definitely.  But I ran out of steam last time.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

assistants, again (was: make it easier to use nnml for archive groups)

[Ted Zlatanov]

On Tue, 19 Oct 2010 20:50:50 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I don't know how to use assistant.el well (it's been years since you
>> wrote it) but I think it's reasonable to check if this is the first time
>> someone starts Gnus and then run assistants accordingly.  We should
>> provide assistants to:
>> 
>> - set up mail servers (providing a fast path for GMail and other popular
>> ones)
>> 
>> - set up NNTP servers (including GMane and GWene)
>> 
>> - set up archiving, expiry, spam.el, gnus-registry, gnus-sync, etc. (I'm
>> listing just my ideas, this should be everything useful)

LMI> We should, definitely.  But I ran out of steam last time.  :-)

I'll work on it.  I really need you to explain how assistants work,
though.  Your parse, render, and data assembly code makes sense when I
read it but in practice (writing actual .ast files) it's hard to use.
Plus it's not obvious to me how to make assisted changes permanent: do I
need to write a converter or can assistant.el customize things directly?

Ted

Re: assistants, again

[Lars Magne Ingebrigtsen]

Ted Zlatanov <tzz@lifelogs.com> writes:

> I'll work on it.

Great!

> I really need you to explain how assistants work, though.  Your parse,
> render, and data assembly code makes sense when I read it but in
> practice (writing actual .ast files) it's hard to use.  Plus it's not
> obvious to me how to make assisted changes permanent: do I need to
> write a converter or can assistant.el customize things directly?

I think you need to hook it into customize, probably, if I remember
correctly.  I meant to write that bit, but didn't get around to it.

If the .ast file format is difficult to use, feel free to change the
format to something better.  I don't think this is used by anybody.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: assistants, again

[Ted Zlatanov]

On Tue, 19 Oct 2010 21:08:48 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I'll work on it.

LMI> Great!

Heh.  Maybe I'll get to it by Christmas.  Not the one in 2010.

>> I really need you to explain how assistants work, though.  Your parse,
>> render, and data assembly code makes sense when I read it but in
>> practice (writing actual .ast files) it's hard to use.  Plus it's not
>> obvious to me how to make assisted changes permanent: do I need to
>> write a converter or can assistant.el customize things directly?

LMI> I think you need to hook it into customize, probably, if I remember
LMI> correctly.  I meant to write that bit, but didn't get around to it.

OK.  Is it supposed to be hooked into one of the :get or :initialize
`defcustom' options?  I have never touched those areas.  The alternate
is to just use 'finish to directly set some variables so assistant.el is
standalone.

LMI> If the .ast file format is difficult to use, feel free to change the
LMI> format to something better.  I don't think this is used by anybody.

No, I mean it's like Lego blocks: I understand each piece but don't know
how to put together a big assembly.  The parser is fine, the format is
fine, but I need to see at least one complete example to do it.  It
doesn't have to be a full example, it can be just a variable with two
configuration paths: either it's a single choice of symbols or a list of
symbols or sublists (to show recursion).  So given the choices 'one,
'two, 'three, show me how to customize a variable to have these possible
values:

'one
nil
'(one two)
'((one two) (three))

...and make it permanent afterwards.

That will be most of what I need and I can figure out the rest.

Ted

Re: assistants, again

[Lars Magne Ingebrigtsen]

Ted Zlatanov <tzz@lifelogs.com> writes:

> Heh.  Maybe I'll get to it by Christmas.  Not the one in 2010.

Darn!

> LMI> I think you need to hook it into customize, probably, if I remember
> LMI> correctly.  I meant to write that bit, but didn't get around to it.
>
> OK.  Is it supposed to be hooked into one of the :get or :initialize
> `defcustom' options?  I have never touched those areas.  The alternate
> is to just use 'finish to directly set some variables so assistant.el is
> standalone.

Hm...  I don't remember.  :-/  Sorry.

> No, I mean it's like Lego blocks: I understand each piece but don't know
> how to put together a big assembly.  The parser is fine, the format is
> fine, but I need to see at least one complete example to do it.  It
> doesn't have to be a full example, it can be just a variable with two
> configuration paths: either it's a single choice of symbols or a list of
> symbols or sublists (to show recursion).  So given the choices 'one,
> 'two, 'three, show me how to customize a variable to have these possible
> values:
>
> 'one
> nil
> '(one two)
> '((one two) (three))

Hm.  I'm not quite sure whether assistant is geared towards that complex
variables, but I think something like the :radio thing would help there?
It might just lack an implementation for a complex type.

> ...and make it permanent afterwards.

That's not implemented yet, I think.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: assistants, again

[Ted Zlatanov]

On Tue, 19 Oct 2010 14:01:31 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

>>> I don't know how to use assistant.el well (it's been years since you
>>> wrote it) but I think it's reasonable to check if this is the first time
>>> someone starts Gnus and then run assistants accordingly.  We should
>>> provide assistants to:
>>> 
>>> - set up mail servers (providing a fast path for GMail and other popular
>>> ones)
>>> 
>>> - set up NNTP servers (including GMane and GWene)
>>> 
>>> - set up archiving, expiry, spam.el, gnus-registry, gnus-sync, etc. (I'm
>>> listing just my ideas, this should be everything useful)

- also set gnus-blocked-images to something other than "." because the
  default is really annoying (but the user needs to approve in case they
  are paranoid)

Ted

Re: assistants, again

[Ted Zlatanov]

On Wed, 20 Oct 2010 07:14:13 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> On Tue, 19 Oct 2010 14:01:31 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 
>>>> I don't know how to use assistant.el well (it's been years since you
>>>> wrote it) but I think it's reasonable to check if this is the first time
>>>> someone starts Gnus and then run assistants accordingly.  We should
>>>> provide assistants to:
>>>> 
>>>> - set up mail servers (providing a fast path for GMail and other popular
>>>> ones)
>>>> 
>>>> - set up NNTP servers (including GMane and GWene)
>>>> 
>>>> - set up archiving, expiry, spam.el, gnus-registry, gnus-sync, etc. (I'm
>>>> listing just my ideas, this should be everything useful)

TZ> - also set gnus-blocked-images to something other than "." because the
TZ>   default is really annoying (but the user needs to approve in case they
TZ>   are paranoid)

- also set the HTML renderer to mm-shr or something else

(yes, this is turning into a TODO list, feel free to add other things)

Ted

Re: assistants, again

[Julien Danjou]

On Wed, Oct 20 2010, Ted Zlatanov wrote:

> - also set the HTML renderer to mm-shr or something else

You mean mm-text-html-renderer? That's already the case.
Or do you mean something else?

-- 
Julien Danjou
// ᐰ <julien@danjou.info>   http://julien.danjou.info

Re: assistants, again

[Ted Zlatanov]

On Wed, 20 Oct 2010 17:33:59 +0200 Julien Danjou <julien@danjou.info> wrote: 

JD> On Wed, Oct 20 2010, Ted Zlatanov wrote:
>> - also set the HTML renderer to mm-shr or something else

JD> You mean mm-text-html-renderer? That's already the case.
JD> Or do you mean something else?

I mean either that or `gnus-article-wash-function' which defaults to
`mm-text-html-renderer'.  I'm not sure which one is right.

But my point is to give the user a choice instead of a default:

1) experimental very fast shr.el
2) fast reliable (but tricky on MacOS X and Windows) w3m
3) links
4) etc.

...if they have never customized this aspect of Gnus.

Ted

Re: assistants, again

[Lars Magne Ingebrigtsen]

Ted Zlatanov <tzz@lifelogs.com> writes:

> I mean either that or `gnus-article-wash-function' which defaults to
> `mm-text-html-renderer'.  I'm not sure which one is right.

Geez!  There's another one of these variables?

I'm now going to rip out all the variables that say they determine how
HTML is rendered, other than `mm-text-html-renderer'.  (I think there's
a least four.)  This will probably lead to changed behaviour for some,
but c'est la jennesequa.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: assistants, again

[Ted Zlatanov]

On Wed, 20 Oct 2010 18:42:19 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I mean either that or `gnus-article-wash-function' which defaults to
>> `mm-text-html-renderer'.  I'm not sure which one is right.

LMI> Geez!  There's another one of these variables?

LMI> I'm now going to rip out all the variables that say they determine how
LMI> HTML is rendered, other than `mm-text-html-renderer'.  (I think there's
LMI> a least four.)  This will probably lead to changed behaviour for some,
LMI> but c'est la jennesequa.

Great.  Thanks for cutting that knot.

Ted

Re: assistants, again

[Lars Magne Ingebrigtsen]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> I'm now going to rip out all the variables that say they determine how
> HTML is rendered, other than `mm-text-html-renderer'. 

The "HTML washing" code is now gone, too.  Instead, it just calls the
"HTML rendering" code directly.

There was some charset stuff in there, too, but I didn't quite
understand what the point was, since there's other commands for changing
the charset, isn't there?  If I've misunderstood something in that dept,
please resurrect the charset code in `article-wash-html'.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: assistants, again

[Lars Magne Ingebrigtsen]

Ted Zlatanov <tzz@lifelogs.com> writes:

> - also set gnus-blocked-images to something other than "." because the
>   default is really annoying (but the user needs to approve in case they
>   are paranoid)

I've now changed the default (as previously discussed) to something that
uses `gnus-news-group-p'.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: make it easier to use nnml for archive groups

[Andreas Schwab]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Unless somebody objects, I'm going to make the archive group default to
> the following:
>
> ((concat "sent."
>           (format-time-string
>            "%Yw%U" (current-time))))

aka (format-time-string "sent.%Yw%U" (current-time)).

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: make it easier to use nnml for archive groups

[Reiner Steib]

On Tue, Oct 19 2010, Andreas Schwab wrote:

> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> Unless somebody objects, I'm going to make the archive group default to
>> the following:
>>
>> ((concat "sent."
>>           (format-time-string
>>            "%Yw%U" (current-time))))
>
> aka (format-time-string "sent.%Yw%U" (current-time)).

I think one group per week is not a good choice.  I don't think many
people are able to remember "I wrote this mail in week no. 42".  And
many user run a Gnus session over week boundaries, I guess (I assume
the value is set only at Gnus startup).

I'd suggest one group per year (or month).  And offer "per week,
month, year" as predefined choices in customize.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

Re: make it easier to use nnml for archive groups

[Ted Zlatanov]

On Wed, 20 Oct 2010 08:31:47 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 

RS> On Tue, Oct 19 2010, Andreas Schwab wrote:
>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> 
>>> Unless somebody objects, I'm going to make the archive group default to
>>> the following:
>>> 
>>> ((concat "sent."
>>> (format-time-string
>>> "%Yw%U" (current-time))))
>> 
>> aka (format-time-string "sent.%Yw%U" (current-time)).

RS> I think one group per week is not a good choice.  I don't think many
RS> people are able to remember "I wrote this mail in week no. 42".  And
RS> many user run a Gnus session over week boundaries, I guess (I assume
RS> the value is set only at Gnus startup).

RS> I'd suggest one group per year (or month).  And offer "per week,
RS> month, year" as predefined choices in customize.

How about these choices:

"%Y-%m"    ; 2010-01
"%Y-%m-%d" ; 2010-01-01
"%Y-%B"    ; 2010-October (as per locale)

I would not use the week number in any way.  I don't know anyone who
remembers the week number 3 months ago, so it's just a hash bucket.

Ted

Re: make it easier to use nnml for archive groups

[Dan Nicolaescu]

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Wed, 20 Oct 2010 08:31:47 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 
>
> RS> On Tue, Oct 19 2010, Andreas Schwab wrote:
>>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>>> 
>>>> Unless somebody objects, I'm going to make the archive group default to
>>>> the following:
>>>> 
>>>> ((concat "sent."
>>>> (format-time-string
>>>> "%Yw%U" (current-time))))
>>> 
>>> aka (format-time-string "sent.%Yw%U" (current-time)).
>
> RS> I think one group per week is not a good choice.  I don't think many
> RS> people are able to remember "I wrote this mail in week no. 42".  And
> RS> many user run a Gnus session over week boundaries, I guess (I assume
> RS> the value is set only at Gnus startup).
>
> RS> I'd suggest one group per year (or month).  And offer "per week,
> RS> month, year" as predefined choices in customize.
>
> How about these choices:
>
> "%Y-%m"    ; 2010-01
> "%Y-%m-%d" ; 2010-01-01
> "%Y-%B"    ; 2010-October (as per locale)
>
> I would not use the week number in any way.  I don't know anyone who
> remembers the week number 3 months ago, so it's just a hash bucket.

One archive per month is too much too, after about 3 years there's too
many groups, and there's no way to automatically compact them.
One archive per year is better, the only limitation is that the
nnfolder default would blow up really really fast.

Re: make it easier to use nnml for archive groups

[Ted Zlatanov]

On Wed, 20 Oct 2010 11:32:39 -0400 Dan Nicolaescu <dann@gnu.org> wrote: 

DN> Ted Zlatanov <tzz@lifelogs.com> writes:
>> On Wed, 20 Oct 2010 08:31:47 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 
>> 
RS> On Tue, Oct 19 2010, Andreas Schwab wrote:
>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>>>> 
>>>>> Unless somebody objects, I'm going to make the archive group default to
>>>>> the following:
>>>>> 
>>>>> ((concat "sent."
>>>>> (format-time-string
>>>>> "%Yw%U" (current-time))))
>>>> 
>>>> aka (format-time-string "sent.%Yw%U" (current-time)).
>> 
RS> I think one group per week is not a good choice.  I don't think many
RS> people are able to remember "I wrote this mail in week no. 42".  And
RS> many user run a Gnus session over week boundaries, I guess (I assume
RS> the value is set only at Gnus startup).
>> 
RS> I'd suggest one group per year (or month).  And offer "per week,
RS> month, year" as predefined choices in customize.
>> 
>> How about these choices:
>> 
>> "%Y-%m"    ; 2010-01
>> "%Y-%m-%d" ; 2010-01-01
>> "%Y-%B"    ; 2010-October (as per locale)
>> 
>> I would not use the week number in any way.  I don't know anyone who
>> remembers the week number 3 months ago, so it's just a hash bucket.

DN> One archive per month is too much too, after about 3 years there's too
DN> many groups, and there's no way to automatically compact them.
DN> One archive per year is better, the only limitation is that the
DN> nnfolder default would blow up really really fast.

I think it should be up to the user; "%Y" can be an option too.

Ted

Re: make it easier to use nnml for archive groups

[Robert Pluim]

Ted Zlatanov <tzz@lifelogs.com> writes:

> I would not use the week number in any way.  I don't know anyone who
> remembers the week number 3 months ago, so it's just a hash bucket.

Plus there are disagreements between different countries as to what is
'week 1' (at least between Germany and France that I'm aware of)

Robert

Re: make it easier to use nnml for archive groups

[Lars Magne Ingebrigtsen]

Ted Zlatanov <tzz@lifelogs.com> writes:

> How about these choices:
>
> "%Y-%m"    ; 2010-01

I went with this as the default.

> "%Y-%B"    ; 2010-October (as per locale)

Although this might be nice, too...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: make it easier to use nnml for archive groups

[Lars Magne Ingebrigtsen]

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> I'd suggest one group per year (or month).  And offer "per week,
> month, year" as predefined choices in customize.

Sounds good.  Done.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: make it easier to use nnml for archive groups

[Dan Nicolaescu]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> LMI> What do y'all think?
>>
>> I sort of agree.  This is something I would expect to be asked to
>> customize the first time I start a MUA, but not to have enabled by
>> default.
>
> Yes.  Unfortunately, Gnus doesn't really start up with a selection pane,
> so we just have to pick sensible defaults.
>
> Unless somebody objects, I'm going to make the archive group default to
> the following:
>
> ((concat "sent."
>           (format-time-string
>            "%Yw%U" (current-time))))
>
> That'll create one folder per week.           

That would be very annoying, that many folders are very hard to manage...