I have found them more confusing than valuable, both when working on
projects and when teaching folks and they're curious about each of the new
files.
I guess we can be glad that the state of user backup/VCS is better now than
a decade ago! I tend to have little hope for things like that, but
While I agree that it is not KiCad's job to do archival backups or
version control, I do think that KiCad should preserve the integrity of
users data through a crash. Even better if the work between the last
save and the crash is also preserved and recovered on restart.
I have had to use
How does the current backup file strategy interact with the autosave feature?
If autosave works without it, that might address a lot of these concerns.
> On 29 Jun 2020, at 23:13, hauptmech wrote:
>
>
> While I agree that it is not KiCad's job to do archival backups or version
> control,
Autosave is independent of the back up file.
On 6/29/2020 6:22 PM, Jeff Young wrote:
> How does the current backup file strategy interact with the autosave feature?
> If autosave works without it, that might address a lot of these concerns.
>
>
>
>> On 29 Jun 2020, at 23:13, hauptmech
Currently, KiCad automatically creates backups of schematic and PCB
files when you save a file.
The logic for these backups is basically: if a file already exists
with the same name as what we are saving, copy that file to a new file
and give it the "-bak" suffix on the file extension.
These
I find them annoying and have to add them to my gitignore's etc constantly.
They're of no value to me because I tend to save every 30 seconds or so
while working.
The *one* thing they might be useful for is guarding against kicad
segfaulting or other failures (disk full, NFS connection lost,
I'm +1 on removing the backup files completely. I can see how they might
have been useful in the past given the save behavior, but I think the
recent changes to that have made them obsolete. I am also someone who puts
all my projects into a git repo, so I have always found them annoying and
never
That save process change is what I was referring to in (2)
The old save process (in 5.1 and earlier) is:
1) Move (not copy) filename.ext to filename.ext-bak
2) Write the save to filename.ext (a new file at this point)
Our current save process (in nightlies) is:
1) Copy filename.ext to
> On Jun 29, 2020, at 12:23 PM, Jon Evans wrote:
>
> Currently, KiCad automatically creates backups of schematic and PCB
> files when you save a file.
>
[snip]
>
> In other words, I don't think this feature actually gives enough value
> to make it worth the clutter in the project folder
9 matches
Mail list logo
