From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: schwab@linux-m68k.org, 24759@debbugs.gnu.org
Subject: bug#24759: 25.1.50; electric-quote-mode
Date: Sun, 23 Oct 2016 10:00:28 +0300 [thread overview]
Message-ID: <8337jnpn1v.fsf@gnu.org> (raw)
In-Reply-To: <48240d67-ab6c-e7ec-9f77-bddbe1c07b83@cs.ucla.edu> (message from Paul Eggert on Sat, 22 Oct 2016 20:55:25 -0700)
> Cc: Eli Zaretskii <eliz@gnu.org>, 24759@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sat, 22 Oct 2016 20:55:25 -0700
>
> As I understand it, this subthread is about what Emacs should do in a unibyte
> locale that isn't the C locale. It's not clear to me why these locales (which
> are no longer that important) should be treated differently from a unibyte C
> locale for this sort of situation.
Because a C locale basically means you have no non-trivial default
encoding. IOW, your default is 'undecided'. In such cases, we prefer
UTF-8 automatically if it can do the job (and it usually can), since
the user doesn't have any specific preferences.
So I think we should indeed remove the electric--insertable-p test in
electric-quote-mode, on the emacs-25 branch.
A related change (which IMO should be done on master) is to make UTF-8
be the first encoding in the sorted list of encodings Emacs offers
when the defaults cannot cope with some characters in a buffer about
to be saved or sent to a subprocess. But this related change is not a
prerequisite for removing the electric--insertable-p test, as it is a
general improvement in the Emacs guesswork, not something specific to
the issue at hand in this bug report.
next prev parent reply other threads:[~2016-10-23 7:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 19:38 bug#24759: 25.1.50; electric-quote-mode Dani Moncayo
2016-10-21 19:58 ` Eli Zaretskii
2016-10-21 20:26 ` Dani Moncayo
2016-10-21 21:01 ` Paul Eggert
2016-10-21 21:04 ` Paul Eggert
2016-10-22 6:49 ` Eli Zaretskii
2016-10-22 7:47 ` Eli Zaretskii
2016-10-22 8:16 ` Dani Moncayo
2016-10-22 9:10 ` Eli Zaretskii
2016-10-22 10:36 ` Dani Moncayo
2016-10-22 18:47 ` Paul Eggert
2016-10-22 19:04 ` Eli Zaretskii
2016-10-22 19:34 ` Eli Zaretskii
2016-10-23 4:10 ` Paul Eggert
2016-10-23 7:13 ` Eli Zaretskii
2016-10-23 8:24 ` Paul Eggert
2016-10-23 8:51 ` Eli Zaretskii
2016-10-22 19:20 ` Andreas Schwab
2016-10-23 3:55 ` Paul Eggert
2016-10-23 7:00 ` Eli Zaretskii [this message]
2016-10-23 8:15 ` Paul Eggert
2016-10-23 8:55 ` Eli Zaretskii
2016-10-23 9:15 ` Dani Moncayo
2016-10-23 9:28 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8337jnpn1v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24759@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=schwab@linux-m68k.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).