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

If DB contains only one path, default to that path if one is not specified when using ls, ui, or the like #316

Open
felder opened this issue Aug 18, 2023 · 1 comment

Comments

@felder
Copy link

felder commented Aug 18, 2023

While not super essential, a nice feature would be for duc to assume a default for the path if the db only contains a single top level path and no path was specified.

This prevents having to separately query the database to find a path to specify.

For example:

# duc info -d filestore.db
Date       Time       Files    Dirs    Size Path
2023-08-18 21:04:14       0      13   52.0K /export/filestore
# duc ls -d filestore.db
Path /export/reports not found in database
Requested path not found
Segmentation fault (core dumped)
# duc ls -d filestore.db /export/filestore
 48.0K filestore

It just seems less useful for it to assume the cwd is the path when that is not in the index.

Also I assume the segfault is a result of #236

@felder felder changed the title If DB contains only one Path, default to that path if one is not specified when using ls, ui, or the like If DB contains only one path, default to that path if one is not specified when using ls, ui, or the like Aug 18, 2023
@felder
Copy link
Author

felder commented Aug 18, 2023

I just upgraded to duc 1.4.5 and I can happily report the segfault is gone.

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