forwarded 560182 https://sourceforge.net/tracker/?func=detail&aid=2911550&group_id=23475&atid=378598 thanks,
C.f. Debian bug http://bugs.debian.org/560182 Josip Rodin <[email protected]> writes: > On Wed, Dec 09, 2009 at 05:15:09PM +0200, Jari Aalto wrote: >> >> joe /tmp/test.txt >> >> Warning: /etc/joe/joerc is newer than your /home/foo/.joerc. >> >> You should update or delete /home/foo/.joerc >> >> Hit enter to continue with /etc/joe/joerc >> >> >> >> Program should always prefer $HOME dot files over /etc. >> > >> > It's warning you that you have to verify that your local syntax is >> > up to date, because if it's not, your joe may become broken. >> > Once you do that, even if you make no changes, just touch the file and >> > the check condition will no longer trigger. >> > >> > The check is valid, but if you wish to update the verbiage, please suggest. >> >> There a many problems >> >> - The program should never use the /etc no mattet how broken users setup >> is. If the user's setup cannot be used, it should simply die with a >> proper error message. > > It does that, arguably better - it gives you a warning message and falls > back to the defaults. The program currently overrides user's settings in every case when the timestamp differs. This is not correct behavior. The program should refuse to start if the setup cannot be parsed. But there is no error here. >> - There is no need to notify user about new file in /etc because the >> upgrades always possibly bring new files. Every user can consult >> the documentation about new features from the manual pages. > > joe's authors thought it's better to inform the user explicitly. > It's erring on the side of caution, and I don't object to it. "Side of caution"? Have more similar of these kind of "checks" and we have soon the "The Windows (tm) experience" There is a manual page to document the chnages. There is a NEWS files to announce changes. It's much clearer for programs to follow the standard procedures: - If setup cannot be parsed, exit with status code and print an error. - Otherwise continue with stadard parsing rules: user's settings first in $HOME. If not dound, use system defaults. It's a good to find out that a mere upgrade causes next version to <blink> and <beep> and <pause> ... for nothing; when setup is not broken. Jari -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
