unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Ingo Lohmar <i.lohmar@gmail.com>
Cc: 22595@debbugs.gnu.org
Subject: bug#22595: 25.1.50; Wishlist: There should be a way to list timers
Date: Tue, 9 Feb 2016 07:16:56 -0800 (PST)	[thread overview]
Message-ID: <10585fb1-f262-4b56-98ab-3b6f627fd942@default> (raw)
In-Reply-To: <87bn7qarzs.fsf@gnus.org>

> > 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?
> 
> Reductio ad absurdum isn't very useful as an argumentation technique.
> 
> I have often wanted to examine (and cancel) certain timers that are out
> of control.  Inspecting them without a buffer like this isn't easy.

I'm with Lars on this one.  What is an implementation detail from
one point of view, and for one user, can be a "user-level feature"
for another user.

Many Emacs users interact with Emacs at deeper levels, where a
text/overlay property is an object of concern, not just something
behind the scenes.  Likewise for other objects: processes, timers,
whatever.

And we do have UIs for working with overlays or text properties.
At least I do.  Likewise, interacting with keymaps and font-lock.

No one is obliged to use a UI that provides easier access to such
things, but that access can be useful for some Emacs users.  Some
Emacs users will never go near hexl mode, but for those who do,
it is useful.





  reply	other threads:[~2016-02-09 15:16 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
2016-02-09 14:16       ` Lars Ingebrigtsen
2016-02-09 15:16         ` Drew Adams [this message]
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

  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=10585fb1-f262-4b56-98ab-3b6f627fd942@default \
    --to=drew.adams@oracle.com \
    --cc=22595@debbugs.gnu.org \
    --cc=i.lohmar@gmail.com \
    --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 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).