unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "T.V Raman" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: eliz@gnu.org
Cc: larsi@gnus.org, 55770@debbugs.gnu.org, raman@google.com
Subject: bug#55770: 29.0.50; Feature Request: Hook When battery transitions to low or critical
Date: Fri, 3 Jun 2022 13:09:11 -0700	[thread overview]
Message-ID: <25242.27239.180264.658796@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <83tu91bnez.fsf@gnu.org>

we're not communicating.

I did not ask to  reduce the 60s -- rather I was saying that if we
allow the user to configure additional functions to run on each
update, and if that user doesn't realize that it will run every
minute, it might put too much load on the system.Eli Zaretskii writes:
 > > From: "T.V Raman" <raman@google.com>
 > > Date: Fri, 3 Jun 2022 11:00:03 -0700
 > > Cc: raman@google.com,
 > >     larsi@gnus.org,
 > >     55770@debbugs.gnu.org
 > > 
 > > I understand and I can set mine appropriately --- I was just pointing
 > > out that a low value for the update interval when combined with an
 > > update function that does some computes could prove a bad combination.
 > 
 > The default value is for when the status is just displayed.  I don't
 > think I see a reason to make the default shorter, because it will just
 > cause more drain on the battery for no good reason.

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

--

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮





  reply	other threads:[~2022-06-03 20:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 16:32 bug#55770: 29.0.50; Feature Request: Hook When battery transitions to low or critical T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-03  3:57 ` Lars Ingebrigtsen
2022-06-03 14:06   ` T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-03 16:39   ` T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-03 17:49     ` Eli Zaretskii
2022-06-03 18:00       ` T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-03 18:40         ` Eli Zaretskii
2022-06-03 20:09           ` T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-04  2:01             ` Phil Sainty

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=25242.27239.180264.658796@retriever.mtv.corp.google.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=55770@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=raman@google.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).