From 96bcef2ec619f55bf30d929f2da8d920f3c5540d Mon Sep 17 00:00:00 2001 From: Chong Yidong Date: Sun, 3 Oct 2010 00:31:59 -0400 Subject: Remove obsolete use of binary-overwrite-mode in bytecomp (Bug#7001). * emacs-lisp/bytecomp.el (byte-compile-from-buffer): Remove obsolete use of binary-overwrite-mode (Bug#7001). --- lisp/emacs-lisp/bytecomp.el | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) (limited to 'lisp/emacs-lisp/bytecomp.el') diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el index c0dc1764647..b3ac7b83d79 100644 --- a/lisp/emacs-lisp/bytecomp.el +++ b/lisp/emacs-lisp/bytecomp.el @@ -1800,15 +1800,7 @@ With argument ARG, insert value in current buffer after the form." (set-buffer-multibyte t) (erase-buffer) ;; (emacs-lisp-mode) - (setq case-fold-search nil) - ;; This is a kludge. Some operating systems (OS/2, DOS) need - ;; to write files containing binary information specially. - ;; Under most circumstances, such files will be in binary - ;; overwrite mode, so those OS's use that flag to guess how - ;; they should write their data. Advise them that .elc files - ;; need to be written carefully. (There's no point running the - ;; mode hook, so don't call `binary-overwrite-mode'.) - (setq overwrite-mode 'overwrite-mode-binary)) + (setq case-fold-search nil)) (displaying-byte-compile-warnings (with-current-buffer bytecomp-inbuffer (and bytecomp-filename -- cgit v1.2.3