From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Joseph Brenner Newsgroups: gmane.emacs.help Subject: Re: coding systems Date: Tue, 03 Nov 2009 11:11:28 -0800 Message-ID: <87vdhrtodb.fsf@kzsu.stanford.edu> References: <87k4y8xwvb.fsf@kzsu.stanford.edu> <874opcvzbx.fsf@lion.rapttech.com.au> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1257277257 23815 80.91.229.12 (3 Nov 2009 19:40:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 3 Nov 2009 19:40:57 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Nov 03 20:40:50 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1N5PFD-0002rz-52 for geh-help-gnu-emacs@m.gmane.org; Tue, 03 Nov 2009 20:40:43 +0100 Original-Received: from localhost ([127.0.0.1]:50242 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N5PFC-0005uG-MJ for geh-help-gnu-emacs@m.gmane.org; Tue, 03 Nov 2009 14:40:42 -0500 Original-Path: news.stanford.edu!usenet.stanford.edu!postnews.google.com!news1.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.posted.rawbandwidth!news.posted.rawbandwidth.POSTED!not-for-mail Original-NNTP-Posting-Date: Tue, 03 Nov 2009 13:11:16 -0600 Original-Newsgroups: gnu.emacs.help User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:1cE9nxVraK6e2AtpeDAGMvIVMM4= Original-Lines: 46 X-Usenet-Provider: http://www.giganews.com Original-NNTP-Posting-Host: 198.144.208.84 Original-X-Trace: sv3-QSx6FeFkwdW3U38BHuAwFn0jRVEaqv5NxuKtk2ZOt+GoVufk+aKFICrDotYaFW2xtt2QcjX9c7grVt6!nf7J0zlBOvV05oBejqpuM+fxUUQxg0IqD7kZTlNQjK32uY4Og+pZHVtV/7XflC2SmOmldkeZRIo= X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 Original-Xref: news.stanford.edu gnu.emacs.help:174370 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:69447 Archived-At: Tim X writes: > Joseph Brenner writes: > >> What is the simplest possible thing I can do to convince emacs >> to never, ever, bug me about what coding system a file should be >> saved under? >> >> For extra points, a solution that minimizes data lossage would be >> nice, but not strictly necessary from my point of view. I just >> want the "Select a coding system" question to go away. >> > > What version of emacs? There have been considerable changes, especially > in emacs 23 that may affect what solution is best. Yes, I should've mentioned that I'm running a cvs emacs, of late-October vintage. > It has been a long time since I've even seen this question. It's been a low-grade issue with me for some time. If I cut-and-paste something from a firefox window to some notes in an emacs file, there's invariable a "smart quote", or an emdash or something that emacs doesn't know what to do with. More recently, I've started seeing a worse problem: there's a package I've been working on to use desktop.el for things like intelligent crash recovery ("desktop-recover.el", at a github near you). When there are some international characters stashed in a register that "desktop-save" wants to preserve, then I'm asked for a coding system not just once, but every single time the auto-save-hook fires, because I use it to do automatic "desktop-save"s. > Given the improvements in emacs 23 for coding systems, I'd recommend > upgrading to emacs 23 if your not already using it and then start > diagnosing the issue to find a solution. You're probably right that emacs 23 is the way to go on this, but then a side-effect of the improvements is that the documentation has gotten a little more complicated. It is a point that I should make sure I don't have any cruft from older emacs in my set-up files.