unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Emre Sahin <i.emre.sahin@gmail.com>
To: David De La Harpe Golden <david@harpegolden.net>
Cc: 643@emacsbugs.donarmstrong.com,
	Chong Yidong <cyd@stupidchicken.com>,
	"Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: bug#643: Battery update
Date: Fri, 08 Aug 2008 00:54:20 +0300	[thread overview]
Message-ID: <87iqucebjn.fsf@leonardo.iesahin.net> (raw)
In-Reply-To: <489B44D6.4020706@harpegolden.net> (David De La Harpe Golden's message of "Thu\, 07 Aug 2008 19\:54\:14 +0100")

David De La Harpe Golden <david@harpegolden.net> writes:

> Lennart Borgman (gmail) wrote:
>> Chong Yidong wrote:
>>> Even though it's the feature freeze, I think it's necessary to ensure
>>> that battery.el works at least at a basic level.
>> 
>> Just out of curiosity: Why is it necessary that battery.el works? Is not
>> this information something that the OS normally gives the user without
>> Emacs?
>> 
>
> not if you're running emacs fullscreen I guess, can't see a tray icon
> then...
>

I'm using ratpoison WM and using Emacs in full screen. (I suggest you
to try ratpoison, stumpwm or xmonad like "tiling wm"s and find "taste
of emacs" in their screen estate management. By the way, stumpwm has
its configuration in Common Lisp, and xmonad in Haskell, if that makes
a difference for you.)

There are no icons or bars or anything around. There is nothing except
Emacs' mode line to show battery information, hence battery.el. :)

Best Regards,

Emre

-- 
I. Emre Sahin                   @ Ankara, Turkey 
Software Developer & Consultant @ http://ydyazilim.com
Ph.D. Candidate       		@ http://cs.bilkent.edu.tr
Blogger, Writer, Poet  		@ http://emresahin.net
Maybe hears the phone  		@ +90 532 261 8985
Maybe gtalk (or jabber)   	@ i.emre.sahin@gmail.com




  reply	other threads:[~2008-08-07 21:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07 16:35 Battery update Chong Yidong
2008-08-07 18:09 ` Sven Joachim
2008-08-07 18:19   ` Chong Yidong
2008-08-07 19:11     ` Sven Joachim
2008-08-07 19:28       ` Chong Yidong
2008-08-07 19:45         ` Sven Joachim
2008-08-07 20:32           ` Chong Yidong
2008-08-07 22:24             ` Emre Sahin
2008-08-08  0:10               ` Chong Yidong
2008-08-08  5:56                 ` Sven Joachim
2008-08-08  8:19                   ` Eli Zaretskii
2008-08-08 10:52                     ` Johannes Weiner
2008-08-08 13:26                 ` Emre Sahin
2008-08-08  5:50             ` Sven Joachim
2008-08-07 18:18 ` bug#643: " Lennart Borgman (gmail)
2008-08-07 18:36   ` Óscar Fuentes
2008-08-07 18:54   ` David De La Harpe Golden
2008-08-07 21:54     ` Emre Sahin [this message]
2008-08-10 10:14   ` Yoni Rabkin
2008-08-11  0:10   ` T. V. Raman
2008-08-08 17:56 ` Stefan Monnier

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=87iqucebjn.fsf@leonardo.iesahin.net \
    --to=i.emre.sahin@gmail.com \
    --cc=643@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    --cc=david@harpegolden.net \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.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).