Closed GoogleCodeExporter closed 9 years ago
Rather than saying "latest", it's nicer to specify the exact release you're
using.
What do you mean by "make a change to that file locally"?
* Assuming that by "local" you mean the MacFUSE machine (and not the SSH
server), how are you making this
change?
* What do you mean by "works locally but breaks"?
* When TextMate does "auto-reload" the file (without MacFUSE in the picture),
how does it work? Do you see the
new data when you click on the TextMate window?
Original comment by si...@gmail.com
on 1 Mar 2007 at 12:37
Another question: what is "auto-file-reload doohickie"? I don't use TextMate.
Original comment by si...@gmail.com
on 1 Mar 2007 at 12:38
i believe TM does a stat of the file and if the mtime is updated, it reloads
the data.
Original comment by andrewde...@gmail.com
on 1 Mar 2007 at 7:00
isanamespace: This is not clear from your original report, but if you indeed
are modifying the file on the "remote"
SSH server and expecting the locally running TextMate to "pick up" the change,
keep in mind that both MacFUSE
and sshfs have a bunch of caches that will not let this happen -- this is how
it's supposed to work. You can turn
off most of these caches (not a good idea in general, but if you must):
sshfs user@host:/dir /mnt/point -onolocalcaches,cache=NO,...
'nolocalcaches' is for MacFUSE, and 'cache=NO' is for sshfs.
Original comment by si...@gmail.com
on 1 Mar 2007 at 11:10
http://code.google.com/p/macfusion/issues/detail?id=47
-- a distinction that may help to clarify the issue here.
Original comment by grahampe...@gmail.com
on 7 May 2007 at 3:59
Is it be somehow possible to easily clear the cache without having to
mount&unmount?
I'm having problem with the same issue. Btw the size of my file is 65MB, I'm
surprised that such a big file is being cached.
Original comment by Igor.Mi...@gmail.com
on 25 May 2007 at 12:28
Igor.Minar:
No, it is not possible to "clear" the cache. Users should neither fiddle with
nor worry about the buffer cache.
Why are you assuming that _all_ 65MB is cached? The kernel tries to cache
"recently accessed" stuff. It will
reclaim physical memory appropriately--again, users needn't worry about the
mechanism.
Original comment by si...@gmail.com
on 29 May 2007 at 7:18
(OT from MacFUSE, gold stars not working *again*. I had starred this issue but
knew nothing about these
updates. <http://code.google.com/p/support/issues/detail?id=272>.)
Original comment by grahampe...@gmail.com
on 2 Jun 2007 at 12:00
Original comment by si...@gmail.com
on 8 Jun 2007 at 7:59
Original issue reported on code.google.com by
isanames...@gmail.com
on 28 Feb 2007 at 11:38