>> ruserpass(), which is unreliably detected and possibly implemented. I >> think the TODO mentions some other functions, like snprintf, which aren't >> implemented yet, but it makes sense to have that section in the README.dev >> as a placeholder. > >Yeah, if we _ever_ use the system functions, as we do with snprint(), they >shouldn't go in that section. > >But if we sometimes use the vendor ruserpass(), then our nmh_getpass() won't >get called -- we need to always use our ruserpass() or else rename >nmh_getpass() back to getpass() (assuming vendor ruserpass() functions >always call getpass()). System ruserpass is never used. I removed the dependency because of this kind of complication. Shantonu *-------------------------------------------* |Shantonu Sen * (617)225-6778 * [EMAIL PROTECTED]| |Electrical Engineering and Computer Science| |Massachusetts Institute of Technology, 2002| *-------------------------------------------*
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Glenn Burkhardt
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Shantonu Sen
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Doug Morris
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Dan Harkless
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Shantonu Sen
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Shantonu Sen
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Dan Harkless
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Shantonu Sen
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Dan Harkless
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Dan Harkless
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Shantonu Sen
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Dan Harkless
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems John Summerfield
- Re: nmh 1.0.4 doesn't work as POP client on LInux systems Dan Harkless