From: Carsten Dominik <carsten.dominik@gmail.com>
To: Dan Davison <dandavison7@gmail.com>
Cc: Jeff Horn <jrhorn424@gmail.com>,
emacs-orgmode@gnu.org, Andrea Crotti <andrea.crotti.0@gmail.com>
Subject: Re: Overlays and elisp code
Date: Tue, 1 Feb 2011 12:30:28 +0100 [thread overview]
Message-ID: <190ACAEA-E49A-434C-BC14-549FFCB3E0AA@gmail.com> (raw)
In-Reply-To: <m1oc6w579d.fsf@gmail.com>
On Feb 1, 2011, at 12:22 PM, Dan Davison wrote:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> Hi Dan,
>>
>> maybe just header in the default value to keep the echo area open for
>> error messages?
>
> Absolutely. But if you prefer, we could just do away with the echo-
> area
> message entirely. That would have the advantage of leaving the user
> interface unchanged.
>
> With the default as '(header), my UI change only makes sense if we
> believe that an appreciable number of users will disable the header
> message and activate the echo-area message in its place.
There are people who hate the header line IIRC. But I guess you are
right - once people are ready to remove the header line for this
application, they will probably have memorized it.
I remember that I started with the echo area and introduced the header
line because people were asking how to get out of there, so I needed
something more persistent.
So I guess if the header line is the default, I'd be fine with
removing the echo area message altogether.
- Carsten
next prev parent reply other threads:[~2011-02-01 11:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 10:04 Overlays and elisp code Andrea Crotti
2011-01-31 20:04 ` Jeff Horn
2011-02-01 8:08 ` Andrea Crotti
2011-02-01 10:51 ` Dan Davison
2011-02-01 11:01 ` Dan Davison
2011-02-01 11:08 ` Carsten Dominik
2011-02-01 11:22 ` Dan Davison
2011-02-01 11:30 ` Carsten Dominik [this message]
2011-02-01 11:47 ` Dan Davison
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=190ACAEA-E49A-434C-BC14-549FFCB3E0AA@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=andrea.crotti.0@gmail.com \
--cc=dandavison7@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jrhorn424@gmail.com \
/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/org-mode.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).