From: "shirish शिरीष" <shirishag75@gmail.com>
To: Daniel Shahaf <danielsh@apache.org>
Cc: zsh-workers <zsh-workers@zsh.org>, Adam <adam@spiers.net>
Subject: Re: [FEATURE REQUEST] Adding battery power to bigfade prompt
Date: Wed, 28 Dec 2016 02:17:10 +0530 [thread overview]
Message-ID: <CADdDZRm5jMs5h6Yxgrxbe96cuRr4EV6o5As5LFmwjRMk24cH8g@mail.gmail.com> (raw)
In-Reply-To: <20161227130925.GB4796@fujitsu.shahaf.local2>
at bottom :-
On 27/12/2016, Daniel Shahaf <danielsh@apache.org> wrote:
> shirish शिरीष wrote on Tue, Dec 27, 2016 at 01:51:28 +0530:
>> It would be nice if either bigfade or some other prompt adds battery
>> power to its prompt, please.
>
> How would that be done portably? The tool to use is ioreg(8) on OS X,
> apm(8) on FreeBSD, and acpi(8) on Linux; and I'm not sure whether
> acpi(8) exists in all Linuxes.
>
> Cheers,
>
> Daniel
> (I have battery info in my tmux status line)
>
Agreed. In that case could we have some sort of generic battery
modules that we could enable on our platform.
What could be done is have four optional scripts added to zsh
documenting which script works with which platform/technology etc. and
then the user would just enable it . The only thing that the user
would have to then think on how to have it on the extreme right or
left (hinking about users who write from right to left rather than the
conventional left to right.)
@ Daniel - if there is a specific module/script which could be used to
easily do this, please share it either on-list or off-list OR if you
want, can also re-ask the same thing in zsh-users@zsh.org if you think
it's a better domain for this type of thing.
Look forward to hearing from you.
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
next prev parent reply other threads:[~2016-12-27 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 20:21 shirish शिरीष
2016-12-27 13:09 ` Daniel Shahaf
2016-12-27 20:47 ` shirish शिरीष [this message]
2016-12-29 10:19 ` Vincent Lefevre
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADdDZRm5jMs5h6Yxgrxbe96cuRr4EV6o5As5LFmwjRMk24cH8g@mail.gmail.com \
--to=shirishag75@gmail.com \
--cc=adam@spiers.net \
--cc=danielsh@apache.org \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).