[Geany-Users] 1.25 incorrectly detecting file changes

Tim Tisdall tisdall at xxxxx
Fri Jul 24 14:27:07 UTC 2015

On 21 July 2015 at 17:04, Matthew Brush <mbrush at codebrainz.ca> wrote:
> On 15-07-21 11:42 AM, Tim Tisdall wrote:
>> I'm using Ubuntu's network drive system to edit files on a remote system so
>> the filenames are "/run/user/1000/gvfs/sftp:host= ...".  This wasn't an
>> issue with the 1.24 release and only started happening after upgrading to
>> 1.25.
> I've never heard of it. One thing you could try is to watch the files using `inotifywait` (in `inotify-tools` package) like:
>     $ inotifywait -m /path/to/a/file/in/question
> And see if it reports changes. Another way (since I don't think Geany uses inotify by default but rather just stat's the file), would be something like:
>     $ watch -n 1 stat -c '%y' /path/to/a/file/in/question

Okay, I'm not sure how it supposed to work, but here's what happens on
my machine with the 1.25:

inotifywait seems to register nothing when I save the file.  When the
warning comes up in Geany and I pick "relead", then inotify registers
three actions:  "OPEN", "ACCESS", and "CLOSE_NOWRITE,CLOSE".

watch is rather annoying because it doesn't give an ongoing log of
changes.  I turned on the '-d' to highlight the changes, but it'd
still be better if it gave an ongoing log.  The result with that was
that it only seemed to update the timestamps once.  However, it's
possible that since it's polling once a second that two timestamp
changes occurred within that one second and I'm just not able to see
that.  :(

So, I'm not really sure if we're any further ahead with figuring out
the issue...  Are there any other tests I could try?

More information about the Users mailing list