From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs Development <Emacs-devel@gnu.org>
Subject: ASCII-only startup message?
Date: Sat, 26 Dec 2015 09:25:32 -0800 [thread overview]
Message-ID: <567ECD8C.1070408@cs.ucla.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 237 bytes --]
What bug did the attached patch fix? Emacs is supposed to display single quotes
properly even in ASCII-only locales, and if there's a problem with that display
it'd be better to fix the underlying problem than paper over the symptoms.
[-- Attachment #2: 0001-Don-t-produce-non-ASCII-characters-in-scratch.patch --]
[-- Type: text/x-diff, Size: 1111 bytes --]
From 1490096652f405f6e2847a8b5e6842f80e2ec9f1 Mon Sep 17 00:00:00 2001
From: Eli Zaretskii <eliz@gnu.org>
Date: Sat, 26 Dec 2015 18:58:04 +0200
Subject: [PATCH] Don't produce non-ASCII characters in *scratch*
* lisp/startup.el (initial-scratch-message): Quote apostrophes to
avoid producing non-ASCII characters in the *scratch* buffer's
commentary.
---
lisp/startup.el | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lisp/startup.el b/lisp/startup.el
index a31d355..0e36d35 100644
--- a/lisp/startup.el
+++ b/lisp/startup.el
@@ -1430,9 +1430,9 @@ x-apply-session-resources
(put 'cursor 'face-modified t))))
(defcustom initial-scratch-message (purecopy "\
-;; This buffer is for notes you don't want to save, and for Lisp evaluation.
+;; This buffer is for notes you don\\='t want to save, and for Lisp evaluation.
;; If you want to create a file, visit that file with \\[find-file],
-;; then enter the text in that file's own buffer.
+;; then enter the text in that file\\='s own buffer.
")
"Initial documentation displayed in *scratch* buffer at startup.
--
2.5.0
next reply other threads:[~2015-12-26 17:25 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 17:25 Paul Eggert [this message]
2015-12-26 18:16 ` ASCII-only startup message? Eli Zaretskii
2015-12-26 18:41 ` Random832
2015-12-26 18:50 ` Paul Eggert
2015-12-26 19:11 ` Eli Zaretskii
2015-12-26 19:01 ` Eli Zaretskii
2015-12-26 18:45 ` Paul Eggert
2015-12-26 19:10 ` Eli Zaretskii
2015-12-26 19:40 ` Paul Eggert
2015-12-26 20:50 ` Eli Zaretskii
2015-12-26 23:28 ` Paul Eggert
2015-12-27 0:17 ` Drew Adams
2015-12-27 1:03 ` Clément Pit--Claudel
2015-12-27 2:51 ` Drew Adams
2015-12-27 1:09 ` Paul Eggert
2015-12-27 15:56 ` Eli Zaretskii
2015-12-27 18:45 ` Paul Eggert
2015-12-27 6:58 ` Random832
2015-12-27 14:17 ` Per Starbäck
2015-12-27 14:55 ` Drew Adams
2015-12-27 16:35 ` Per Starbäck
2015-12-27 17:42 ` Drew Adams
2015-12-27 19:27 ` Per Starbäck
2015-12-27 22:47 ` Drew Adams
2015-12-27 23:45 ` Per Starbäck
2015-12-28 2:01 ` Drew Adams
2015-12-28 5:51 ` Random832
2015-12-28 10:09 ` Drew Adams
2015-12-28 6:05 ` Per Starbäck
2015-12-28 10:13 ` Drew Adams
2015-12-28 9:12 ` Nikolai Weibull
2015-12-28 10:15 ` Drew Adams
2015-12-28 14:59 ` Nikolai Weibull
2015-12-28 18:39 ` Drew Adams
2015-12-29 9:06 ` Alan Mackenzie
2015-12-28 9:37 ` Paul Eggert
2015-12-28 10:16 ` Drew Adams
2015-12-29 7:05 ` Random832
2015-12-29 8:01 ` Yuri Khan
2015-12-29 14:38 ` Random832
2015-12-29 15:58 ` Eli Zaretskii
2015-12-29 17:05 ` Paul Eggert
2015-12-29 18:00 ` Drew Adams
2015-12-29 18:16 ` Eli Zaretskii
2015-12-29 19:24 ` Paul Eggert
2015-12-29 15:55 ` Eli Zaretskii
2015-12-29 17:40 ` Drew Adams
2015-12-28 16:31 ` Eli Zaretskii
2015-12-27 3:44 ` Eli Zaretskii
2015-12-27 8:12 ` Nikolai Weibull
2015-12-28 20:04 ` John Wiegley
2015-12-29 6:50 ` Richard Stallman
2015-12-29 16:55 ` John Wiegley
2015-12-29 17:30 ` Paul Eggert
2015-12-29 18:18 ` Drew Adams
2016-01-01 13:29 ` Marcin Borkowski
2016-01-01 17:48 ` John Wiegley
2016-01-01 17:50 ` John Wiegley
2016-01-02 8:14 ` Paul Eggert
2015-12-29 15:05 ` Random832
2015-12-29 16:49 ` John Wiegley
[not found] ` <<n5u7gn$6vh$1@ger.gmane.org>
2015-12-29 17:46 ` Drew Adams
[not found] <<567ECD8C.1070408@cs.ucla.edu>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=567ECD8C.1070408@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=Emacs-devel@gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.