unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Dima Kogan <dima@secretsauce.net>
Cc: 49714@debbugs.gnu.org
Subject: bug#49714: 28.0.50; TRAMP burns CPU and has insufficient user reporting when using xxxx-sk SSH keys
Date: Sat, 24 Jul 2021 20:44:15 +0200	[thread overview]
Message-ID: <87czr7o8lc.fsf@gmx.de> (raw)
In-Reply-To: <87wnpfr25i.fsf@secretsauce.net> (Dima Kogan's message of "Sat, 24 Jul 2021 11:35:05 -0700")

Dima Kogan <dima@secretsauce.net> writes:

>>> There should be a loop, but emacs shouldn't be using all my CPU cycles
>>> while waiting for user interaction. Emacs can select() on the ssh
>>> process file descriptor, and sleep until the ssh process has stuff to
>>> say.
>>
>> Well, I'm on Lisp level. I just have accept-process-output, and in my
>> loop I check whether there is new output. There's no low level API to
>> let Emacs sleep for the ssh process file descriptor.
>
> It just sounds unbelievable that emacs can't do blocking reads from the
> lisp level. Let me look at (accept-process-output)

accept-process-output could block. But it blocks the whole Emacs then,
which isn't what we want.






  reply	other threads:[~2021-07-24 18:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 22:05 bug#49714: 28.0.50; TRAMP burns CPU and has insufficient user reporting when using xxxx-sk SSH keys Dima Kogan
2021-07-24 12:02 ` Michael Albinus
2021-07-24 18:15   ` Dima Kogan
2021-07-24 18:24     ` Michael Albinus
2021-07-24 18:35       ` Dima Kogan
2021-07-24 18:44         ` Michael Albinus [this message]
2021-07-24 18:52           ` Dima Kogan
2021-07-25 12:37             ` Michael Albinus
     [not found]         ` <87tukjr1lq.fsf@secretsauce.net>
     [not found]           ` <87eebnmqty.fsf@gmx.de>
     [not found]             ` <87lf5vqya5.fsf@secretsauce.net>
     [not found]               ` <87o8aqwp1v.fsf@gmx.de>
     [not found]                 ` <874kciqfuv.fsf@secretsauce.net>
     [not found]                   ` <87bl6puql6.fsf@gmx.de>
     [not found]                     ` <87h7ggpb4k.fsf@secretsauce.net>
     [not found]                       ` <87pmv4td2v.fsf@gmx.de>
     [not found]                         ` <8735s0p260.fsf@secretsauce.net>
     [not found]                           ` <87lf5st3b2.fsf@gmx.de>
     [not found]                             ` <87tukfobxa.fsf@secretsauce.net>
     [not found]                               ` <878s1rttfc.fsf@gmx.de>
     [not found]                                 ` <87czr3o497.fsf@secretsauce.net>
     [not found]                                   ` <874kcftol2.fsf@gmx.de>
     [not found]                                     ` <87a6m7nzv0.fsf@secretsauce.net>
2021-07-28  7:18                                       ` Michael Albinus
2021-07-28 19:58                                         ` Dima Kogan
2021-07-28 20:07                                           ` Michael Albinus
2021-07-28 20:12                                             ` Dima Kogan
2021-08-03 20:16                                           ` Michael Albinus
2021-08-08  5:41                                             ` Dima Kogan
2021-08-08 14:21                                               ` Michael Albinus
2021-08-13 19:18                                                 ` Dima Kogan
2021-08-16 19:50                                                   ` Michael Albinus
     [not found]                                                     ` <87eeat414c.fsf@gmx.de>
     [not found]                                                       ` <87lf4x5ork.fsf@secretsauce.net>
2021-08-22 13:06                                                         ` Michael Albinus
2021-09-09 13:58                                                           ` Michael Albinus
2021-09-09 18:00                                                           ` Dima Kogan
2021-07-24 18:30     ` Michael Albinus

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=87czr7o8lc.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=49714@debbugs.gnu.org \
    --cc=dima@secretsauce.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).