unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mathias Dahl" <mathias.dahl@gmail.com>
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, 30 Mar 2008 02:01:55 +0100	[thread overview]
Message-ID: <7dbe73ed0803291801l1a407a5cr39db76fc80af0850@mail.gmail.com> (raw)
In-Reply-To: <18414.49139.56167.451502@tfkp07.physik.uni-erlangen.de>

>  I am sorry for my ignorance...In what context is killing a useful
>  operation in a dired buffer? I revert my dired buffers pretty often
>  and this recovers any killed lines.

Yes, that's right, revert gets the lines back. The primary reason I
use kill is to avoid information overload when working with files. I
might mark files containing some regexp and the hits might be
distributed in many remote places in the directory. Toggling and
killing brings the marked files all neatly together, letting me work
with them easily. I too thought it was a strange feature to begin
with, but now I cannot live without it.

>  If there is a command proced-do-kill-lines analogous to
>  dired-do-kill-lines, it might be confusing that "killing" is usually
>  a very different and permanent operation in the context of unix
>  processes. (Right now k is bound to proced-send-signal. Certainly I
>  could change that. But what is the most intuitive / the least
>  counterintuitive key binding?)

Yes, `kill' in this context might be confusing. What about `flush'
which is used already in `flush-lines'. Or `remove' or `delete'?

/Mathias




  reply	other threads:[~2008-03-30  1:01 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
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 [this message]
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=7dbe73ed0803291801l1a407a5cr39db76fc80af0850@mail.gmail.com \
    --to=mathias.dahl@gmail.com \
    --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).