Eugene Sajine <euguess@xxxxxxxxx> writes: > Thank you, but I'm not wrong, as i described the exact same thing > somewhere in my second or third message, without even knowing the > implementation details. I understand the reason WHY it is like it is, > i just don't like it as it is inconsistent and IMHO incorrect. Just try: Create a file. 1) Launch emacs, save and quit. 2) Launch emacs, don't save, and quit. >From outside, it's EXACTLY the same thing. In the first case, emacs will just tell you "no change need to be saved" and quit, in the second, it'll quit. Try deleting the file in the meantime, it won't change the behavior. Now, what would you do about this? Ignore Emacs and force people to use vi? People have been spending a whole thread to explain you that it's not going to work. I think it'll either be time to acknowledge that, or to learn C and write a patch. Or perhaps try to write it in Java to understand why it doesn't work. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html