From: Lennon C. <le...@ri...> - 2008-08-13 09:19:58
Attachments:
signature.asc
|
rox-filer currently caches the contents of directories, including MIME types, for a certain amount of time. This is presumably because MIME sniffing could take a while under certain conditions (eg, a network mount). Thing being, it causes some fairly common instances when you have to refresh to get expected behavior: - Automounting of removables - if two happen at different times to be auto mounted to the same directory (eg, /media/usbdisk), then visiting that directory after plugging in the second will show the contents of the *first*, which isn't plugged into the system anymore. - Any modification to a file that causes it's MIME type to change - a common one is downloading a file via Fetch or a torrent client. In this case, the file starts off as empty (and hence, text/plain). The download completes, and the file gets renamed, and rox *continues to show it as text/plain*, and hence try to open it in a text editor. A less serious version of this is that when working on code, you might start of with a blank file, but after you've modified it, rox won't show the correct type (and hence often, the correct icon). I run into these things nearly every day. Are these really worth it for a bit of extra speed in some specific situations? -- Lennon Victor Cook "He who receives an idea from me receives without lessening, as he who lights his candle at mine receives light without darkening" -- Thomas Jefferso |
From: Tony H. <h...@re...> - 2008-08-13 13:54:25
|
On Wed, 13 Aug 2008 19:15:36 +1000 Lennon Cook <le...@ri...> wrote: > rox-filer currently caches the contents of directories, including MIME > types, for a certain amount of time. This is presumably > because MIME sniffing could take a while under certain conditions (eg, > a network mount). Thing being, it causes some fairly common instances > when you have to refresh to get expected behavior: [Snip] > I run into these things nearly every day. Are these really worth it for > a bit of extra speed in some specific situations? I guess a reasonable compromise would be to check mtime and/or size and invalidate the cached reading if it's changed. And unmounting should clear the cache for all items on the volume. -- TH * http://www.realh.co.uk |
From: Thomas L. <ta...@gm...> - 2008-08-13 20:21:24
|
2008/8/13 Lennon Cook <le...@ri...>: > rox-filer currently caches the contents of directories, including MIME > types, for a certain amount of time. I haven't looked at the code for a while, but I don't remember it doing that. If it re-reads a directory (which it will do when it detects a change) it should work out the type again. The talk of 'caches' in the xdgmime code is (I think) about caching the MIME database rather than the results. I opened a filer window and then, in an xterm, did: $ touch test $ rm test; echo '#!/usr/bin/env python' > test It updates from text to Python right away here (Linux). -- Dr Thomas Leonard ROX desktop / Zero Install GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 |
From: Alex A. <cir...@gm...> - 2008-08-15 17:39:00
|
On Wed, Aug 13, 2008 at 3:21 PM, Thomas Leonard <ta...@gm...> wrote: > 2008/8/13 Lennon Cook <le...@ri...>: > > rox-filer currently caches the contents of directories, including MIME > > types, for a certain amount of time. > > I haven't looked at the code for a while, but I don't remember it > doing that. If it re-reads a directory (which it will do when it > detects a change) it should work out the type again. The talk of > 'caches' in the xdgmime code is (I think) about caching the MIME > database rather than the results. > > I opened a filer window and then, in an xterm, did: > > $ touch test > $ rm test; echo '#!/usr/bin/env python' > test > What if you don't rm test? Keep the inode the same? > > It updates from text to Python right away here (Linux). > > > -- > Dr Thomas Leonard ROX desktop / Zero Install > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > rox-devel mailing list > rox...@li... > https://lists.sourceforge.net/lists/listinfo/rox-devel > -- - Alex Austin Circuitsoft Computer Services (651) 238-9273 www.circuitsoftcs.com "...and then I visited Wikipedia ...and the next 8 hours are a blur." |
From: Thomas L. <ta...@gm...> - 2008-08-17 10:18:17
|
On Fri, 15 Aug 2008 12:38:49 -0500, Alex Austin wrote: > On Wed, Aug 13, 2008 at 3:21 PM, Thomas Leonard <ta...@gm...> > wrote: > >> 2008/8/13 Lennon Cook <le...@ri...>: >> > rox-filer currently caches the contents of directories, including >> > MIME types, for a certain amount of time. >> >> I haven't looked at the code for a while, but I don't remember it doing >> that. If it re-reads a directory (which it will do when it detects a >> change) it should work out the type again. The talk of 'caches' in the >> xdgmime code is (I think) about caching the MIME database rather than >> the results. >> >> I opened a filer window and then, in an xterm, did: >> >> $ touch test >> $ rm test; echo '#!/usr/bin/env python' > test >> > What if you don't rm test? Keep the inode the same? Still works for me: $ touch test2 $ echo '#!/usr/bin/env python' >> test2 $ touch some-new-file (you have to change the directory in some way just to generate an event that will cause the filer to rescan it, but as soon as it rescans it sees the new type) Using the newer inotify it should be possible to get notified when a file inside a directory changes, even when the directory itself doesn't. ROX- Filer currently uses dnotify, except on the gio branch, which uses whatever gio uses. -- Dr Thomas Leonard http://rox.sourceforge.net GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 |
From: Stephen W. <st...@ke...> - 2008-08-17 10:27:39
|
Thomas Leonard <ta...@gm...> wrote: > Using the newer inotify it should be possible to get notified when a file > inside a directory changes, even when the directory itself doesn't. ROX- > Filer currently uses dnotify, except on the gio branch, which uses > whatever gio uses. dnotify stopped working for me when I upgraded from SuSE 10.2 to 11.0. As far as I can tell it compiles with dnotify support, it just doesn't notice when the directory changes. -- Stephen Watson http://www.kerofin.demon.co.uk/ If you read this on a mailing list, send any reply back to the list and not to me. Not even CC. My bleeding heart does not extend to charity |
From: Thomas L. <ta...@gm...> - 2008-08-19 21:07:42
|
2008/8/17 Stephen Watson <st...@ke...>: > Thomas Leonard <ta...@gm...> wrote: > >> Using the newer inotify it should be possible to get notified when a file >> inside a directory changes, even when the directory itself doesn't. ROX- >> Filer currently uses dnotify, except on the gio branch, which uses >> whatever gio uses. > > dnotify stopped working for me when I upgraded from SuSE 10.2 to 11.0. As > far as I can tell it compiles with dnotify support, it just doesn't notice > when the directory changes. Does dnotify work from the command line? -- Dr Thomas Leonard ROX desktop / Zero Install GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 |
From: Stephen W. <st...@ke...> - 2008-08-19 22:03:49
|
"Thomas Leonard" <ta...@gm...> wrote: > 2008/8/17 Stephen Watson <st...@ke...>: > > Thomas Leonard <ta...@gm...> wrote: > > > >> Using the newer inotify it should be possible to get notified when a file > >> inside a directory changes, even when the directory itself doesn't. ROX- > >> Filer currently uses dnotify, except on the gio branch, which uses > >> whatever gio uses. > > > > dnotify stopped working for me when I upgraded from SuSE 10.2 to 11.0. As > > far as I can tell it compiles with dnotify support, it just doesn't notice > > when the directory changes. > > Does dnotify work from the command line? Err, I didn't know that dnotify had a command line interface! apropos shows nothing. -- Stephen Watson http://www.kerofin.demon.co.uk/ If you read this on a mailing list, send any reply back to the list and not to me. Not even CC. Do you mind not farting while I'm saving the world? |
From: Thomas L. <ta...@gm...> - 2008-08-20 19:11:58
|
2008/8/19 Stephen Watson <st...@ke...>: > "Thomas Leonard" <ta...@gm...> wrote: > >> 2008/8/17 Stephen Watson <st...@ke...>: >> > Thomas Leonard <ta...@gm...> wrote: >> > >> >> Using the newer inotify it should be possible to get notified when a > file >> >> inside a directory changes, even when the directory itself doesn't. > ROX- >> >> Filer currently uses dnotify, except on the gio branch, which uses >> >> whatever gio uses. >> > >> > dnotify stopped working for me when I upgraded from SuSE 10.2 to 11.0. > As >> > far as I can tell it compiles with dnotify support, it just doesn't > notice >> > when the directory changes. >> >> Does dnotify work from the command line? > > Err, I didn't know that dnotify had a command line interface! apropos shows > nothing. $ dnotify --help Usage: dnotify [OPTION]... DIRECTORY... [-e COMMAND...] Execute a command every time the contents of a directory change. ... Maybe it's in a separate package? The Ubuntu command comes from the "dnotify" package. -- Dr Thomas Leonard ROX desktop / Zero Install GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 |
From: Stephen W. <st...@ke...> - 2008-08-20 19:54:16
|
"Thomas Leonard" <ta...@gm...> wrote: > 2008/8/19 Stephen Watson <st...@ke...>: > > "Thomas Leonard" <ta...@gm...> wrote: > > > >> 2008/8/17 Stephen Watson <st...@ke...>: > >> > Thomas Leonard <ta...@gm...> wrote: > >> > > >> >> Using the newer inotify it should be possible to get notified when a > > file > >> >> inside a directory changes, even when the directory itself doesn't. > > ROX- > >> >> Filer currently uses dnotify, except on the gio branch, which uses > >> >> whatever gio uses. > >> > > >> > dnotify stopped working for me when I upgraded from SuSE 10.2 to 11.0. > > As > >> > far as I can tell it compiles with dnotify support, it just doesn't > > notice > >> > when the directory changes. > >> > >> Does dnotify work from the command line? > > > > Err, I didn't know that dnotify had a command line interface! apropos shows > > nothing. > > $ dnotify --help > Usage: dnotify [OPTION]... DIRECTORY... [-e COMMAND...] > Execute a command every time the contents of a directory change. > ... > > Maybe it's in a separate package? The Ubuntu command comes from the > "dnotify" package. No such package in SuSE 11. There's an iwatch for inotify but nothing for dnotify. I wonder if SuSE have given up on dnotify. -- Stephen Watson http://www.kerofin.demon.co.uk/ If you read this on a mailing list, send any reply back to the list and not to me. Not even CC. Strange as I seem I'm getting stranger by the minute |
From: Stephen W. <st...@ke...> - 2008-08-29 11:47:07
|
Stephen Watson <st...@ke...> wrote: > "Thomas Leonard" <ta...@gm...> wrote: > > > >> 2008/8/17 Stephen Watson <st...@ke...>: > > >> > dnotify stopped working for me when I upgraded from SuSE 10.2 to > 11.0. > > > As > > >> > far as I can tell it compiles with dnotify support, it just doesn't > > > notice > > >> > when the directory changes. > > Maybe it's in a separate package? The Ubuntu command comes from the > > "dnotify" package. > > No such package in SuSE 11. There's an iwatch for inotify but nothing for > dnotify. I wonder if SuSE have given up on dnotify. This patch adds inotify support, overriding the dnotify support at compile time. -- Stephen Watson http://www.kerofin.demon.co.uk/ If you read this on a mailing list, send any reply back to the list and not to me. Not even CC. Forget the shooty dog thing. |