Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[QoL] Improve the logic of backup_files #8

Open
RKI027 opened this issue Jun 27, 2024 · 0 comments
Open

[QoL] Improve the logic of backup_files #8

RKI027 opened this issue Jun 27, 2024 · 0 comments

Comments

@RKI027
Copy link
Owner

RKI027 commented Jun 27, 2024

Currently, it will overwrite any backup with the current file which may have been annotated, with a big warning to avoid that.

A better process would be:

  • still a no-op without a specific flag
  • with --warning=False and nothing else: check if backup already exists, in which case skip this file and only backup files for which no backup exists
  • with --warning=False and --overwrite-backup=True, unconditionally backup all files

I don't think there's a smarter way while keeping the behavior of the tool as it is (ie writing the output directly in the TexTools folder).

Another way would be to only work in the project directory and have another command to copy the backup or the annotated file in the TexTools folder
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RKI027