config file not used with stdin
See original GitHub issueVim users that are using neoformat for prettier integration use the --stdin
option which causes the config not to be picked up.
When using stdin filePath
is the working directory here making fileDir
one level up from where it needs to be.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
sed: -i may not be used with stdin on Mac OS X - Stack Overflow
The problem is that Mac OS X uses the BSD version of sed , which treats the -i option slightly differently. The GNU...
Read more >Why ssh immediately disconnects when using -F /dev/stdin ...
I've tried forcing the pseudo-terminal allocation with no success. I'm aware the following two-command syntax works as expected: vagrant ssh- ...
Read more >How do I get Urchin to read a webserver log from standard ...
Important Note: You cannot run Urchin profiles that are configured with a "stdin" log source to run via the Urchin Scheduler, since the...
Read more >docker config create - Docker Documentation
Creates a config using standard input or from a file for the config content. For detailed information about using configs, refer to store...
Read more >Configuration - Gitlint - Joris Roovers
Generate a default .gitlint config file by running: ... When not using the --staged flag while linting a commit message via stdin or...
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
I just shipped 1.6.1 that contains this fix! Thanks for reporting it!
D’oh, that would do it, too. Forgot that cosmiconfig handles files perfectly well.