all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Geoff Gole <geoffgole@gmail.com>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Annoying call to error in goto-history-element
Date: Tue, 7 Dec 2010 00:59:14 +0100	[thread overview]
Message-ID: <AANLkTim9fQLGqPyQsShtxH+OJ=VU=05qb2hzZm-29HO1@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin26RwcqEFWSVP3zdjiJLZuWBjRMjOaB2NevgDh@mail.gmail.com>

On Tue, Dec 7, 2010 at 12:48 AM, Geoff Gole <geoffgole@gmail.com> wrote:
> When moving through the history of find-file, running into the end of
> the history will result in an error message briefly and annoyingly
> obscuring the minibuffer. To see this, emacs -q C-x C-f <up>. The
> cause is calls to error in goto-history-element.
>
> It looks like in place of error we could call minibuffer-message and
> exit the function (see patch below), which would make for a more
> pleasant experience. Unfortunately that relies on the fact that the
> callers of goto-history-element don't perform any real work after
> their call to same, and that doesn't seem like a clean solution.
>
> The only other thing I can think of is writing a macro
> with-redirected-error-messages which would catch and redirect Lisp
> errors into calls to minibuffer-message, and adding that to the
> callers in question. I don't really like that either.
>
> Thoughts?

Is it necessary with a message at all here? Just some kind of visible
"beep" instead perhaps?



  reply	other threads:[~2010-12-06 23:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 23:48 Annoying call to error in goto-history-element Geoff Gole
2010-12-06 23:59 ` Lennart Borgman [this message]
2010-12-07  0:37   ` Geoff Gole
2010-12-07  1:07     ` Lennart Borgman

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='AANLkTim9fQLGqPyQsShtxH+OJ=VU=05qb2hzZm-29HO1@mail.gmail.com' \
    --to=lennart.borgman@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=geoffgole@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 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.