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

Installation didn't create file in the Vivaldi manifest directory. #1433

Closed
anterpin opened this issue Oct 18, 2022 · 4 comments · Fixed by #1434
Closed

Installation didn't create file in the Vivaldi manifest directory. #1433

anterpin opened this issue Oct 18, 2022 · 4 comments · Fixed by #1434

Comments

@anterpin
Copy link

  • OS Version: Linux manjaro 5.10.141-1-MANJARO Iframe doesn't receive input #1 SMP PREEMPT Mon Sep 5 10:15:26 UTC 2022 x86_64 GNU/Linux
  • Browser Version: Vivaldi 5.5.2805.38 (Stable channel) stable (64-bit)
  • Browser Addon Version: Firenvim 0.2.13
  • Neovim Plugin Version: 0.2.13

What I tried to do

firenvim#install(0) didn't install the firenvim.json in ~/.config/vivaldi/NativeMessagingHosts directory.

@glacambre
Copy link
Owner

What is the value of $XDG_CONFIG_HOME in your shell?

@anterpin
Copy link
Author

I don't have this environment variable set.
But I have run the installation with google-chrome installed about two years ago, and the extension in chrome is working correctly. (I copied firename.json from the google-chrome folder to the Vivaldi folder, and it started to work)

@glacambre
Copy link
Owner

I don't have this environment variable set.

Okay, that's probably the reason why Vivaldi isn't being detected. I'll update Firenvim to work around such problems.

I copied firename.json from the google-chrome folder to the Vivaldi folder, and it started to work

That's surprising to hear, I've had reports that Vivaldi used Chrome's native messaging host directory in the past. Something probably changed. Thanks for the report.

@glacambre
Copy link
Owner

Could you update your firenvim neovim plugin, remove any firenvim.json in ~/.confiig (can easily be done with find ~/.config -iname firenvim.json -delete) and then run firenvim#install(0) again and see if the firenvim.json has been created where it's expected?

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 a pull request may close this issue.

2 participants