From: Boruch Baum <boruch_baum@gmx.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 40771@debbugs.gnu.org
Subject: bug#40771: 26.1: javascript-mode timers persist after closing mode buffers
Date: Tue, 28 Apr 2020 23:58:23 -0400 [thread overview]
Message-ID: <20200429035823.fv2ajirsvlhdogck@E15-2016.optimum.net> (raw)
In-Reply-To: <851ro99eu2.fsf@gmail.com>
On 2020-04-27 10:35, Noam Postavsky wrote:
> Boruch Baum <boruch_baum@gmx.com> writes:
> > * 0.50 t jit-lock-context-fontify
>
> I don't think this one is javascript-related.
Oops. You're quite right on that one.
> > * 30.00 t js-gc
> It's a global timer which isn't connected to any particular buffer. I'm
> not sure why you think the timer should be killed.
It's associated with file js.el "Major mode for editing JavaScript", so
if no buffer is using that major mode, or more charitably if no buffer
is editing javascript, then the timer is cruft.
> Do you see any problems coming from the existence of this timer?
I'm not sure. The immediate reason I bothered to perform M-x list-timers
was trouble I had killing the scrolling ticker of newsticker.el. The
reason I killed the two timers was to see if doing so would stop my
emacsclient process from intermittently freezing. I've been having a
recurring problem with that, on average once every few weeks: the server
process remains functional, so I don't lose any work or data, but I need
to kill the emacsclient process and re-connect to the server.
In any event, the metric shouldn't be whether anyone "sees any problems
coming from its existence", the metric should be whether its continued
existence is good software engineering practice. Likewise for Dmitry
Gutov's suggestion to remove code associated with MozRepl.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
prev parent reply other threads:[~2020-04-29 3:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 15:43 bug#40771: 26.1: javascript-mode timers persist after closing mode buffers Boruch Baum
2020-04-27 14:35 ` Noam Postavsky
2020-04-27 14:52 ` Dmitry Gutov
2020-04-29 4:02 ` Boruch Baum
2020-04-29 4:10 ` Dmitry Gutov
2021-09-18 14:37 ` Lars Ingebrigtsen
2021-09-18 20:43 ` Dmitry Gutov
2021-10-04 9:56 ` Lars Ingebrigtsen
2020-04-29 3:58 ` Boruch Baum [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=20200429035823.fv2ajirsvlhdogck@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=40771@debbugs.gnu.org \
--cc=npostavs@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).