unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Peter Ludemann <peter.ludemann@gmail.com>
Cc: 38644@debbugs.gnu.org
Subject: bug#38644: 26.3; emacs uses 100% CPU with auto-revert-mode
Date: Tue, 17 Dec 2019 20:30:26 +0100	[thread overview]
Message-ID: <87woauyckt.fsf@gmx.de> (raw)
In-Reply-To: <CAHjfyZ2=3WnSkv4QfJOW7XJ3tOfw1_nM0deVtUkG2cfZKs2wYA@mail.gmail.com> (Peter Ludemann's message of "Tue, 17 Dec 2019 10:27:36 -0800")

Peter Ludemann <peter.ludemann@gmail.com> writes:

> But first: I see different versions of this discussion at
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2018-10/msg00997.html
> and
> http://emacs.1067599.n8.nabble.com/bug-33194-26-1-Auto-revert-mode-causes-emacs-to-use-100-cpu-whenever-a-file-is-being-written-to-in-ty-tt468378.html#none
> (the former has a 2nd thread, which mentions the patch in Emacs 27) .
> .. what is the correct way to interact with emacs bugs?

Just reply to this message, and keep 38644@debbugs.gnu.org in Cc. Whether
you keep me (or anybody else) in the list of recipients depends on your taste.

Best regards, Michael.





  reply	other threads:[~2019-12-17 19:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17  1:23 bug#38644: 26.3; emacs uses 100% CPU with auto-revert-mode Peter Ludemann
2019-12-17 13:59 ` Michael Albinus
2019-12-17 16:17 ` Eli Zaretskii
2019-12-17 18:27   ` Peter Ludemann
2019-12-17 19:30     ` Michael Albinus [this message]
2019-12-28 21:12       ` Peter Ludemann
2019-12-29 15:23         ` Michael Albinus
2020-01-04 18:50           ` Peter Ludemann
2020-01-05  9:28             ` Michael Albinus
2020-01-05 13:04 ` Mattias Engdegård
2020-01-05 19:31   ` Peter Ludemann
2020-01-05 19:57     ` Mattias Engdegård
2020-01-07  0:01       ` Peter Ludemann
2020-01-07  0:34         ` Peter Ludemann

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=87woauyckt.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=38644@debbugs.gnu.org \
    --cc=peter.ludemann@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).