From: Eli Zaretskii <eliz@gnu.org>
To: Joseph Turner <joseph@ushin.org>
Cc: emacs-devel@gnu.org, schwab@suse.de, adam@alphapapa.net
Subject: Re: How to get buffer byte length (not number of characters)?
Date: Fri, 23 Aug 2024 10:02:24 +0300 [thread overview]
Message-ID: <86frqvrabj.fsf@gnu.org> (raw)
In-Reply-To: <878qwnj3j0.fsf@ushin.org> (message from Joseph Turner on Thu, 22 Aug 2024 20:56:19 -0700)
> From: Joseph Turner <joseph@ushin.org>
> Cc: emacs-devel@gnu.org, schwab@suse.de, adam@alphapapa.net
> Date: Thu, 22 Aug 2024 20:56:19 -0700
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> For encoding text, should we encode with buffer-file-coding-system?
> >
> > If you are sure it will do, yes. But what if the buffer started as
> > all-ASCII and then the user or some Lisp program added some non-ASCII
> > characters before saving? Then buffer-file-coding-system is no longer
> > pertinent.
>
> I understand. Thank you!
>
> How do we encode if find-coding-systems-region returns '(undecided)?
Use buffer-file-coding-system.
If this is an interactive command, you could also use
select-safe-coding-system, which calls find-coding-systems-region
internally, and also has complex logic for finding suitable callbacks
and asking the user to select an encoding if it fails to find
something suitable. But this is not appropriate in non-interactive
code.
next prev parent reply other threads:[~2024-08-23 7:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 7:10 How to get buffer byte length (not number of characters)? Joseph Turner
2024-08-20 7:51 ` Joseph Turner
2024-08-20 11:20 ` Eli Zaretskii
2024-08-20 11:15 ` Eli Zaretskii
2024-08-21 9:20 ` Joseph Turner
2024-08-21 17:47 ` Eli Zaretskii
2024-08-21 23:52 ` Joseph Turner
2024-08-22 4:06 ` Eli Zaretskii
2024-08-22 7:24 ` Joseph Turner
2024-08-22 11:04 ` Eli Zaretskii
2024-08-22 18:29 ` Joseph Turner
2024-08-22 18:44 ` Eli Zaretskii
2024-08-22 19:32 ` tomas
2024-08-23 3:56 ` Joseph Turner
2024-08-23 7:02 ` Eli Zaretskii [this message]
2024-08-23 7:37 ` Joseph Turner
2024-08-23 12:34 ` Eli Zaretskii
2024-08-23 7:43 ` Joseph Turner
2024-08-23 12:38 ` Eli Zaretskii
2024-08-23 16:59 ` Joseph Turner
2024-08-23 17:35 ` Eli Zaretskii
2024-08-23 20:37 ` Joseph Turner
2024-08-24 6:14 ` Joseph Turner
2024-08-22 12:26 ` Adam Porter
2024-08-22 12:47 ` tomas
2024-08-23 6:28 ` Adam Porter
2024-08-22 13:50 ` Eli Zaretskii
2024-08-23 6:31 ` Adam Porter
2024-08-23 6:51 ` Eli Zaretskii
2024-08-23 7:07 ` Joseph Turner
2024-08-23 7:58 ` Joseph Turner
2024-08-22 7:09 ` Andreas Schwab
2024-08-22 7:30 ` Joseph Turner
2024-08-22 11:05 ` Eli Zaretskii
2024-08-26 6:37 ` Joseph Turner
2024-08-26 6:49 ` Joseph Turner
2024-08-26 11:22 ` Eli Zaretskii
2024-08-27 4:48 ` Joseph Turner
2024-08-26 11:20 ` Eli Zaretskii
2024-08-20 11:24 ` Andreas Schwab
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=86frqvrabj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
--cc=joseph@ushin.org \
--cc=schwab@suse.de \
/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).