unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24759@debbugs.gnu.org
Subject: bug#24759: 25.1.50; electric-quote-mode
Date: Sun, 23 Oct 2016 01:24:15 -0700	[thread overview]
Message-ID: <2ee8a0d1-46b8-3b44-3721-806538daca82@cs.ucla.edu> (raw)
In-Reply-To: <831sz7pmgf.fsf@gnu.org>

Eli Zaretskii wrote:

>> UTF-8 should be the most-preferred multibyte encoding nowadays, unless there is
>> a reasonable indication that the user prefers something else.
>
> What kind of indication do you have in mind?

A locale that uses some non-UTF-8 multibyte encoding.

>> In a unibyte European locale, UTF-8 should be the first-listed
>> multibyte encoding by default.
>
> Why not list it the first always?

I wouldn't object. People who prefer non-UTF-8 multibyte locales might not like 
it (I'm not such a person so I can't say).

> If the single prompt we now issue already annoys
> you, it hardly makes sense to do the same multiple times.

It's not merely the prompt that annoys me. It's that the prompt can occur long 
after the problem it diagnoses.

We could suppress the prompt in later occurrences if the user doesn't want to 
see it again.

>> It's a bit like spelling checking.
>
> It's not.  A mis-spelled buffer can be saved, but we cannot save a
> buffer without knowing how to encode it.

A bit like, not exactly like. The point is that users often find it more 
convenient to see problems right away. For example, although an 
improperly-parenthesized Lisp buffer can be saved, it's still nice to have 
parenthesis-matching enabled as I type, so that I can see and fix parenthesis 
problems while they're still fresh in my mind.





  reply	other threads:[~2016-10-23  8:24 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 [this message]
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
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=2ee8a0d1-46b8-3b44-3721-806538daca82@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=24759@debbugs.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 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).