From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [Warning and iso 8859-1 default?]
Date: Sat, 20 Jul 2019 20:40:33 +0300 [thread overview]
Message-ID: <83ef2ksiy6.fsf@gnu.org> (raw)
In-Reply-To: <jwv7e8cwquf.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 20 Jul 2019 13:37:04 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: emacs-devel@gnu.org
> Date: Sat, 20 Jul 2019 13:37:04 -0400
>
> >> I see, then I guess the only place where we could detect the problem is
> >> in `save-buffer`.
> > What problem is that?
>
> The problem of saving the file in an encoding that will be mis-detected
> when read back using that same Emacs.
That would make saving using any single-byte encoding "a problem",
right?
Rather than calling this a problem we should perhaps work on improving
detection of single-byte encodings.
next prev parent reply other threads:[~2019-07-20 17:40 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 11:31 problem with old hebrew latex files in iso 8859-8 coding Uwe Brauer
2019-07-18 11:48 ` Eli Zaretskii
2019-07-18 12:06 ` Uwe Brauer
2019-07-18 12:11 ` Lars Ingebrigtsen
2019-07-18 12:17 ` Uwe Brauer
2019-07-18 12:35 ` Eli Zaretskii
2019-07-18 13:03 ` Uwe Brauer
2019-07-18 13:56 ` Eli Zaretskii
2019-07-18 13:14 ` Uwe Brauer
2019-07-18 13:27 ` Andreas Schwab
2019-07-18 13:52 ` Uwe Brauer
2019-07-18 13:54 ` Uwe Brauer
2019-07-18 14:12 ` Eli Zaretskii
2019-07-18 14:00 ` Eli Zaretskii
2019-07-20 13:39 ` [Warning and iso 8859-1 default?] (was: problem with old hebrew latex files in iso 8859-8 coding) Uwe Brauer
2019-07-20 13:53 ` Eli Zaretskii
2019-07-20 13:57 ` [Warning and iso 8859-1 default?] Uwe Brauer
2019-07-20 14:09 ` Eli Zaretskii
2019-07-20 14:16 ` Uwe Brauer
2019-07-20 15:51 ` Eli Zaretskii
2019-07-20 16:17 ` Uwe Brauer
2019-07-20 16:46 ` Eli Zaretskii
2019-07-20 17:17 ` Eli Zaretskii
2019-07-20 16:48 ` Eli Zaretskii
2019-07-20 17:29 ` Stefan Monnier
2019-07-20 18:08 ` Uwe Brauer
2019-07-20 14:20 ` Stefan Monnier
2019-07-20 16:20 ` Uwe Brauer
2019-07-20 17:27 ` Stefan Monnier
2019-07-20 17:33 ` Eli Zaretskii
2019-07-20 17:37 ` Stefan Monnier
2019-07-20 17:40 ` Eli Zaretskii [this message]
2019-07-21 13:24 ` Stefan Monnier
2019-07-18 12:15 ` problem with old hebrew latex files in iso 8859-8 coding Eli Zaretskii
2019-07-18 12:19 ` Uwe Brauer
2019-07-18 12:37 ` Eli Zaretskii
2019-07-18 12:55 ` Uwe Brauer
2019-07-18 13:55 ` Eli Zaretskii
2019-07-18 14:04 ` Uwe Brauer
2019-07-18 14:14 ` Eli Zaretskii
2019-07-18 14:26 ` Uwe Brauer
2019-07-18 14:31 ` Eli Zaretskii
2019-07-18 13:05 ` Andreas Schwab
2019-07-18 13:57 ` Eli Zaretskii
2019-07-18 12:29 ` Andreas Schwab
2019-07-18 15:02 ` Stefan Monnier
2019-07-18 15:24 ` Uwe Brauer
2019-07-18 16:06 ` Eli Zaretskii
2019-07-18 17:10 ` Eli Zaretskii
2019-08-21 7:40 ` Arne Jørgensen
2019-08-21 7:43 ` Uwe Brauer
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=83ef2ksiy6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).