-
-
Notifications
You must be signed in to change notification settings - Fork 44
Fix for #79 #82
New issue
Have a question about this project? No Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “No 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? No Sign in to your account
Fix for #79 #82
Conversation
55bac77
to
18a4c0f
Compare
README.md
Outdated
@@ -99,6 +99,26 @@ point. You can, however, change this behaviour by invoking such | |||
commands with a prefix argument. For instance: `C-u C-c C-v` will ask | |||
for the symbol you want to show the docstring for. | |||
|
|||
#### *WARNING* - Standard REPLs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the title of this section is extremely misleading.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably this should be in some caveats or faq section of the readme.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or in configuration.
README.md
Outdated
|
||
Note that if you decide _NOT_ to use the socket repl, it is highly recommended | ||
you disable output coloring and/or readline facilities: `inf-clojure` does not | ||
filter out ASCII escape characters at the moment and will not behave correctly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why filter them out? Why not simply apply them the same way we do in CIDER? It's quite trivial.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We apply them visually, but the regex match is failing every time because of those. A solution is for our regexes to skip the ascii escape codes. Do you have a link for cider? If there is an alternative I am all for it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue of speaking with the terminal is a big one. Comint hides some of the complexity but cannot eliminate it. Things like embedded readline
and colors all change behaviors and I am so far from being an expert that I was even wondering whether console support should be dropped completely at some point (maybe by adopting another Emacs socket-only package). Sooner or later...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...I guess it will happen. Cider does not handle this because of nRepl in between. In any case I can try to escape them, I saw it in some other plugin ...We'll see about the result.
Checked out this pull requests and this is what I'm getting
and as I type
|
Is this on Lumo? It means it recognizes it as Clojure Repl. Thanks for testing, very helpful.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
On lumo yes (can be confirmed by looking at the stacktrace). No problem! |
@hlolli how do you launch |
I did it like this
|
@hlolli sorry about that, just double checking 😄 I can reproduce. |
You error above still happens when the first thing you do is |
The eldoc error in Lumo is related to a |
ee72d95
to
a152514
Compare
Split this one in two (or more) while discovering and solving issues. |
@bbatsov so we are not merging this one? Why? |
My bad. Misinterpreted the comment. |
Ok cool lemme know 😀 |
Replace this placeholder text with a summary of the changes in your PR.
The more detailed you are, the better.
Before submitting the PR make sure the following things have been done (and denote this
by checking the relevant checkboxes):
M-x checkdoc
warningsThanks!