all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Michael Albinus <michael.albinus@gmx.de>,
	Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: tramp+recentf: persistent errors due to expand-file-name
Date: Tue, 12 Aug 2008 16:41:53 +0200	[thread overview]
Message-ID: <87EBED8D-437A-4B75-AF95-745C1CAE145F@gmail.com> (raw)
In-Reply-To: <e01d8a50808120604v5da4684cr24d9b51b36c19d50@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 615 bytes --]

On 12 Aug 2008, at 15:04, Lennart Borgman wrote:
>
> I agree, but there is a problem with this in Emas. If you protect  
> the code with condition-case it makes it very hard to find out where  
> the problem was. It would be good if someone find a way to enhance  
> this.

A condition-case in `run-hooks' could output a warning to *Messages*,  
but catch the error.
One can still run the debugger when such an error occurs.

While it's important for us to find bugs, users obviously don't want  
to be prevented from running a command just because an extension (and  
that's what the hooks mostly do) fails to run.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2193 bytes --]

  reply	other threads:[~2008-08-12 14:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-10 17:08 tramp+recentf: persistent errors due to expand-file-name David Reitter
2008-08-11 19:18 ` Michael Albinus
2008-08-12  7:01   ` David Reitter
2008-08-12 12:57     ` Michael Albinus
2008-08-12 13:04       ` Lennart Borgman
2008-08-12 14:41         ` David Reitter [this message]
2008-08-12 15:06           ` Lennart Borgman (gmail)
2008-08-12 19:27             ` Stefan Monnier
2008-08-14 18:35               ` Lennart Borgman (gmail)

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=87EBED8D-437A-4B75-AF95-745C1CAE145F@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    --cc=michael.albinus@gmx.de \
    /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.