unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: "Roland Winkler" <Roland.Winkler@physik.uni-erlangen.de>
Cc: emacs-devel@gnu.org
Subject: Re: proced.el -- operate on processes like dired
Date: Sun, 11 May 2008 02:57:34 +0300	[thread overview]
Message-ID: <877ie1k9id.fsf@jurta.org> (raw)
In-Reply-To: <18421.33333.742725.806352@tfkp07.physik.uni-erlangen.de> (Roland Winkler's message of "Fri, 4 Apr 2008 03:19:49 +0200")

> Juri Linkov wrote:
>> BTW, I noticed one inconsistency between Proced and Dired: in Proced
>> `DEL' doesn't remove the mark from the previous line, unlike Dired.
>
> This will be fixed in Proced. It's more annoying that this is
> inconsistent between Dired and Ibuffer. ibuffer-unmark-backward
> unmarks the buffer on the current line, unlike dired-unmark-backward.

Thanks, and new sorting commands are very useful.

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"?

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.

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?

-- 
Juri Linkov
http://www.jurta.org/emacs/




  reply	other threads:[~2008-05-10 23:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3skyeu90i.fsf@tfkp07.physik.uni-erlangen.de>
2008-03-25 21:00 ` proced.el -- operate on processes like dired Richard Stallman
2008-03-25 22:57   ` Roland Winkler
2008-03-26  1:09     ` Mathias Dahl
2008-03-26  2:51       ` Roland Winkler
2008-03-26  9:06         ` Mathias Dahl
2008-03-26 22:25       ` Richard Stallman
2008-03-26 22:40         ` Drew Adams
2008-03-30 22:34         ` Juri Linkov
2008-03-31  7:40           ` Mathias Dahl
2008-04-04  1:19           ` Roland Winkler
2008-05-10 23:57             ` Juri Linkov [this message]
2008-05-11  4:54               ` Roland Winkler
2008-05-11  5:01                 ` dhruva
2008-03-29 22:17       ` Roland Winkler
2008-03-30  1:01         ` Mathias Dahl
2008-03-30  2:53           ` Roland Winkler
2008-03-31 18:38             ` Chad Brown
2008-03-26  2:02     ` Stefan Monnier
2008-03-26  2:40       ` Roland Winkler
2008-03-26  7:42         ` Glenn Morris
2008-03-26 15:08           ` Roland Winkler
2008-03-26 22:25     ` Richard Stallman
2008-03-30  3:25   ` T. V. Raman
2008-05-11 13:54 Roland Winkler
2008-05-11 17:47 ` Óscar Fuentes
2008-05-13  2:48   ` Roland Winkler

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=877ie1k9id.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=Roland.Winkler@physik.uni-erlangen.de \
    --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).