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

zsh causing exec-path-from-shell :init: Expected printf output from shell (still) #8873

Closed
zeroasterisk opened this issue May 10, 2017 · 5 comments
Labels
- Bug tracker - Loading stale marked as a stale issue/pr (usually by a bot)

Comments

@zeroasterisk
Copy link

Description :octocat:

re: exec-path-from-shell :init: Expected printf output from shell - #4755

I'm also getting this problem - and so far, none of the suggestions are helping. I am new to spacemacs.

Reproduction guide 🪲

  • Start Emacs

Observed behaviour: 👀 💔

Error (use-package): exec-path-from-shell :init: Expected printf output from shell, but got: "__RESULT/Users/alan/.nvm/versions/node/v6.7.0/bin:/Users/alan/.rvm/gems/ruby-2.2.2/bin:/..."

Expected behaviour: ❤️ 😄
no errors on startup

System Info 💻

  • OS: darwin
  • Emacs: 25.1.1
  • Spacemacs: 0.200.9
  • Spacemacs branch: master (rev. 8e1af14)
  • Graphic display: t
  • Distribution: spacemacs
  • Editing style: vim
  • Completion: helm
  • Layers:
(helm emacs-lisp)
  • System configuration features: JPEG RSVG NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES
@ublubu
Copy link

ublubu commented Jul 3, 2017

My error looks like this:

Error (use-package): exec-path-from-shell :init: Expected printf output from shell, but got: "__RESULT�2945ad54c3e6b37c561ff49f058c4cc8�/home/kynan/workspace/go/src/k8s.io/kubernetes:/home/kynan/go/bin:/home/kynan/workspace/go/bin:/home/kynan/workspace/go/src/k8s.io/kubernetes/third_party/etcd:/home/kynan/bin:/home/kynan/.local/bin:/home/kynan/workspace/go/src/k8s.io/kubernetes:/home/kynan/go/bin:/home/kynan/workspace/go/bin:/home/kynan/workspace/go/src/k8s.io/kubernetes/third_party/etcd:/home/kynan/bin:/home/kynan/.local/bin:/home/kynan/workspace/gcloud/google-cloud-sdk/bin:/home/kynan/workspace/go/src/k8s.io/kubernetes:/home/kynan/go/bin:/home/kynan/workspace/go/bin:/home/kynan/workspace/go/src/k8s.io/kubernetes/third_party/etcd:/home/kynan/bin:/home/kynan/.local/bin:/home/kynan/bin:/home/kynan/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin:/home/kynan/Android/Sdk/tools:/home/kynan/Android/Sdk/platform-tools:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin�__RESULT"

I'm on Ubuntu 16.04 with Emacs 25.1.1, Spacemacs 200.9, and these layers:

helm
auto-completion
emacs-lisp
syntax-checking
go
haskell
html
javascript
markdown
yaml

@RomanKapitonov
Copy link

Getting the same error. I've been trying to find the reason and it seems that the following code from .zshrc is broken:

export NVM_DIR=~/.nvm
source $(brew --prefix nvm)/nvm.sh

Removing these lines eliminates the warning. But then another issue appears:
PATH is not being extended with nvm location and hence tern binary is not being found for the javascript layer. tern binary not found spacemacs warning appears in the warnings buffer.

@RomanKapitonov
Copy link

An interesting observation:

If to replace

export NVM_DIR=~/.nvm
source $(brew --prefix nvm)/nvm.sh

with

export NVM_DIR=~"$HOME/.nvm"
source $(brew --prefix nvm)/nvm.sh

the warning message disappears. I'm not sure how it's different from the above path, but that seems to make the warning disappear.

@ghost
Copy link

ghost commented Sep 8, 2017

@RomanKapitonov Yes...I change my code from

source ~/.oh-my-zsh/plugins/git/git.plugin.zsh

to

source $HOME/.oh-my-zsh/plugins/git/git.plugin.zsh

Then the error disappear....

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- Bug tracker - Loading stale marked as a stale issue/pr (usually by a bot)
Projects
None yet
Development

No branches or pull requests

4 participants