unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David.Kastrup@t-online.de (David Kastrup)
Cc: emacs-devel@gnu.org
Subject: Re: Idea for determining what users use
Date: 27 May 2003 15:27:08 +0200	[thread overview]
Message-ID: <x51xyko6z7.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E19KdpQ-00072R-Rf@fencepost.gnu.org>

Richard Stallman <rms@gnu.org> writes:

> We have no good way to determine if anyone still uses a feature.
> Maybe we can create one.
> 
> Imagine a function called note-feature-used.
> You call it like this:  (note-feature-used 'foo "Foo").
> The first time you call it, it sends mail to
> emacs-features-used@gnu.org with subject Foo,
> asking you for permission to send it,
> and it records (setq foo t) in your .emacs file.
> If you call it again, it does nothing.
> 
> We could put these calls into various files and functions in order
> to find out (after the next release) whether anyone uses them.

Quite dangerous since it could be felt as a sort of privacy issue.
It must be carefully voiced.

Something like

Feature foo has been deprecated (? for info).  Complain (y/n)?

and then offer the usual "use it this time/don't ask again" dialog we
use for disabled commands.

After a while, one can remove the feature/command and instead do

Feature foo has been removed (? for info).  Complain (y/n)?

The info should explain why something is removed/deprecated and what
to use instead.  The mail buffer should be set up in a way that the
user can add his own comments and send, not just do this silently.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2003-05-27 13:27 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27 12:45 Idea for determining what users use Richard Stallman
2003-05-27 13:27 ` David Kastrup [this message]
2003-05-27 14:16 ` Vincent LADEUIL
2003-05-27 14:28 ` Stefan Monnier
2003-05-28  0:43   ` Kim F. Storm
2003-05-28  7:04     ` Juanma Barranquero
2003-05-28 13:54   ` Richard Stallman
2003-05-28 14:33     ` Stefan Monnier
2003-05-30  0:49       ` Richard Stallman
2003-05-27 14:39 ` Thien-Thi Nguyen
2003-05-27 15:32   ` Stephen J. Turnbull
2003-05-28 23:58   ` Richard Stallman
2003-05-29 11:35     ` Thien-Thi Nguyen
2003-05-30  0:48       ` Richard Stallman
2003-05-31 12:37         ` Thien-Thi Nguyen
2003-06-01 15:53           ` Richard Stallman
2003-06-01 20:26             ` Thien-Thi Nguyen
2003-06-03  4:06               ` Richard Stallman
     [not found] ` <m1r86ktqxx.fsf@vila.local.>
2003-05-28 13:54   ` Richard Stallman
2003-05-28 14:40     ` Vincent LADEUIL
     [not found]     ` <m1y90rp221.fsf@vila.local.>
2003-05-30  0:49       ` Richard Stallman
2003-05-30  7:28         ` Jan D.
2003-05-30 13:29           ` Stefan Monnier
2003-05-30 14:52             ` Jan D.
2003-05-30 15:40               ` Stefan Monnier
2003-05-30 16:32                 ` Alex Schroeder
2003-05-31 19:51                   ` Richard Stallman
2003-06-01  0:48                     ` Peter Lee
2003-06-01  1:24                     ` Luc Teirlinck
2003-06-01  1:59                       ` Luc Teirlinck
2003-06-02 11:16                         ` Richard Stallman
2003-06-03 22:55                           ` Kim F. Storm
2003-06-05  0:08                             ` Richard Stallman
2003-06-06  0:21                               ` Kim F. Storm
2003-06-07 10:22                                 ` Richard Stallman
2003-05-30 16:45                 ` Jan D.
2003-05-30 16:57                   ` Stefan Monnier
2003-05-31 19:51             ` Richard Stallman
2003-05-30 23:47 ` Kim F. Storm
2003-05-30 23:04   ` Miles Bader
2003-06-03 22:24     ` Kim F. Storm
2003-05-30 23:14   ` { SPAM 2 }::Re: " Luc Teirlinck
2003-05-30 23:40     ` Luc Teirlinck
2003-05-31 10:45     ` Kai Großjohann
2003-06-01 15:52   ` Richard Stallman
2003-06-01  5:06 ` Luc Teirlinck
2003-06-02 11:16   ` Richard Stallman
2003-06-03  2:43     ` Luc Teirlinck
2003-06-04  8:53       ` Richard Stallman
2003-06-03  4:05     ` Luc Teirlinck

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=x51xyko6z7.fsf@lola.goethe.zz \
    --to=david.kastrup@t-online.de \
    --cc=dak@gnu.org \
    --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).