emacs-wiki-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [emacs-wiki-discuss] Strange planner problem


From: Jim Ottaway
Subject: Re: [emacs-wiki-discuss] Strange planner problem
Date: Tue, 29 Nov 2005 16:02:30 +0000
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

>>>>> David Lord <address@hidden> writes:

> Hi,
> I'm getting a really odd problem with the latest versions of
> planner-muse (planner-muse--mwolson--1.0--patch-116) and muse
> (3.02.02) (tarballs downloaded from
> http://www.mwolson.org/static/dist/).  When I do M-x plan after
> starting up emacs (21.3.1 Windows 2000 with cygwin), it asks for the
> password for one of the remote machines that I sometimes connect to
> using ange-ftp. Then, whether I put in the password or not, it hangs
> with 'Preparing diary...' in the minibuffer; it doesn't appear to be
> consuming CPU.  If I do C-g, it seems to have loaded the day-page
> correctly.

> Regards
> David


Do you have a link to a file on that remote machine in one of your
plan pages?

I noticed this behaviour a few days ago and since.  I have tracked it
down to links like this: '[[/su::/etc/ssh/sshd_config][sshd_config]]'.
It happens with a minimal muse installation [i.e., nothing link
muse-wiki loaded] and a minimal test muse page containing nothing but
that explicit link.

It seems to me that this happens during the font-locking of explicit
links.  In particular the use of file-exists-p in muse-link-face
provokes Emacs into using tramp for the link
'/su::/etc/ssh/sshd_config'. It only happens once, of course, since
the password is cached by tramp [by default].  The problem goes away
if one removes the test for file existence from muse-link-face.

I don't know what the solution is, except perhaps for not checking for
the existence of files that look like tramp files [using
tramp-file-name-regexp, I suppose].

I don't know about ange-ftp, but I would imagine the problem is the
same there as for tramp.

Regards,

-- 
Jim Ottaway




reply via email to

[Prev in Thread] Current Thread [Next in Thread]