[EMAIL PROTECTED] writes: > [If somebody gets this twice (thrice?) I apologize, used the wrong sender > first two tries.] > > Hi, > > I'm a recently converted nmh/exmh user. There were a couple of things > I found missing that I hacked in. There's also a couple of less necessary > things that I added just for the heck of it. My question is whether > anyone would be interested in these changes, and in what format I should > send patches (split up per feature or everything in one big blob). > > - etcpath to searchpath. > I created a new routine searchpath to replace etcpath. If given > a filename without leading '/' or '~' it searches the folder > and all its parents before searching ~/Mail and /etc/nmh. > While I was writing this into nmh the same feature was also put > into exmh, but nmh would be a cleaner location? Aren't there usability and security concerns with this? Won't some people suddenly start getting different components files than the ones they expect if they don't change their .mh_profile to prepend '~/<`mhparam path`>' to all components filenames? I think it'd be safer to check the current directory (but not its parent tree -- why do you need that?) *last*, with an option to force the components file in the current directory by using './'..., just like with $PATHs. > - formatted components for comp. > I wanted a formatted components file for comp because I want to > automatically 'Fcc:' to the current folder. > > - folder components escape. > The current/target/something folder can be used from your > formatted components files. > > - userflags and component escapes. > comp and repl were extended with a '-userflag key=value' option that > allows the user to add any needed component escape from the commandline. > Makes it easier to use one componentfile for multiple uses. > > These features were only implemented for comp and repl. dist and forw > haven't been tackled yet because I'm not completely comfortable with all > their features. > > So, is anyone interested or shall I keep them to myself? > > Tobias Nijweide I don't have a personal interest in the components changes, but I can see how they'd be useful, and at first glance they don't seem to have undesirable consequences like your etcpath change. Why don't you post the diffs to the list and see if anyone takes it upon themselves to commit them? Separate diffs per feature are of course preferable, but if that's hard to achieve, it seems like those three changes are related enough that a single diff would be acceptable. Just make sure the diff is against the latest CVS source so the patches work properly and don't get rejected. Frankly, though, you'd increase the chances of the patches getting applied if the new features were implemented across the board and if you updated the documentation to reflect the changes (you didn't mention whether or not you'd done this). ----------------------------------------------------------------------- Dan Harkless | To prevent SPAM contamination, please [EMAIL PROTECTED] | do not post this private email address SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
