-
Notifications
You must be signed in to change notification settings - Fork 25
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
Compilation mode in REPL buffer #45
Comments
Your approach seems fine overall, though it should be moved out of a use-package hook when we merge it into Snail. The crash must have come from vterm. Do you think you can reproduce it well enough to open a ticket there? |
I modified the hook into
and it now works without crashing. I am not sure I retrieved the cached basedir correctly earlier, so that was probably the reason for the (SIGSEGV) crash. It should work without problems if implemented in Snail 🙂 |
Looks good, thanks! |
@martinbiel: Looking to merge this suggestion. I can't get clickable links in vterm buffers at all. Can you confirm that it worked intermittently for you? I'm wondering if vterm behavior with regard to allowing links changed between the time you opened this ticket and now. |
@martinbiel: Take a look at this branch which essentially copies your hook: https://github.com/gcv/julia-snail/tree/compilation-mode-in-repl It doesn't seem to make the REPL clickable for me. |
This would be a very useful feature. Unfortunately, it doesn't seem to be able to find the path of the currently edited file for some reason. |
Could an option be added to enable the functionality implemented in #12 also to the snail REPL buffer? I like the ability to follow error links when testing my packages interactively.
I tried to just manually enable this in a hacky hook:
which appeared to enable the feature I am asking for. Error links became clickable and correctly pointed to my package code. However, Emacs crashed at one point when clicking one of the error links, so this temporary solution is not the way to go 🙂
The text was updated successfully, but these errors were encountered: