[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [emacs-wiki-discuss] Re: files opened
From: |
Frederik Fouvry |
Subject: |
Re: [emacs-wiki-discuss] Re: files opened |
Date: |
Wed, 18 Aug 2004 11:55:44 +0200 (CEST) |
,-- On Sun, 15 Aug 2004 21:31:47 +0800, Sacha Chua wrote:
|
| Ccing the mailing list to see if someone can come up with a nice way
| to solve this problem. =)
|
| address@hidden writes:
|
| > When I have only the day planner file open, and I save it after a
| > modification, I find that the procedure has opened all planner pages
| > that are linked to from that page. That's a bit like opening a web
| > page in a browser and having it open for you all pages directly
| > linked from the page. It also makes buffer lists quite large, so
| > that they are harder to deal with, and highlighting takes quite a
| > bit of the time as well.
|
| > Better IMO would be to close files that were not opened before,
| > unless the interactive command given by the user implies that the
| > file should remain open (e.g. planner-goto, etc.). I don't really
| > know how one could go about doing this. Perhaps the easiest is by
| > checking if a file is opened first, and restoring the situation
| > after updating it. It seems that planner-update-task() is to
| > "blame". (There doesn't seem to be a simple defadvice() way round
| > it.)
|
| Excellent idea. =) Closing files immediately after planner-update-task
| will result in lots of churning, though. Maybe we can do it the way
| the calendar does it? I know there's similar code in
| planner-kill-calendar-files. Before saving, we can make a list of all
| open planner files, and then restore this list after all the saving is
| finished.
I've been using the code I sent you (opening the file for every
link), and (not surprising) it's fairly slow. I hadn't sat down
and thought about a better way, but your proposal sounds good.
Is there any way to switch off (temporarily) highlighting when
files have to be opened in the background? That would make it
even faster. (This of course under the assumption that the
text-properties are not needed for the update.)
There's some more file-finding going in with plan() as well.
Cheers,
Frederik