[EMAIL PROTECTED] writes: > > > - 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. > > With current directory you mean current folder, or really current directory? Okay, I'm sorry. I misread your initial description. I thought you were saying directory rather than mail folder. My security concerns came from imagining it climbing all the way up to the '/' directory looking for components files. My usability concerns came from imagining having a components file in the current directory that you don't want to override your ~/`mhparam path` version or the system version. Now I understand your feature, and it sounds like a good addition. > > 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). > > That's why I first sent my request for interest to the list. Stuff works > satisfactorily for me now. If nobody wanted it, I wouldn't have bothered > with documentation and parts that I don't use. > > I'll split up the searchpath and components changes and flesh them out > a bit more, and put them on the list when they work. Great! Thanks a lot for your contribution. ----------------------------------------------------------------------- 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.
