After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 761382 - Request to 'reload' after the file
Request to 'reload' after the file
Status: RESOLVED OBSOLETE
Product: anjuta
Classification: Applications
Component: unknown
3.18.x
Other Linux
: Normal major
: ---
Assigned To: Anjuta maintainers
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2016-02-01 02:19 UTC by John
Modified: 2020-11-06 20:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description John 2016-02-01 02:19:47 UTC
This error is very similar to https://bugzilla.gnome.org/show_bug.cgi?id=758567
but in my case, Ctrl-S does NOT seem to trigger the problem.

I get the annoying 'The file on the disk is more recent...' if I just try to run the modified program, which triggers a save and a recompile automatically. 

Anyway, as the author of the other bug indicate, it's possible to simply ignore the error, but if some modifications were made to the source, and then 'Refresh' pressed, then those modifications _are_ lost.

Note that this also is similar to a bug reported in version 2.1.1 (!) around 2008.
Comment 1 Sébastien Granjoux 2017-06-17 13:15:41 UTC
I have just tried but I don't get it. Do you get this every time and in all projects? I have tried with a newly created project, GTK in C.
Comment 2 John 2017-06-19 13:58:25 UTC
It seems that it has been solved now. 

I'm now using the anjuta-master from just before you updated Scintilla (I'll test that version later).

The original complaint was using the last stable version (3.18.0, from the webpage). I'd recommend doing a new official release...
Comment 3 Sébastien Granjoux 2017-06-19 19:28:36 UTC
Do you use GtkSourceView? I think it's linked to it.

Moreover, there is no change in master compared to 3.18, except this bug #756426 but it is in 3.18.2.

I think it could be linked to the speed of saving, so upgrading your computer could have fixed this too.
Comment 4 André Klapper 2020-11-06 20:22:02 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/anjuta/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.