unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: emacs-devel@gnu.org
Subject: Re: Support for multiple batteries
Date: Sat, 13 Jun 2020 00:02:41 -0400	[thread overview]
Message-ID: <E1jjxNR-0004Sy-GT@fencepost.gnu.org> (raw)
In-Reply-To: <87tuzhy49m.fsf@tcd.ie> (contovob@tcd.ie)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > AFAICT only two battery status backends currently support multiple
  > sources of information: battery-linux-sysfs and battery-linux-proc-acpi,
  > for Linux sysfs and ACPI support, respectively.

Could you clear up for me what "currently" means in this context?  I
don't know what code was changed in January or so -- only that the
change led to incorrect reports, on a Thinkpad T400s with two
batteries inserted.

  > The way they handle multiple batteries is by merging multiple data into
  > a single report.

I am not sure what that means, concretely.

                      Is this what you mean by "proper" support,

Proper support means at least giving a good estimate for how long
before the machine runs out of energy, and a good estimate of the
actual fraction of maximum charge the batteries can hold.  The code
from last October could do that.

When I type M-x battery in the version as of October 2,
it displays something like

  Power BAT, battery Discharging (98.1% load, remaining time 4:04)

where the numbers depend on the energy capacity of each battery and
the current charge of each battery, as well as the actual current or
power.

That is what I think is crucial for M-x battery.

-- 
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2020-06-13  4:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27  3:38 Support for multiple batteries Richard Stallman
2020-02-28  7:43 ` Eli Zaretskii
2020-02-28 10:21   ` lg.zevlg
2020-02-28 12:57     ` Eli Zaretskii
2020-03-01  3:46     ` Richard Stallman
2020-03-03  3:37       ` Richard Stallman
2020-06-11 16:08 ` Basil L. Contovounesios
2020-06-13  4:02   ` Richard Stallman [this message]
2020-06-13 11:48     ` Basil L. Contovounesios
2020-06-14 13:40       ` Richard Stallman
2020-06-18 15:59         ` Basil L. Contovounesios
2020-06-13 19:42     ` Drew Adams
2020-06-14 13:43       ` Richard Stallman

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=E1jjxNR-0004Sy-GT@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=contovob@tcd.ie \
    --cc=emacs-devel@gnu.org \
    /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).