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

Neomake integration with bare files and STACK_YAML #71

Open
parsonsmatt opened this issue Jul 21, 2017 · 6 comments
Open

Neomake integration with bare files and STACK_YAML #71

parsonsmatt opened this issue Jul 21, 2017 · 6 comments

Comments

@parsonsmatt
Copy link
Owner

Copied from #67 (thanks @tsoernes!):

When using STACK_YAML environment variable to specify a stack.yaml file, the neomake integration fails with following message:

Error detected while processing function <SNR>51_on_stdout[26]..<SNR>51_new_response[22]..intero#maker#write_update:
line    3:
E482: Can't open file /tmp/nvimWuC10t/3 for writing: no such file or directory
@tsoernes
Copy link

I don't use a STACK_YAML env var (echo $STACK_YAML doesn't print anything and I haven't set it myself), I assume stack just defaults to the global yaml file when run as a bare file.

@parsonsmatt
Copy link
Owner Author

That use case is working for me, oddly enough.

@tsoernes
Copy link

I'm not getting this issue on my other system using the exact same init.vim, editing same file on same operating system with same neovim version so I'm not getting any wiser. The systems are configured to be as identical as possible.

@rdnetto
Copy link
Collaborator

rdnetto commented Jul 22, 2017

The weird thing about this is that we switched to using a tempfile instead of .stack-work specifically because of Stack scripts. Looking at the output of tempname() on the affected system could be interesting - I suspect the /tmp/nvimWuC10t directory doesn't exist.

@tsoernes
Copy link

tsoernes commented Jul 22, 2017

My previous analysis of this issue was incorrect.

The error happens when the line

#!/usr/bin/env stack

is either added then :wq or removed then :wq.

In either case you won't get it the second time the file is opened then :wq (without editing anything) because in case 1 (line is present) intero won't start the second time around and in case 2 (line not present) intero seem to work correctly on bare files as @rdnetto mentioned.

When replicating these steps I also get this error on my other system.

@jez
Copy link
Collaborator

jez commented Jul 23, 2017 via email

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

No branches or pull requests

4 participants