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

Allow flameshot screen/full with no options #1964

Closed
veracioux opened this issue Oct 11, 2021 · 1 comment · Fixed by #1970
Closed

Allow flameshot screen/full with no options #1964

veracioux opened this issue Oct 11, 2021 · 1 comment · Fixed by #1970
Assignees
Labels
CLI CLI specific Enhancement Feature requests and code enhancements

Comments

@veracioux
Copy link
Contributor

veracioux commented Oct 11, 2021

If no options are specified to flameshot screen/full subcommands, I think we should open a file dialog, instead of printing an error message as we do currently. The dialog should behave just like the one triggered by the Save button in gui mode.

@mmahmoudian
Copy link
Member

I agree. It was weird to me as well. The only workaround I found was --path "" to make Flameshot open the save file dialog

@mmahmoudian mmahmoudian added Enhancement Feature requests and code enhancements CLI CLI specific labels Oct 12, 2021
@veracioux veracioux self-assigned this Oct 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLI CLI specific Enhancement Feature requests and code enhancements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants