unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: Errors on missing completion?
Date: Fri, 21 Mar 2008 01:26:19 +0100	[thread overview]
Message-ID: <47E300AB.50607@gmail.com> (raw)
In-Reply-To: <87fxulhrh7.fsf@jurta.org>

Juri Linkov wrote:
>>> There is a special variable `debug-ignored-errors' with the list
>>> of error messages to ignore, and as I see it already contains
>>> "^No dynamic expansion for .* found$".  So when debug-on-error
>>> is non-nil, `dabbrev-expand' is not disturbing due to this variable.
>>> Do you have a test case where `debug-ignored-errors' gets ignored?
>> Thanks, I forgot about that variable.
>>
>> No, I can't understand what happened before right now. I get no error
>> now. I will try to actually read the error message next time ;-)
> 
> Ah, I now see what is wrong.  When `dabbrev-check-other-buffers' is nil,
> the error message is "No dynamic expansion for \"%s\" found in this-buffer"
> that is not matched by `debug-ignored-errors'.  The following patch
> fixes this.  All the rest messages are already covered by this list.


Oh, thanks. But wouldn't it be easier to use catch - throw in cases like 
this instead. Is not that what the debug-ignored-errors in a way implements?




      reply	other threads:[~2008-03-21  0:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 21:00 Errors on missing completion? Lennart Borgman (gmail)
2008-03-20 20:35 ` Juri Linkov
2008-03-20 21:11   ` Lennart Borgman (gmail)
2008-03-20 23:20     ` Juri Linkov
2008-03-20 23:50       ` Lennart Borgman (gmail)
2008-03-21  0:04         ` Juri Linkov
2008-03-21  0:26           ` Lennart Borgman (gmail) [this message]

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=47E300AB.50607@gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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 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).