From: David Kastrup <dak@gnu.org>
Cc: Lute.Kamstra.lists@xs4all.nl, emacs-devel@gnu.org
Subject: Re: Darwin support for lisp/battery.el.
Date: Mon, 04 Jul 2005 17:30:28 +0200 [thread overview]
Message-ID: <8564vq7fmz.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1DpSIK-0001W9-6W@fencepost.gnu.org> (Richard M. Stallman's message of "Mon, 04 Jul 2005 10:51:36 -0400")
"Richard M. Stallman" <rms@gnu.org> writes:
> But the communication is just with the kernel, via the proc file
> system.
>
> If this comment should talk about the kernels, that is ok. Just as
> long as it does so in a clear and unambiguous way, that reinforces
> the distinction between the kernels and the larger systems.
Well, looks like with Linux, the communication is just with the
kernel, but with MacOSX/Darwin, the communication is with a command
line utility.
Sometimes accuracy is an annoying goal.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-07-04 15:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 12:21 Darwin support for lisp/battery.el Lute Kamstra
2005-07-02 13:49 ` David Kastrup
2005-07-02 14:33 ` Lute Kamstra
2005-07-02 15:16 ` David Kastrup
2005-07-03 20:42 ` Richard M. Stallman
2005-07-03 21:28 ` David Kastrup
2005-07-03 22:34 ` Lute Kamstra
2005-07-03 22:46 ` David Kastrup
2005-07-04 2:41 ` Ken Raeburn
2005-07-04 7:39 ` Lute Kamstra
2005-07-04 8:28 ` Arne Jørgensen
2005-07-04 9:44 ` Lute Kamstra
[not found] ` <87pstysxke.fsf@seamus.arnested.dk>
2005-07-04 10:43 ` Lute Kamstra
2005-07-04 9:31 ` Ken Raeburn
2005-07-04 9:40 ` Ken Raeburn
2005-07-06 11:42 ` Lute Kamstra
2005-07-06 13:05 ` Sean O'Rourke
2005-07-09 10:13 ` Lute Kamstra
2005-07-04 14:51 ` Richard M. Stallman
2005-07-04 15:30 ` David Kastrup [this message]
2005-07-05 16:12 ` Richard M. Stallman
2005-07-05 20:27 ` Aidan Kehoe
2005-07-03 22:32 ` Lute Kamstra
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=8564vq7fmz.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=Lute.Kamstra.lists@xs4all.nl \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.