all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ingo Lohmar <i.lohmar@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: 22595@debbugs.gnu.org
Subject: bug#22595: 25.1.50; Wishlist: There should be a way to list timers
Date: Tue, 09 Feb 2016 15:10:07 +0100	[thread overview]
Message-ID: <87h9hiht4w.fsf@acer.localhost.com> (raw)
In-Reply-To: <87k2mekaye.fsf@gnus.org>

On Tue, Feb 09 2016 11:02 (+1100), Lars Ingebrigtsen wrote:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> When working with timers, it's very easy to get into a situation where
>>> you've started a timer, but you don't have the timer object handy.  It
>>> would be very nice if we had a command that would list all timers
>>
>> Maybe I'm missing something here, but the two lists timer-list and
>> timer-idle-list already provide you with the list you wanted.  No?
>
> Sure, the lists are there, but there isn't a user interface to list them
> and kill them.



Why is this a good idea at all?  Timers are always an implementation
detail, not a user-level feature, as far as I am concerned.  We neither
have a UI for working with all overlays or text properties of a buffer,
have we?





  parent reply	other threads:[~2016-02-09 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08  6:15 bug#22595: 25.1.50; Wishlist: There should be a way to list timers Lars Ingebrigtsen
2016-02-08 17:08 ` Eli Zaretskii
2016-02-09  0:02   ` Lars Ingebrigtsen
2016-02-09  2:36     ` Lars Ingebrigtsen
2016-02-09 14:10     ` Ingo Lohmar [this message]
2016-02-09 14:16       ` Lars Ingebrigtsen
2016-02-09 15:16         ` Drew Adams
2016-02-09 17:13           ` Ingo Lohmar
2016-02-09 17:37             ` Drew Adams
2016-02-09 17:02         ` Ingo Lohmar
2016-02-09 17:31       ` Eli Zaretskii
2016-02-09 18:32         ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h9hiht4w.fsf@acer.localhost.com \
    --to=i.lohmar@gmail.com \
    --cc=22595@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.