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

question about evaluation coming from lisp/slime #362

Open
Dapuva76 opened this issue Feb 28, 2019 · 1 comment
Open

question about evaluation coming from lisp/slime #362

Dapuva76 opened this issue Feb 28, 2019 · 1 comment

Comments

@Dapuva76
Copy link

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?

@Dapuva76
Copy link
Author

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!

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

No branches or pull requests

1 participant