[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: tramp+recentf: persistent errors due to expand-file-name
From: |
David Reitter |
Subject: |
Re: tramp+recentf: persistent errors due to expand-file-name |
Date: |
Tue, 12 Aug 2008 16:41:53 +0200 |
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.
smime.p7s
Description: S/MIME cryptographic signature
- tramp+recentf: persistent errors due to expand-file-name, David Reitter, 2008/08/10
- Re: tramp+recentf: persistent errors due to expand-file-name, Michael Albinus, 2008/08/11
- Re: tramp+recentf: persistent errors due to expand-file-name, David Reitter, 2008/08/12
- Re: tramp+recentf: persistent errors due to expand-file-name, Michael Albinus, 2008/08/12
- Re: tramp+recentf: persistent errors due to expand-file-name, Lennart Borgman, 2008/08/12
- Re: tramp+recentf: persistent errors due to expand-file-name,
David Reitter <=
- Re: tramp+recentf: persistent errors due to expand-file-name, Lennart Borgman (gmail), 2008/08/12
- Re: tramp+recentf: persistent errors due to expand-file-name, Stefan Monnier, 2008/08/12
- Re: tramp+recentf: persistent errors due to expand-file-name, Lennart Borgman (gmail), 2008/08/14