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

Extraneous file reads

In system 79.40, ...

When I have a file FOO.BAR#> and I explicitly write it to FOO.BAR#100 (which
is higher than any existing FOO.BAR), then a Find File occurs (eg, via Tags
Search), Zwei finds out it needs to use FOO.BAR#100, so reads it from disk
rather than using it out of my buffer. Why can't it use the copy that is in
the unmodified buffer, rather than risking my having two initially-identical 
but soon-to-diverge copies of the same stuff in core? ... or at least offer to
do so?

Additionally, M-X Compile File always prompts for a buffer name to compile,
yet last time I used it -- many versions ago -- it wanted to always read off
of disk even when there was an unmodified copy in core. If it's going to use
the copy off of disk, it might as well prompt for a buffername instead of a 
filename. I stopped using M-X Compile File as a result of this; now I just
use QC-FILE or QC-FILE-LOAD from lisp listeners because they seem to do more
natural things. I wish these were Zwei commands...

Accessing files from remote file systems is very slow and cleaning up little
points like this save a lot of time and hassle ...