From: Miles Bader <miles@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: implement Solaris support for system-process-attributes and list-system-processes
Date: Fri, 19 Dec 2008 17:48:59 +0900 [thread overview]
Message-ID: <buo4p10zh1g.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <200812190745.mBJ7jWVe015085@mothra.ics.uci.edu> (Dan Nicolaescu's message of "Thu, 18 Dec 2008 23:45:32 -0800 (PST)")
Dan Nicolaescu <dann@ics.uci.edu> writes:
> How does this sound:
> - move the procfs_list_system_processes and procfs_system_process_attributes to sysdep.c
> - remove the procfs_ prefix
> - add the proper #defines (HAVE_PROCFS can probably be used by a few OSes)
> - the default implementations just return Qnil
> - make Fsystem_process_attributes and Flist_system_processes just call
> list_system_processes and system_process_attributes
> - rename the w32 versions to system_process_attributes and list_system_processes
> - remove the PROCATTR and LISTPROC macros
> ?
... and while you're at it, rename Fsystem_process_attributes to
"Fprocess_attributes" and make it also accept emacs process objects as
an argument, ala signal-process.
-Miles
--
"Suppose He doesn't give a shit? Suppose there is a God but He
just doesn't give a shit?" [George Carlin]
next prev parent reply other threads:[~2008-12-19 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 9:16 implement Solaris support for system-process-attributes and list-system-processes Dan Nicolaescu
2008-12-18 20:22 ` Eli Zaretskii
2008-12-19 7:45 ` Dan Nicolaescu
2008-12-19 8:35 ` Eli Zaretskii
2008-12-19 19:51 ` Dan Nicolaescu
2008-12-20 12:10 ` Eli Zaretskii
2008-12-19 8:48 ` Miles Bader [this message]
2008-12-19 19:51 ` Dan Nicolaescu
2008-12-20 3:40 ` Miles Bader
2008-12-20 3:50 ` Dan Nicolaescu
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=buo4p10zh1g.fsf@dhapc248.dev.necel.com \
--to=miles@gnu.org \
--cc=dann@ics.uci.edu \
--cc=eliz@gnu.org \
--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).