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

Change cache location from ~/.mapscii to ~/.cache/.mapscii #60

Open
ghost opened this issue Feb 15, 2019 · 4 comments
Open

Change cache location from ~/.mapscii to ~/.cache/.mapscii #60

ghost opened this issue Feb 15, 2019 · 4 comments

Comments

@ghost
Copy link

ghost commented Feb 15, 2019

As suggested in this video (https://www.youtube.com/watch?v=AFtfpluqv14&t=585s) is a good practice to use the default folder, that is ~/.cache to put application cache files to have a cleaner home folder, so I would suggest updating the code and move the .mapscii folder in that folder.

@ghost ghost closed this as completed Feb 15, 2019
@ghost ghost changed the title Change cache location from ~/.mapscii to ~ Change cache location from ~/.mapscii to ~/.config/.mapscii Feb 15, 2019
@ghost ghost reopened this Feb 15, 2019
@ghost ghost changed the title Change cache location from ~/.mapscii to ~/.config/.mapscii Change cache location from ~/.mapscii to ~/.cache/.mapscii Feb 15, 2019
@jaller94
Copy link
Collaborator

Sounds like a great idea to allow the system or an administrator to clean up the cache or mount the ~/.cache to a temporary storage. 👍

Actual configs should go somewhere else (if mapscii ever gets those).

I think it should be ~/.cache/mapscii instead of ~/.cache/.mapscii. Is there any reason to make the sub folder a hidden folder?

@ghost
Copy link
Author

ghost commented Feb 16, 2019

Yeah, I think that ~/.cache/mapscii is better, there is no reason to make a hidden folder.

@jaller94
Copy link
Collaborator

Should a terminal message suggest users to clean up ~/.mapscii/cache? Should the files be copied over?

@ruppec
Copy link

ruppec commented Jul 6, 2020

Is this going to be implemented sometime soon?

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

2 participants