This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-30
Channels
- # 100-days-of-code (2)
- # announcements (2)
- # beginners (8)
- # boot (6)
- # calva (52)
- # cider (6)
- # cljs-dev (11)
- # cljsrn (3)
- # clojure (58)
- # clojure-austin (2)
- # clojure-russia (6)
- # clojure-spec (23)
- # clojure-uk (12)
- # clojurescript (29)
- # datomic (10)
- # emacs (1)
- # figwheel (2)
- # figwheel-main (2)
- # fulcro (3)
- # luminus (1)
- # off-topic (38)
- # re-frame (21)
- # ring-swagger (1)
- # robots (1)
- # shadow-cljs (65)
- # spacemacs (3)
- # tools-deps (16)
@d4hines it sounds like you only have joker defined in your path for interactive shells, i.e. when you run a terminal application. It is recommended to set PATH in shell configuration files that are sourced unconditionally (i.e. when run from the Mac OSX GUI launcher), such as .profile
, .bash_profile
or .zshenv
.
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
Alternatively you could source the configuration for interactive shells, .bashrc
or .zshrc
from .profile
(or .bash_profile
, .zshenv
) so you always get the same PATH regardless of how you run your application.
# if running bash and .bashrc file exists, then read in the values
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi
When setting environment variables in .profile
you will need to at least logout/login to the operating system (or restart) before those variables are picked up.
If joker is on the exec-path
when Emacs has started and its still not working, then that is a problem. I would
- check joker file is executable, eg. chmod a+x joker
- delete the flycheck
and flycheck-joker
packages from ~/.emacs.d/elpa/<emacs-version>/<spacemacs-branch>/
and restart Emacs. Then Spacemacs will download the package again (sometimes a package can get corrupted when downloading)
- update Spacemacs (I assume you are running develop
, if not then consider using develop
, as master
is a long way behind)
- update the packages using the Update Packages link on the Spacemacs home page and restart Spacemacs, SPC q r
(and maybe restart a second time if there are more than a couple of package updates just to make sure).