Open Akuli opened 6 months ago
Maybe one command is file specific and the other is directory specific?
The more I think about this, the more I want to make the commands project-specific. I think:
git grep -n some_function_name
, I'm probably refactoring all usages of a function in a single project. I want to run that git grep
from any file that happens to mention the function within that project, regardless of filetype. I don't want Porcupine to run that specific git grep
in other projects..pdf
files from .txt
files. I want to say python3 make-pdf.py {file_name}
and have it only affect .txt
files.git grep -n ...
pattern could be useful in any project, and I want Porcupine to autocomplete that everywhere. But I don't want it to blindly run git grep -n some_function_name
in a totally unrelated project like it does now.
I often do this:
python3 -m pytest
On the other hand, many other Porcupine users expect F5 to just run the file, no matter what file type it is.
I'm not sure what's the best solution. Maybe Porcupine should consider commands to be project-specific (not filetype-specific) when they don't use the
{file_name}
or{file_path}
substitution?