lifearttw / macfuse

Automatically exported from code.google.com/p/macfuse
0 stars 0 forks source link

MacFuse breaks TextMates auto-file-reload doohickie #119

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Use Text Mate
2. Mount a remote linux partion using sshfs
3. Open a file in TM. Make a change to that file locally. TM never reloads
the file

What is the expected output? What do you see instead?
Auto-reload works locally but breaks because of the way MacFUSE does
/something/

What version of the product are you using? On what operating system?
Latest on Mac OS x tiger

Please provide any additional information below.

Original issue reported on code.google.com by isanames...@gmail.com on 28 Feb 2007 at 11:38

GoogleCodeExporter commented 8 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

GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
(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

GoogleCodeExporter commented 8 years ago

Original comment by si...@gmail.com on 8 Jun 2007 at 7:59