Re: Working on the install-mh change questions
Jon Steinhart <[EMAIL PROTECTED]> wrote: > 5.There's code that removes a trailing / from mypath if mypath is more > than one character long. Seems completely unnecessary; the definition > of path names means that // is interpreted as /. And if that wasn't > the case, this code wouldn't catch multiple trailing slashes anyway. I'm not familiar enough with the MH code to know about the other issues, but with this one, if the path is shown to the user in any way, at worst this is a nice cosmetic fix. At best, it saves the user from opening the wrong file if he cut and pastes the path into Emacs, for example. Thanks for taking the time to clean things up. -- Bill Wohler <[EMAIL PROTECTED]> http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and mh-e. Vote Libertarian! If you're passed on the right, you're in the wrong lane.
install-mh location
Well, here's a minor detail that could cause problems. I have a version of nmh here that has sbr/context_read modified to give a "run install-mh" message if mh isn't installed rather than doing it for the user as per yesterday's discussion. But, install-mh is not likely to be in the user's path; it's in the lib directory. Should I change the installation to move this to the bin directory or to make a link from the bin to the lib directory? Jon
Re: install-mh location
Jon Steinhart <[EMAIL PROTECTED]> wrote: >Well, here's a minor detail that could cause problems. >I have a version of nmh here that has sbr/context_read >modified to give a "run install-mh" message if mh >isn't installed rather than doing it for the user as >per yesterday's discussion. >But, install-mh is not likely to be in the user's path; >it's in the lib directory. Should I change the >installation to move this to the bin directory or to >make a link from the bin to the lib directory? Make a sym-link, or put in a shell script. -NWR
Re: nmh 1.1 release canidate uploaded
Scott Lipcon <[EMAIL PROTECTED]> wrote: > I don't think release candidates belong in the ports collection. 1.1rc1 > should be relatively stable, but it hasn't been tested much at this point. > Development has gone very slowly.If there is enough demand, I'd consider > making a second port, nmh-devel, as is common for some other ports. Ehhh...I don't think there's enough demand to do that. > Alternatively, I'd be willing to figure out how to make a FreeBSD package of > 1.1 rc1 and make it available for download for FreeBSD users who want to give > 1.1 a try. I could probably come up with a package without too much difficulty...would it make sense to stick it in savannah's download area for the nmh project? Or maybe just assume that most people who would want to play with the RC code might be able to build it for themselves and not worry about it? I don't know...being kinda swamped at work right now, I'm inclined to go that way unless there's some sort of outcry :). Scott
Re: Appropriateness of new program/feature
>> >It's always bugged me that MH/nmh starts to install a new user setup if >I guess that I wasn't being brave enough to suggest changing the way that >things worked. I'll give it a few days to settle out, and then make the >above change if no major objections arise. No objection from me. --Ken
