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.

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

A suggestion for "don't create backup~ files" in spacemacs/config.el #2271

Closed
xfq opened this issue Jul 7, 2015 · 4 comments
Closed

A suggestion for "don't create backup~ files" in spacemacs/config.el #2271

xfq opened this issue Jul 7, 2015 · 4 comments

Comments

@xfq
Copy link
Contributor

xfq commented Jul 7, 2015

In spacemacs/config.el:

;; don't create backup~ files
(setq backup-by-copying t
      make-backup-files nil
      create-lockfiles nil)

I suggest changing it to:

;; don't create backup~ files
(setq make-backup-files nil)

I understand the rationale for setting make-backup-files to nil (although the default value of vc-make-backup-files is already nil), but I think it isn't necessary to change the value of backup-by-copying and create-lockfiles. Here are my reasons:

  • The value of make-backup-files is already nil, so changing the value of backup-by-copying won't have any effect.
  • IMHO lockfiles are more important than backup files since they can prevent concurrent changes.
@geo7
Copy link
Contributor

geo7 commented Oct 23, 2015

@TheBB Is this still relevant? Aren't backups sent to cache or something now?

If not then Suggestions / discussion tag might fit here.

@xfq
Copy link
Contributor Author

xfq commented Oct 24, 2015

It's still relevant.

Although spacemacs-auto-save-directory is in spacemacs-cache-directory by default, what I said in the original post was irrelevant to the auto-saving feature, and is still true in the current develop.

@StreakyCobra
Copy link
Contributor

@xfq Can you propose your change in a PR? It would be better discussed there.

@StreakyCobra
Copy link
Contributor

This old issue has been waiting for a response for more than one month. As no answer has been provided, we can not help further or know if the issue is still relevant. We are then closing it. Feel free to open a new issue if there is any news on this side, be sure to read this guide first and link this issue in the new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants