From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.com>,
"'Fabian Ezequiel Gallina'" <galli.87@gmail.com>
Cc: "'Óscar Fuentes'" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: RE: Deprecate _emacs on Windows
Date: Wed, 23 Mar 2011 06:42:16 -0700 [thread overview]
Message-ID: <3E42E56342C648C0B0DFA48F9D10659A@us.oracle.com> (raw)
In-Reply-To: <AANLkTimeuWJC=_ykoPWjyL0QXSHMWSjv5G7vLUNOB3+N@mail.gmail.com>
> > 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)"
BTW, IIUC it is not yet obsolete - it is still supported. It is being
deprecated at this time, not desupported.
> Are you trying to provoke Drew a heart attack?
Can't resist, can you? Drop the snide remarks, please. It's not about me,
Juanma, remember? Stop trying to caricature me.
> 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).
Actually, IMO the suggestion is a reasonable one.
My point was that this information for the user is not a warning of anything, so
it should not scream WARNING. (I also think it is more appropriate to convey
deprecation info in NEWS and manual, but a non-warning message is OK if it is an
addition.)
As with some other places in Emacs, the user response to the question could be
more than a binary choice. E.g., (a) rename now, (b) do nothing now, and (c) do
not rename and don't remind me again. With either (a) or (c) the user will see
the message only once.
Dunno whether there might be any problem from doing this at its current position
during startup: lots of stuff can go on before (just a guess) and after
(definitely) the message appears. Maybe it should wait until Emacs is idle for
some given period? Dunno.
Interrupting the user also has the advantage that s?he will necessarily see the
message. In my case, the *Warning* buffer appeared (splitting the window)
briefly, and then disappeared as the rest of my startup sequence finished. If I
had not noticed the window-split briefly I would not have been aware that there
was a *Warning* buffer somewhere with a message for me. Some users with a
shorter startup sequence might well miss it. (And no, please do not just add a
long `sleep-for' or something.)
On the other hand, perhaps something would need to be done to inhibit the
message when Emacs is used in batch mode. But that is perhaps in order anyway,
regardless of whether the message asks the user a question. Maybe this has
already been taken care of - dunno.
next prev parent reply other threads:[~2011-03-23 13:42 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
2011-03-23 13:42 ` Drew Adams [this message]
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=3E42E56342C648C0B0DFA48F9D10659A@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=galli.87@gmail.com \
--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).