From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Roland Winkler" Newsgroups: gmane.emacs.devel Subject: Re: proced.el -- operate on processes like dired Date: Sun, 11 May 2008 06:54:56 +0200 Message-ID: <18470.31776.935364.833363@tfkp07.physik.uni-erlangen.de> References: <18409.33604.699654.7860@tfkp07.physik.uni-erlangen.de> <7dbe73ed0803251809u71557525w7d8253bf5d787c7d@mail.gmail.com> <87r6dsq9mi.fsf@jurta.org> <18421.33333.742725.806352@tfkp07.physik.uni-erlangen.de> <877ie1k9id.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1210481717 28043 80.91.229.12 (11 May 2008 04:55:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 11 May 2008 04:55:17 +0000 (UTC) Cc: emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 11 06:55:52 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Jv3bE-0000mP-9T for ged-emacs-devel@m.gmane.org; Sun, 11 May 2008 06:55:52 +0200 Original-Received: from localhost ([127.0.0.1]:42072 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jv3aV-0005sC-IT for ged-emacs-devel@m.gmane.org; Sun, 11 May 2008 00:55:07 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jv3aQ-0005rU-S7 for emacs-devel@gnu.org; Sun, 11 May 2008 00:55:02 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jv3aP-0005rI-Lk for emacs-devel@gnu.org; Sun, 11 May 2008 00:55:02 -0400 Original-Received: from [199.232.76.173] (port=38395 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jv3aP-0005rF-H8 for emacs-devel@gnu.org; Sun, 11 May 2008 00:55:01 -0400 Original-Received: from tfkpsv.physik.uni-erlangen.de ([131.188.164.197]:18360) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jv3aP-0004M5-1h for emacs-devel@gnu.org; Sun, 11 May 2008 00:55:01 -0400 Original-Received: from tfkp07.physik.uni-erlangen.de (tfkp07.physik.uni-erlangen.de [131.188.164.207]) by tfkpsv.physik.uni-erlangen.de (Postfix) with ESMTP id C7C3421868; Sun, 11 May 2008 06:54:58 +0200 (CEST) In-Reply-To: <877ie1k9id.fsf@jurta.org> X-Mailer: VM 8.0.9 under Emacs 22.2.1 (i686-pc-linux-gnu) X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:96957 Archived-At: On Sun May 11 2008 Juri Linkov wrote: > However, now `proced' displays only processes belonging to the current > user, and not all processes. Could you add a filter, e.g. asking in > the minibuffer to select among values "all" and "user"? Proced already allows you to choose a "listing type" (via proced-listing-type bound to l). Note that this is customizable via proced-command-alist. The idea is that here you can play with the options of ps(1) (of course, this depends greatly on the rather different options available on different systems). In the future I also want to a add a filter-like behavior that allows you to either mark processes or to restrict the display to those processes that would otherwise be marked. (It's a bit annoying that ps(1) comes in rather many different flavors. I want to keep it seperate as much as possible what is achieved in proced via ps(1) itself and via the elisp layer on top of it.) > Another feature I suggest is to put column names to the buffer's > header line, so scrolling will keep them visible in the header > line. Thanks, that's a good idea (that will probably even simplify a few other things that work around the first line in the proced buffer because this line does not display a process). > And another small thing I suggest to rename an improper buffer name > "*Process Info*" (this can be confused with the information about > one particular process). Maybe a better name is "*Process List*" > (this would be like "*Buffer List*"). But if this will conflict > with `list-processes' with the same buffer name, then maybe a > simple buffer name `*Proced*' would be more descriptive? As "*Process List*" is already used by list-processes, "*Proced*" is probably best (similar to "*Ibuffer*"). Also, the code is such that one can rename the proced buffer and have several proced buffers in parallel that use different listing types / filters. Roland