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 11:00:03 -0700	[thread overview]
Message-ID: <25242.19491.737855.32056@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <83v8thbps3.fsf@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.Eli Zaretskii writes:
 > > Cc: 55770@debbugs.gnu.org
 > > Date: Fri, 03 Jun 2022 09:39:10 -0700
 > > From:  "T.V Raman" via "Bug reports for GNU Emacs,
 > >  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
 > > 
 > > 
 > > Lookeding at this more closely,
 > > default value of battery-update-interval is 60s which might be okay for
 > > updating modeline; will having other functions here prove to be an
 > > efficiency hit?
 > > 
 > > For instance, if playing a sound on entering critical state,  one might
 > > well end up implementing some more logic to decide how often to play a sound.
 > 
 > battery-update-interval is also a defcustom, so you can make it
 > smaller if you need.

-- 

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 18:00 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 [this message]
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
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.19491.737855.32056@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).