unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Support for multiple batteries
Date: Thu, 11 Jun 2020 17:08:05 +0100	[thread overview]
Message-ID: <87tuzhy49m.fsf@tcd.ie> (raw)
In-Reply-To: <E1j7A0m-0000vA-1B@fencepost.gnu.org> (Richard Stallman's message of "Wed, 26 Feb 2020 22:38:56 -0500")

Richard Stallman <rms@gnu.org> writes:

> Has proper support for multiple batteries in battery.el
> been reimplemented yet?  I use that case, and I wrote the
> old code to handle it.

What exactly do you mean by "proper" support?

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.

The way they handle multiple batteries is by merging multiple data into
a single report.  Is this what you mean by "proper" support, or do you
envision some other way to report on multiple batteries?

My patch in https://debbugs.gnu.org/39491#55 also adds support for
multiple power sources to battery-upower, for UPower support.

It is possible that the other backends also support multiple batteries
if the single source they query is already summarising data from
multiple batteries, but I'm not familiar enough with APM, pmset, or MS
Windows to say.

-- 
Basil



  parent reply	other threads:[~2020-06-11 16:08 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 [this message]
2020-06-13  4:02   ` Richard Stallman
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=87tuzhy49m.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).