|
From: | Emacs bug Tracking System |
Subject: | bug#992: marked as done (coding system for next command not honoured with C-u 0 C-x s) |
Date: | Sun, 5 Oct 2008 12:15:03 -0700 |
Your message dated Sun, 05 Oct 2008 15:09:54 -0400 with message-id <87ljx2voxp.fsf@cyd.mit.edu> and subject line Re: coding system for next command not honoured with C-u 0 C-x s has caused the Emacs bug report #992, regarding coding system for next command not honoured with C-u 0 C-x s to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don@donarmstrong.com immediately.) -- 992: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=992 Emacs Bug Tracking System Contact don@donarmstrong.com with problems
--- Begin Message ---Subject: coding system for next command not honoured with C-u 0 C-x s Date: Wed, 17 Sep 2008 18:39:09 +0200 To reproduce: emacs -Q C-x C-f aaa RET -- create a file aa <write anything, with carriage return> -- write random text C-x RET c dos RET C-x C-s -- save it in Dos mode C-x k RET -- kill the buffer C-x C-f aaa RET -- reload the file <write anything> -- modify it C-x RET c unix RET M-0 C-x C-s -- save in Unix mode, no backup At this point, the buffer should be in Unix mode, but instead it is in Dos mode. Accordingly, the file is saved in Dos mode. The bug only happens with M-0 C-x C-s, not with plain C-x C-s.
--- End Message ---
--- Begin Message ---Subject: Re: coding system for next command not honoured with C-u 0 C-x s Date: Sun, 05 Oct 2008 15:09:54 -0400 The patch I provided earlier seems to DTRT, so I've checked it in.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |