* darren chamberlain ([EMAIL PROTECTED]) wrote: > I'm going to reply to a bunch of messages all at once. I'm > attaching my first quick attempt at a configuration script; I've > called mutt-makeconfig, for lack of a better name. It's very > brute force, but it works. The config is very basic, enough to > get the bare minimum of personalized part of the process done > (ie, it sets realname, from, alternates, editor, folder, > mbox_type, print_command, and sendmail). It's written in perl, > uses only standard (5.00505+) modules, and runs reasonably fast. > The options it takes are --muttrc (where it should write the > file, default /tmp/muttrc-$USER) and --color (a useless option to > make it purty).
I think a major improvement would be to store the configuration file (sorry for the buzzword) metainfo seperately. Have a parsable file containg the options, possible values, and description. This will make adding new configuration directives much easier than writing (and reusing) code for each one. Opinions? > And, just so everyone knows, I'm not really attached to the > script, they way it does things, the language it's written in, or > the choice of colors on the screen, so spare no flames. :) IT SUCKS! :) > Quoting Will Yardley <[EMAIL PROTECTED]> in ><[EMAIL PROTECTED]>: > > regarding cvs space, i've never setup a cvs pserver before; i'm > > assuming this will be the easiest way to offer anonymous CVS > > access. i doubt it's that hard to setup though. > > Anonymous CVS access is not enough, because the folks working on > it will need write access; that means user accounts. If we make > it a sourceforge project, then all the hard work is handled for > us, at least in that department. sf.net was /made/ for this sort of project. It seems a shame not to use it. [...] > I agree entirely. sh is the most likely candidate, if we are > going for it to run absolutely everywhere (I'd say awk would be > the second, followed by perl). The script I've written doesn't > too (too many) Perl-ish things and should be strightforward to > port to whatever languagewe decide to use, if that's what is > wanted. I vote Perl, but it looks like that's the programming lingua franca for this list anyhow. > The Feynman Problem 1) Write down the problem. > Solving Algorithm 2) Think real hard. > 3) Write down the answer. Have you read /Genius/ by James Gleick? Great book. /me sees the ball start to rock... mike ps: Coincidentily, I'm in the process of developing an ancillary tool for people trying to get GPG+mutt working fast and easy.
