unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: jsynacek@redhat.com, 41640@debbugs.gnu.org
Subject: bug#41640: 28.0.50; shell startup very slow when init file is used
Date: Fri, 05 Jun 2020 14:51:47 +0300	[thread overview]
Message-ID: <838sh1bui4.fsf@gnu.org> (raw)
In-Reply-To: <87mu5h3ofg.fsf@gmail.com> (message from Pip Cet on Fri, 05 Jun 2020 08:30:11 +0000)

> From: Pip Cet <pipcet@gmail.com>
> Cc: jsynacek@redhat.com,  41640@debbugs.gnu.org
> Date: Fri, 05 Jun 2020 08:30:11 +0000
> 
> > The code and the comments don't say why we used sleep-for, which your
> > patch removes.  Did you succeed in understanding what was that for,
> > and if so, can you describe that reason and the rationale for removing
> > the sleep?
> 
> I'll try. (According to git, this code has been here since 1990).

Yes.  But Jim Blandy, who clearly had some problem he tried to solve,
didn't describe the problem itself, just the solution.

> The code inserted the file contents of the startfile at (point-max)
> in the comint *output* buffer. I believe the concern was that
> insert-file-contents would accept process output, corrupting the
> start file, and it's possible this may happen, at least with tramp
> handlers. Therefore, to avoid the process output being sent back to
> the process, I think the sleep-for was added as a way to ensure the
> program was done displaying the prompt.

So you are saying that the wait is there to allow us to receive the
shell's prompt, so that the contents of start file don't mix with that
prompt?  If that is the reason, then I think your changes are indeed
TRT.

Thanks.





  reply	other threads:[~2020-06-05 11:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01  8:52 bug#41640: 28.0.50; shell startup very slow when init file is used Jan Synacek
2020-06-04 21:21 ` Pip Cet
2020-06-05  7:50   ` Eli Zaretskii
2020-06-05  8:30     ` Pip Cet
2020-06-05 11:51       ` Eli Zaretskii [this message]
2020-06-05 12:13         ` Pip Cet
2020-09-27 13:10           ` Lars Ingebrigtsen
2020-06-05  9:07     ` Jan Synacek

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=838sh1bui4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=41640@debbugs.gnu.org \
    --cc=jsynacek@redhat.com \
    --cc=pipcet@gmail.com \
    /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).