all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.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: Fri, 30 Oct 2020 15:25:37 +0200	[thread overview]
Message-ID: <83v9eralri.fsf@gnu.org> (raw)
In-Reply-To: <87mu03j3cv.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri,  30 Oct 2020 13:38:24 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Lin Sun <lin.sun@zoom.us>,  44320@debbugs.gnu.org
> Date: Fri, 30 Oct 2020 13:38:24 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> I got a bug that `send-string-to-termina` maybe send part of contents to
> >> terminal, calling `fwrite` in loop to make sure all contents are written.
> >
> > Any idea why does it not write the entire string in the single call,
> > or how to reproduce this?  What is the size of the string in the case
> > where it fails to write everything?
> 
> fwrite isn't guaranteed to write the entire string in one go, is it?  So
> I'm surprised that this doesn't lead to more problems, but I guess it
> doesn't show up more in practice because one usually sends less than one
> block at a time to the terminal?

I understand the basics, I'd just would like to know the details in
this case.  fwrite could be interrupted by something, or it could
write only part of the buffer, or something else.

This is very old code, so it is surprising this only comes up now.
I'd rather we understood the issue completely before we decide how to
fix it.





  reply	other threads:[~2020-10-30 13:25 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 [this message]
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

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=83v9eralri.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44320@debbugs.gnu.org \
    --cc=larsi@gnus.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 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.