From: Qiantan Hong <qhong@mit.edu>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Question: estimating size of a buffer when written to file?
Date: Wed, 8 Dec 2021 15:55:42 +0000 [thread overview]
Message-ID: <5F5ECF4B-77A1-4C3A-A665-54207AC6A1BF@mit.edu> (raw)
In-Reply-To: <87a6hbw0ts.fsf@gmx.net>
> Is (string-bytes (buffer-string)) not reliable?
>
> Steve Berman
I’m not very familiar with different kinds of encoding,
but would some coding system result in final
writes longer than internal string-bytes?
Best,
Qiantan
next prev parent reply other threads:[~2021-12-08 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 15:33 Question: estimating size of a buffer when written to file? Qiantan Hong
2021-12-08 15:52 ` Stephen Berman
2021-12-08 15:55 ` Qiantan Hong [this message]
2021-12-08 16:01 ` Stephen Berman
2021-12-08 16:29 ` Daniel Martín
2021-12-08 17:03 ` Stefan Monnier
2021-12-08 17:09 ` Qiantan Hong
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=5F5ECF4B-77A1-4C3A-A665-54207AC6A1BF@mit.edu \
--to=qhong@mit.edu \
--cc=emacs-devel@gnu.org \
--cc=stephen.berman@gmx.net \
/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).