Disable for specific file types
See original GitHub issueHi, I was wondering if there’s a way to disable ultest
altogether for specific file types.
Use case: I’m setting MANPAGER
to neovim
, and when I open a man page, ultest
gives an error (there are no tests to run for a man page 😆). I tried to check :h ultest-config
, but looking quickly, I didn’t find any settings to achieve that
Thank you
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to Disable Preview for Certain File Types in Explorer ...
Let's say you want to disable preview generation for Microsoft Word documents — e.g., .docx , .doc , or other file types. Follow...
Read more >Restrict access to certain file types - TechNet - Microsoft
Based on my understanding, the Disallow of software restriction path rules means only disabling specific software which is in that specific path ...
Read more >How to Block Specific File Types in Windows Server 2012?
Right-click File Screens in the left pane again and select Create File Screen Exception from the menu. Select the group to exclude under...
Read more >How To Disable VS Code 'formatOnSave' For Specific File ...
Hit Cmd + S to save it and the formatOnSave will be disabled on extensions you listed in previous step. Step #4 —...
Read more >Turning off eslint rule for a specific file - Stack Overflow
You can turn off/change a particular rule for a file by putting the configurations at the top of the file. /* eslint no-use-before-define:...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for the error, this should be fixed in latest commit now!
Nice @rcarriga , updated the plugin and the error seems to be gone, thank you
But still, I think, it would be nice if there was an option in
vim-ultest
to allow disabling the plugin for specific file types (maybe even with regex support)