unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fabian Ezequiel Gallina <galli.87@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: Deprecate _emacs on Windows
Date: Wed, 23 Mar 2011 10:36:11 -0300	[thread overview]
Message-ID: <AANLkTi=voxJsWYstgwG80kt2aU+V1sEPtw3dWtYHnfTU@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimeuWJC=_ykoPWjyL0QXSHMWSjv5G7vLUNOB3+N@mail.gmail.com>

2011/3/23 Juanma Barranquero <lekktu@gmail.com>:
> On Wed, Mar 23, 2011 at 13:23, Fabian Ezequiel Gallina
> <galli.87@gmail.com> wrote:
>
>> How about to make the warning interactive? giving the user the
>> posibility to let Emacs rename the file right there when the warning
>> is prompt?
>>
>> "_emacs is obsolete, do you want to let Emacs rename it to .emacs now? (y/n)"
>
> Are you trying to provoke Drew a heart attack?
>
> Or, more seriously, that would be too intrusive IMO, and you would
> need to add a way to silence it anway (in case the user does not want
> to rename it).
>
>     Juanma
>

I think it would be neat if a warning could be a simple string or a
cons where the car is the warning string and the cdr is a callback
that should be interactive (to be called via call-interactively):
Something like this: ("This foo should be a bar" . 'handle-foo-bar).

This way for warnings that can be assisted, a callback can be fired to
help the user to solve it. The "_emacs" to ".emacs" case is a good
example. Also is the case of deprecated vars.

The callback of course should let the user choose to take action or not.


Regards,
-- 
Fabián E. Gallina
http://www.from-the-cloud.com



  reply	other threads:[~2011-03-23 13:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 21:54 Deprecate _emacs on Windows Juanma Barranquero
2011-03-12 22:02 ` Lennart Borgman
2011-03-12 22:48   ` Drew Adams
2011-03-12 22:53     ` Lennart Borgman
2011-03-12 23:03       ` Drew Adams
2011-03-12 23:20         ` Lennart Borgman
2011-03-13  4:01   ` Stefan Monnier
2011-03-13  4:14     ` Juanma Barranquero
2011-03-22 20:38     ` Drew Adams
2011-03-22 20:50       ` Juanma Barranquero
2011-03-23  0:12         ` Drew Adams
2011-03-23  0:26           ` Juanma Barranquero
2011-03-23  0:58             ` Drew Adams
2011-03-23  1:34               ` Juanma Barranquero
2011-03-23  1:42                 ` Juanma Barranquero
2011-03-24 23:33                   ` Stephen J. Turnbull
2011-03-24 23:39                     ` Juanma Barranquero
2011-03-23  2:42                 ` Drew Adams
2011-03-23  3:00                   ` Juanma Barranquero
2011-03-23  3:20               ` Stephen J. Turnbull
2011-03-23  3:34                 ` Juanma Barranquero
2011-03-23  5:01                   ` Óscar Fuentes
2011-03-23 12:07                     ` Juanma Barranquero
2011-03-23 12:23                       ` Fabian Ezequiel Gallina
2011-03-23 12:30                         ` Juanma Barranquero
2011-03-23 13:36                           ` Fabian Ezequiel Gallina [this message]
2011-03-23 13:42                           ` Drew Adams
2011-03-23 14:30                             ` Juanma Barranquero
2011-03-23 17:40                             ` Stefan Monnier
2011-03-23 14:09                 ` Drew Adams
2011-03-23 16:23                   ` Stephen J. Turnbull
2011-03-13 22:49 ` Chong Yidong

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='AANLkTi=voxJsWYstgwG80kt2aU+V1sEPtw3dWtYHnfTU@mail.gmail.com' \
    --to=galli.87@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=ofv@wanadoo.es \
    /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).