| Tom Plagge on Thu, 2 Dec 2004 14:03:46 -0600 (CST) |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| Re: [nimh-dev] MH sequences |
We'll need something like a ~/.nimh_profile file, then, unless we want to force
the path ~/Mail upon our users. I prefer ~/mail myself, and forcing ~/Mail
would cause problems for people who occasionally use Netscape mail (for
example). This is the reason I was initially thinking of having a ~/.nimh
directory. Alternative proposals?
-t
> > Another thing we should decide on soon is how to store configuration and
> > state variables. I'm thinking about having the following directory setup:
> > ~/.nimh/state/: Current folder, sequences for each folder, lock files, etc.
> > ~/.nimh/config/: Profile, MIME config, replcomps, components, aliases, etc.
> > ~/mail/: Folders and messages
> > /usr/local/share/nimh/config: Default configuration files
>
>
> How about just {FOLDER}/.nimh/ for per-folder state files and then store
> any and all configurations within $MAILDIR as normal (unhidden) files,
> or, at least $MAILDIR/nimh_config? I don't think configuration files
> should be hidden.
>
> I would really love to have an additional command:
>
> catm +folder messagelist
>
> It's just an mh-aware wrapper to cat.
>
>
> Jon
> --
> Jon Stewart Advanced Los Angeles C++
> stew1@xxxxxxxxxxx http://www.alacpp.org
>
________________________________________________________________________
Tom Plagge UC Berkeley Physics Dept.
351 LeConte Hall Voice: (510) 643-1650
Berkeley, CA 94720 Email: tplagge@xxxxxxxxxxxxxxxxx
________________________________________________________________________
_______________________________________________
nimh-dev mailing list
nimh-dev@xxxxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/nimh-dev