From: "Roland Winkler" <winkler@gnu.org>
To: Daimrod <daimrod@gmail.com>
Cc: 14341@debbugs.gnu.org, Nic Ferrier <nferrier@ferrier.me.uk>
Subject: bug#14341: adding an auto toggle update keybinding to proced
Date: Tue, 14 May 2013 22:34:04 -0500 [thread overview]
Message-ID: <20883.556.473288.225804@gargle.gargle.HOWL> (raw)
In-Reply-To: <87mws5lowc.fsf@tanger.home>
On Wed May 8 2013 Daimrod wrote:
> Glenn Morris <rgm@gnu.org> writes:
> > (I'm not sure if proced-toggle-auto-update needs a keybinding, but I
> > don't use proced.)
I agree that proced-toggle-auto-update is not the kind of command
that justifies a keybinding.
> It should at least been documented by `proced-mode'. Something like:
>
> Type \\[proced-toggle-auto-update] to update automatically the process
> list. The time interval for updates can be configured via
> `proced-auto-update-interval'.
Thank you, makes sense. I'll do that.
> I'll probably send another that adds a new proced top level:
>
> proced-top
>
> that automatically turns on the auto-update.
If you like the auto-update, you can also set the default of the
buffer-local variable proced-auto-update-flag to t.
So I guess that a separate command proced-top would be needed only
if one starts several proced sessions, some with auto-update and
others without it. Does this happen? Normally, I have exactly one
proced session running for as long as my emacs session. And this one
session gets updated as needed.
next prev parent reply other threads:[~2013-05-15 3:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 9:00 bug#14341: adding an auto toggle update keybinding to proced Nic Ferrier
2013-05-08 7:20 ` Glenn Morris
2013-05-08 10:57 ` Daimrod
2013-05-08 12:08 ` Nic Ferrier
2013-05-15 3:34 ` Roland Winkler [this message]
2016-02-24 5:06 ` Lars Ingebrigtsen
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=20883.556.473288.225804@gargle.gargle.HOWL \
--to=winkler@gnu.org \
--cc=14341@debbugs.gnu.org \
--cc=daimrod@gmail.com \
--cc=nferrier@ferrier.me.uk \
/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).