From: David Kastrup <dak@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Alan Mackenzie <acm@muc.de>, Emacs Development <Emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master 9ffb6ce 5/5: Quoting fixes in lisp/internationa
Date: Fri, 04 Sep 2015 20:07:46 +0200 [thread overview]
Message-ID: <87k2s6t5vx.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <55E9D9BB.90905@cs.ucla.edu> (Paul Eggert's message of "Fri, 4 Sep 2015 10:49:47 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> On 09/04/2015 09:23 AM, Alan Mackenzie wrote:
>>
>>> Please try adding (setq text-quoting-style 'grave) there.
>> It works.
>
> Thanks for checking.
>
>> I'd prefer to stick to the `text-quoting-style'
>
> Yes, and the intent of the current master is to do both: i.e., if you
> have (setq text-quoting-style 'grave) in your .emacs, then both (1)
> unescaped curved quotes are transliterated to ASCII characters in help
> buffers and strings, and (2) all curved quotes are displayed as
> shadowed ASCII characters.
Can we stop making assumptions about the user? Whether one does not
want to have Emacs' own diagnostics exhibiting ‘...’ and whether the
display/font/whatever warrants specific marking for third-party texts
containing such characters are entirely separate topics and should be
controlled by separate options.
So what if it's not the display that is deficient but the user? Emacs
should not try reconfiguring the user for peaceful cooperation rather
than the other way round since that would be far too frustrating for
Emacs in the long run.
--
David Kastrup
next prev parent reply other threads:[~2015-09-04 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 14:51 [Emacs-diffs] master 9ffb6ce 5/5: Quoting fixes in lisp/internationa Paul Eggert
2015-09-04 16:23 ` Alan Mackenzie
2015-09-04 17:49 ` Paul Eggert
2015-09-04 18:07 ` David Kastrup [this message]
2015-09-04 18:35 ` Paul Eggert
2015-09-04 18:53 ` David Kastrup
2015-09-04 18:53 ` Alan Mackenzie
2015-09-05 18:40 ` Paul Eggert
2015-09-09 9:38 ` Paul Eggert
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=87k2s6t5vx.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=acm@muc.de \
--cc=eggert@cs.ucla.edu \
/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.