Thanks for politely listening to the explanations, some people are so angry
they lost data (sort of understandable immediately after it happens) that they
simply won't listen.
> However, you should at least modify the error message in geany so that the
> user is warned (in red) to save its
OK, thanks for the explanations...
However, you should at least modify the error message in geany so that the user
is warned (in red) to save its file on another partition before exiting geany.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
No, gedit does not use GIO _unmodified_, it carries a workaround to the GIO
issue (which leaves a truncated file in some cases, its described in the wiki
article), and that workaround depends on the internal workings of GIO AFAICT.
That may be fine for something like gedit where it is part of
>To be clear, running out of disk part way through writing the file is a
>hardware problem. Your hardware doesn't have a big enough disk :)
I don't agree with you...
I did some tests in a VM with geany and some other editors and the same
situation. Here are the results:
- geany => nulls out
You can set the atomic file saving setting (and only that one, see the wiki
article) to get the best chance of avoiding data loss.
But the process that provides atomic file saving doesn't work everywhere (like
on some network storage systems or windows systems) and it introduces other
problems
> The user just requested that the file be overwritten when they said "save".
> Clearly the content of their "precious" file doesn't matter any more, its the
> contents of the Geany buffer that the user wants to save that is important.
> And as the wiki article says, failing to save does not
> There is no way to think that when exiting an editor after it says there is
> no more space left on device, that editor will null out your precious file!
> So expecting that the user will save his data elsewhere before exiting is
> clearly not the correct way...
The user just requested that
> > Why not simply checking that the remaining space is greater than the
> > current file size and only allow to save in that case?
>
> Because that information is not available cheaply, reliably, and portably for
> all filesystem types and platforms Geany is available on, if a save fails
>
And as a further example of the problems with the approach, something as
"simple" as free space on a plain vanilla ext4 partition is complicated by the
fact that its a delayed allocation journalling file system, so free space is
only accurate just after a full filesystem sync and no other file
> Why not simply checking that the remaining space is greater than the current
> file size and only allow to save in that case?
Because that information is not available cheaply, portably for all filesystem
types and platforms Geany is available on, if a save fails just save somewhere
else and
> See
> https://wiki.geany.org/config/all_you_never_wanted_to_know_about_file_saving
>
> Which saving method are you using? Any method other than
> use_atomic_file_saving is likely to result in the behaviour you describe as
> indicated in the reference above.
No I don't have
duplicate of #1895 and others
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2494#issuecomment-625107556
Closed #2494.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2494#event-3311781726
See https://wiki.geany.org/config/all_you_never_wanted_to_know_about_file_saving
Which saving method are you using? Any method other than
use_atomic_file_saving is likely to result in the behaviour you describe as
indicated in the reference above.
--
You are receiving this because you are
When the partition is full, attempting to save a file in Geany results in a
complete file loss.
Geany version : 1.36
System : Ubuntu Linux 20.04 LTS
To reproduce :
1. Fill some partition until there is no space left on it. For example :
fallocate -l 100G bigfile
2. Edit a text file located in
15 matches
Mail list logo
