all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Michael Olson <mwolson@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: remember(-diary).el
Date: Mon, 03 Dec 2007 16:44:06 +0100	[thread overview]
Message-ID: <47542446.9010400@gmail.com> (raw)
In-Reply-To: <874pezx141.fsf@grepfind.mwolson.org>

Michael Olson wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
> 
>>> From: Michael Olson <mwolson@gnu.org>
>>> I want to be able to pop up a warning window upon loading a file
>>> (this window can be disabled by the user) which tells people of the
>>> issue, and which registry key to change in order for it not to be a
>>> problem anymore.
>> That's be harassing the user, a very un-Emacsy thing to do, IMO.
> 
> I don't think of it as harassing the user -- if something has
> nondeterministic behavior whenever its source code gets checked out, I
> want to warn people about it.  Obviously the message that appears would
> need to be invective-free and informative.  And since it appears during
> load, it needs to contain instructions for how to disable the display of
> the message.


One may feel differently about this, but for me it sounds like the right 
thing to do in a case like this. It is however very important that the 
message is (very) easy to turn off - and that the information in the 
message is easy to find again.

Actually I believe that this way of handling the problem is what 
computer users expects today. However I also agree with Eli that it 
could be harassing the user. It must be used with caution.

I have tried to avoid this as much as possible (though I felt a bit 
differently in the beginning). In one important case I use it now. It is 
for a package where you do not get the full benefit of it unless you 
turn on some things that may influence Emacs outside of that package 
too. I then inform the user of that this way, using display-buffer to 
show the message and from there the user can turn on those things or 
just choose not to see the message any more.

  reply	other threads:[~2007-12-03 15:44 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21  7:24 remember(-diary).el martin rudalics
2007-11-21  7:32 ` remember(-diary).el Miles Bader
2007-11-21  8:39   ` remember(-diary).el Glenn Morris
2007-11-21 18:49     ` remember(-diary).el Eli Zaretskii
2007-11-21 23:57       ` remember(-diary).el John Wiegley
2007-11-21  8:44   ` remember(-diary).el martin rudalics
2007-11-21 13:55     ` remember(-diary).el Miles Bader
2007-11-21 17:06       ` remember(-diary).el martin rudalics
2007-11-21 18:50       ` remember(-diary).el Eli Zaretskii
2007-11-22  2:13         ` remember(-diary).el Miles Bader
2007-11-22  4:18           ` remember(-diary).el Eli Zaretskii
2007-11-22  8:57             ` remember(-diary).el martin rudalics
2007-11-22  9:44               ` remember(-diary).el joakim
2007-11-23  4:35                 ` remember(-diary).el Richard Stallman
2007-11-23 20:56                   ` remember(-diary).el Stephen J. Turnbull
2007-11-23 21:46                     ` remember(-diary).el David Kastrup
2007-11-22 10:41               ` remember(-diary).el Leo
2007-11-22 23:57                 ` remember(-diary).el Juri Linkov
2007-11-23  0:10                   ` remember(-diary).el Leo
2007-11-30  6:17                     ` remember(-diary).el Michael Olson
2007-11-30  8:27                       ` remember(-diary).el Leo
2007-11-30 12:40                         ` remember(-diary).el Michael Olson
2007-11-22  2:27     ` remember(-diary).el Richard Stallman
2007-11-30  6:22       ` remember(-diary).el Michael Olson
2007-11-30 16:48         ` remember(-diary).el Richard Stallman
2007-11-30 18:42           ` remember(-diary).el Michael Olson
2007-11-30 19:06             ` remember(-diary).el Glenn Morris
2007-11-30 22:11               ` remember(-diary).el Michael Olson
2007-11-30 22:22                 ` remember(-diary).el Leo
2007-12-01  9:07                   ` remember(-diary).el Eli Zaretskii
2007-12-01  9:56                     ` remember(-diary).el David Kastrup
2007-12-01  9:06                 ` remember(-diary).el Eli Zaretskii
2007-12-02 21:33                   ` remember(-diary).el Michael Olson
2007-12-03  4:18                     ` remember(-diary).el Eli Zaretskii
2007-12-03 15:13                       ` remember(-diary).el Michael Olson
2007-12-03 15:44                         ` Lennart Borgman (gmail) [this message]
2007-12-03  1:05                   ` remember(-diary).el Michael Olson
2007-12-03  4:22                     ` remember(-diary).el Eli Zaretskii
2007-12-03 14:40                       ` remember(-diary).el Stefan Monnier
2007-12-03 20:51                         ` remember(-diary).el Eli Zaretskii
2007-12-01 17:59             ` remember(-diary).el Richard Stallman
2007-11-30 20:57         ` remember(-diary).el Eli Zaretskii
2007-11-30 22:07           ` remember(-diary).el Michael Olson
2007-12-05  1:22       ` remember(-diary).el Michael Olson
2007-12-05  4:46         ` remember(-diary).el Eli Zaretskii
2007-11-21 18:24 ` remember(-diary).el Sven Joachim
2007-11-21 18:54   ` remember(-diary).el Eli Zaretskii
2007-11-22 13:32   ` remember(-diary).el martin rudalics
2007-11-22 23:57     ` remember(-diary).el Juri Linkov

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=47542446.9010400@gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mwolson@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 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.