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

Add a command line flag to specify the archive location #5

Open
codecircuit opened this issue Mar 26, 2020 · 3 comments
Open

Add a command line flag to specify the archive location #5

codecircuit opened this issue Mar 26, 2020 · 3 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@codecircuit
Copy link

This would be useful if you do not want to store the matrices in your home directory.

@tcojean
Copy link
Member

tcojean commented Mar 29, 2020

Thanks for your input on this!

I agree something needs to be done here. My question is how to do it properly. Let's try to collect some options:

  • Use a configuration file (e.g. .ssget.conf) in ~/.config/ and/or /etc/default/ssget.conf, or anything else with custom options stored inside such as ARCHIVE_LOCATION=/custom/path/to/archive (could also allow extension to other options if needed);
  • Have a command line switch which changes the default location (also creating a configuration file somewhere?) and eventually moves any preexisting archive to the new location at the same time;
  • A combination of the two?
  • Anything else?

@tcojean tcojean added enhancement New feature or request good first issue Good for newcomers labels Mar 29, 2020
@codecircuit
Copy link
Author

codecircuit commented Mar 30, 2020

As far as I understood it you must first query the matrix IDs like this:

ids=$(ssget -s "[ @name == matrixname ] || [ @name == othermatrixname]")

before you can download them with

for id in $ids; do
  ssget -i $id -e
done

It would be cool if you can just add -e to the first command and all matrices matching the predicate are downloaded. But instead of overloading this issue, maybe we open one issue for each feature?

@tcojean
Copy link
Member

tcojean commented Mar 31, 2020

Indeed as that is another feature I think another issue on the subject would be better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants