From: pjb@informatimago.com (Pascal J. Bourguignon)
To: help-gnu-emacs@gnu.org
Subject: Re: Why would emacs be running on an idle system?
Date: Wed, 27 May 2009 17:47:50 +0200 [thread overview]
Message-ID: <7c1vqa7djt.fsf@pbourguignon.anevia.com> (raw)
In-Reply-To: mailman.7921.1243438512.31690.help-gnu-emacs@gnu.org
Peter Dyballa <Peter_Dyballa@Web.DE> writes:
> Am 27.05.2009 um 15:44 schrieb D W:
>
>> Any ideas why I would see emacs22 in there or where I should look
>> to find
>> out what might have triggered this?
>
>
> Do you have pstree to see the tree of processes involved in creating
> that GNU Emacs 22 process?
or: ps fax with procps.
--
__Pascal Bourguignon__
next prev parent reply other threads:[~2009-05-27 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 13:44 Why would emacs be running on an idle system? D W
2009-05-27 15:34 ` Peter Dyballa
[not found] ` <mailman.7921.1243438512.31690.help-gnu-emacs@gnu.org>
2009-05-27 15:47 ` Pascal J. Bourguignon [this message]
[not found] <mailman.7913.1243434453.31690.help-gnu-emacs@gnu.org>
2009-05-28 1:06 ` Barry Margolin
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=7c1vqa7djt.fsf@pbourguignon.anevia.com \
--to=pjb@informatimago.com \
--cc=help-gnu-emacs@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.
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).