Replies: 1 comment 25 replies
-
|
Dang, sorry. I know why that I'm looking into what I changed that disabled Atom. Will report back ASAP. |
Beta Was this translation helpful? Give feedback.
25 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
1.3.0-beta.6
setting up Kit on my second machine, a 2013 MacBook air running Big Sur
clean install of Kit and Atom
Atom has installed its Shell Commands
which atom in terminal gives /usr/local/bin/atom as expected
in the file ~/.kenv/.env is the line
KIT_EDITOR=/usr/local/bin/atom
the original version
KIT_EDITOR=atom
didn't work either
from the terminal, I can run
atom ~/.kenv/scripts/ascript and atom launches with ascript.js ready for editing just fine.
if I run Kit from the command line and try to edit a script, I get the following error:
getScripts is not defined
ReferenceError: getScripts is not defined
at Object.menu [as choices] (file:///Users/BikeFixe/.kit/cli/fns.js:11:9)
at async global.kitPrompt (/Users/BikeFixe/.kit/preload/mac-terminal.cjs:498:19)
at async global.arg (/Users/BikeFixe/.kit/preload/mac-terminal.cjs:544:15)
at async file:///Users/BikeFixe/.kit/cli/edit.js?uuid=4fb0bd72-daf8-4fc9-b27c-37676ed7ab1c:3:12
{ line: '///Users/BikeFixe/.kit/cli/fns.js', col: '11' }
Beta Was this translation helpful? Give feedback.
All reactions