unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44320@debbugs.gnu.org, lin.sun@zoom.us
Subject: bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents
Date: Mon, 02 Nov 2020 17:30:44 +0100	[thread overview]
Message-ID: <87mtzz4t6z.fsf@gnus.org> (raw)
In-Reply-To: <83zh3zd9ou.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 02 Nov 2020 18:07:13 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> What is the significance of 4K bytes in this case?  Is 'fwrite'
> documented not to write more than that?  I couldn't find such
> documentation.

writes that are less than a system block size are unlikely to be chopped
into parts.

> Anyway, if we need to fix calls to 'fwrite', we should provide
> something similar to emacs_write, and use it everywhere we use
> 'fwrite' now.

I can't see anything in the fwrite man page that guarantees that it'll
write all that we tell it to write:

RETURN VALUE
       On success, fread() and fwrite() return the number of items read or writ‐
       ten.  This number equals the number of bytes transferred only  when  size
       is  1.  If an error occurs, or the end of the file is reached, the return
       value is a short item count (or zero).


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2020-11-02 16:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 23:01 bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents Lin Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-30  0:36 ` Lin Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-30  8:06 ` Eli Zaretskii
2020-10-30 12:38   ` Lars Ingebrigtsen
2020-10-30 13:25     ` Eli Zaretskii
2020-11-02  2:58       ` LinSun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-02  3:11         ` LinSun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-02 15:31           ` Eli Zaretskii
2020-11-02 15:49             ` Andreas Schwab
2020-11-02 16:14               ` Eli Zaretskii
2020-11-02 16:41                 ` Andreas Schwab
2020-11-02 17:10                   ` Eli Zaretskii
2020-11-02 17:36                     ` Andreas Schwab
2020-11-02 17:59                       ` Eli Zaretskii
2020-11-02 18:02                         ` Andreas Schwab
2020-11-02 18:12                           ` Eli Zaretskii
2020-11-02 18:22                             ` Andreas Schwab
2020-11-02 18:35                               ` Eli Zaretskii
2020-11-02 18:58                                 ` Andreas Schwab
2020-11-02 19:31                                   ` Eli Zaretskii
2020-11-02 20:26                                     ` Andreas Schwab
     [not found]                                       ` <4BD75783-F561-4DB8-A733-13A3D924C8C1@hxcore.ol>
2020-11-03 15:29                                         ` Eli Zaretskii
2020-11-05  0:14                                           ` LinSun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-07  9:28                                             ` Eli Zaretskii
2020-11-09  2:27                                               ` LinSun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-05 15:59                                       ` Eli Zaretskii
2020-11-05 16:07                                         ` Andreas Schwab
2020-11-02 15:22         ` Lars Ingebrigtsen
2020-11-02 16:07           ` Eli Zaretskii
2020-11-02 16:30             ` Lars Ingebrigtsen [this message]

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=87mtzz4t6z.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=44320@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=lin.sun@zoom.us \
    /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).