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

[Feature request] Customize savehist, recentf, places save files locations #15499

Open
pataquets opened this issue May 7, 2022 · 4 comments
Open

Comments

@pataquets
Copy link
Contributor

I was trying to customize some file location variables to be in my ~/.spacemacs.d/directory.
Some examples:

  • recentf-file-name
  • save-hist-file
  • save-place-file

Doing it on user-init ended up with the values being overwritten. And doing it on user-config, although somewhat worked, also created files on my .emacs.d dir anyway, adding unnecessary cruft.

I've found the corresponding init-* functions in the spacemacs-defaults layer, which have the directory spacemacs-cache-directory hard-coded, so it looks like to me that it is not possible to do this cleanly. No matter how you approach it, you'll be always working around Spacemacs' logic, which might change in the future.
(As a side note, I wonder if these files belong to the cache dir, but that's another story and it may be just my usage, which is keeping them synchronized between PCs via Dropbox).

If the feature is acceptable and someone is interested into picking this up, what would be the way to expose this?
Adding some dotspacemacs-* variables to be customizable on dotspacemacs/init would be enough?
What would be the recommended naming?

@github-actions
Copy link

github-actions bot commented May 7, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label May 7, 2023
@pataquets
Copy link
Contributor Author

Still interested

@github-actions github-actions bot removed the stale marked as a stale issue/pr (usually by a bot) label May 7, 2023
Copy link

github-actions bot commented May 6, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label May 6, 2024
@pataquets
Copy link
Contributor Author

Still interested

@github-actions github-actions bot removed the stale marked as a stale issue/pr (usually by a bot) label May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant