Skip to content

Add tooling to allow for user-defined post question pick command #351

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

john-d-murphy
Copy link

@john-d-murphy john-d-murphy commented Mar 30, 2025

For CPP files, I found that I needed an extra file in my code folder to prevent my editor's code anaylsis from throwing spurious warnings.
It makes sense to copy this file into the code folder after every pick action, and it also makes sense to not have this hard-coded since other people's dev environments may be different.
Therefore, this PR allows a user to set thier own default action to take after a pick action has been completed.

I'm happy to make any edits to this or to have this thrown out - it's my first bit of Go code and I'm not sure if this even warrants a feature request.

For context, I'm using this to push build commands and a test framework to each problem so I can do a build and test on a given problem's tests in vim directly.

@j178
Copy link
Owner

j178 commented Mar 31, 2025

Thanks for your PR! I’m unavailable to review it at the moment, but I’ll get back to it in about a week. Thanks for your patience!

@john-d-murphy
Copy link
Author

Thanks for your PR! I’m unavailable to review it at the moment, but I’ll get back to it in about a week. Thanks for your patience!

No problem! Whenever you're ready. I realized I needed to write the code for my use case, and I figured I'd share. Absolutely no rush, and I'm happy to describe how/why I'm using it when you're ready.

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

Successfully merging this pull request may close these issues.

2 participants