You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm new to programming in general, and so far I've been coding Lisp using slime in emacs. I'm used to evaluating (slime-eval-defun) a variable like (setq a 3), and then using that variable in every function I want to write (in the same file). So not evaluate the whole buffer, but just the line or function individually.
But with alchemist, if I evaluate (alchemist-eval-current-line) a line with a definition like n = 3, and then evaluate another line referencing n, it says that the variable is not set. Is there a way to mimic slime's behaviour, where I can reference a variable if I already evaluated it?
The text was updated successfully, but these errors were encountered:
You seem to have fixed this? There's been a renaming/reworking of functions, aka (alchemist-eval-current-line) is now (alchemist-iex-send-current-line) if I'm not wrong. Weird coincidence or maybe someone read this, thanks for the change!
I'm new to programming in general, and so far I've been coding Lisp using slime in emacs. I'm used to evaluating (slime-eval-defun) a variable like (setq a 3), and then using that variable in every function I want to write (in the same file). So not evaluate the whole buffer, but just the line or function individually.
But with alchemist, if I evaluate (alchemist-eval-current-line) a line with a definition like n = 3, and then evaluate another line referencing n, it says that the variable is not set. Is there a way to mimic slime's behaviour, where I can reference a variable if I already evaluated it?
The text was updated successfully, but these errors were encountered: