bug#992: coding system for next command not honoured with C-u 0 C-x s

bug#992: coding system for next command not honoured with C-u 0 C-x s

[Francesco Potorti`]

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.

bug#992: coding system for next command not honoured with C-u 0 C-x s

[Chong Yidong]

Does this patch DTRT?

*** trunk/lisp/international/mule-cmds.el.~1.339.~	2008-09-02 11:15:20.000000000 -0400
--- trunk/lisp/international/mule-cmds.el	2008-09-30 17:31:03.000000000 -0400
***************
*** 287,293 ****
  	 (cmd (key-binding keyseq))
  	 prefix)
  
!     (when (eq cmd 'universal-argument)
        (call-interactively cmd)
  
        ;; Process keys bound in `universal-argument-map'.
--- 287,293 ----
  	 (cmd (key-binding keyseq))
  	 prefix)
  
!     (when (memq cmd '(universal-argument digit-argument))
        (call-interactively cmd)
  
        ;; Process keys bound in `universal-argument-map'.

Diff finished.  Tue Sep 30 17:31:41 2008

bug#992: marked as done (coding system for next command not honoured with C-u 0 C-x s)

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]


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

[-- Attachment #2: Type: message/rfc822, Size: 2892 bytes --]

From: Francesco Potorti` <pot@gnu.org>
To: GNU emacs bug list <bug-gnu-emacs@gnu.org>
Subject: coding system for next command not honoured with C-u 0 C-x s
Date: Wed, 17 Sep 2008 18:39:09 +0200
Message-ID: <E1Kg03Z-0001DV-0M@tucano.isti.cnr.it>

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.




[-- Attachment #3: Type: message/rfc822, Size: 1016 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: 992-done@emacsbugs.donarmstrong.com
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
Message-ID: <87ljx2voxp.fsf@cyd.mit.edu>

The patch I provided earlier seems to DTRT, so I've checked it in.