From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60872@debbugs.gnu.org, jonas@bernoul.li, emacs18@gmail.com
Subject: bug#60872: 29.0.60; emacsql broken after Jan 12 change
Date: Tue, 17 Jan 2023 15:42:06 +0100 [thread overview]
Message-ID: <87a62hcjep.fsf@gmail.com> (raw)
In-Reply-To: <83r0vt2rgt.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 17 Jan 2023 15:58:10 +0200")
>>>>> On Tue, 17 Jan 2023 15:58:10 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Is it enough of an error for us to silently replace `utf-8-auto' with
>> `utf-8' when itʼs specified for `coding-system-for-write'?
Eli> That's what the bug I fixed effectively did. But no, I don't think
Eli> this is something we can do, let alone silently. It could be that
Eli> some extremely rare/obscure, but nevertheless legitimate use case does
Eli> really want to produce BOM on encoding.
Right. Iʼd suggest a doc change, but thereʼs no documentation for
`utf-8-auto' anyway, and perhaps we should avoid drawing attention to
it :-)
>>
>> Either that or use `make-process' directly and pass `:coding'
Eli> No, that will suffer from the same problem:
Yep
Robert
--
next prev parent reply other threads:[~2023-01-17 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 4:50 bug#60872: 29.0.60; emacsql broken after Jan 12 change Richard Kim
2023-01-17 10:02 ` Robert Pluim
2023-01-17 12:45 ` Eli Zaretskii
2023-01-17 13:10 ` Robert Pluim
2023-01-17 13:38 ` Robert Pluim
2023-01-17 13:58 ` Eli Zaretskii
2023-01-17 14:42 ` Robert Pluim [this message]
2023-01-17 14:54 ` Eli Zaretskii
[not found] ` <878ri13xt1.fsf@bernoul.li>
2023-01-17 17:35 ` Eli Zaretskii
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=87a62hcjep.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=60872@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacs18@gmail.com \
--cc=jonas@bernoul.li \
/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.