bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: find-file-read-only then set-buffer-file-coding-system ...


From: Eli Zaretskii
Subject: Re: find-file-read-only then set-buffer-file-coding-system ...
Date: Sat, 03 Feb 2001 12:35:45 +0200

[For the umpteenth time, PLEASE stop using a fake address in this
forum!]
> From: Dan Jacobson <address@hidden>
> Newsgroups: gnu.emacs.bug
> Date: 02 Feb 2001 16:11:06 +0800
> 
> Something less then ideal is happening here: Using
> find-file-read-only, or view-mode, then upon, say, seeing the coding
> system might need a little adjustments to view the file better, doing
> set-buffer-file-coding-system ... ok, now when we are thru viewing,
> etc. using q or C-x k, one gets big warnings about buffer modified,
> kill anyway [yes no]? etc.

Why would you need to change buffer-file-coding-system in this
situation?  If you wanted to get Emacs to display the buffer
differently, then changing buffer-file-coding-system won't cut it: it
only changes how Emacs will save the buffer, but does nothing to
buffer's text.

To have the file decoded differently, kill the buffer and visit it
again, this time using "C-x RET c CODING-SYSTEM RET" immediately
before find-file-read-only.

The fact that Emacs sets the buffer's modified flag when you change
the buffer's coding system is a feature: it reflects the fact that the
file on disk would have been changed if you save it.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]