tonsky / clojure-sublimed Goto Github PK

I don't find the plugin listed when I search for sublime clojure in package control.

Am I missing it, or shouldn't it appear here? https://packagecontrol.io/search/Sublime%20Clojure

• Ctrl+I on a region
• Edit inside it
• Cmd+Z

Expected: text returns, region does not
Actual: both text and region return. Region could not be removed anymore

This might happen if you edit inside region or evaluate another region that intersects with yours. Right now we just forget about it, would be great to cancel task

Hello, I know this is not an issue of Clojure Sublimed per see, but I couldn't find any help for this anywhere else, so I'll try to get some light here.

I'm playing with Clojure Sublime + LSP, the problem is that the LSP thing on Sublime puts an annotation to show the code actions always in the right side, for example:

The result is that when I evaluate a line, it doesn't show anything on the right side. It actually does show, but it places it in a line after the LSP annotation, making it not visible... unless I hover with the mouse, like:

The question is, how can I disable the LSP annotation on the right, so I can have just the Clojure Sublime evaluation there? (I still want to use code actions, but I have a dedicated shortcut for it, I just want to get rid of the annotation on the side).

Might actually be two options: display right next to form (moves text after):

or at the end of the current line:

Will probably require reporting back form start/end positions

Hi I'm using

"color_scheme": "Monokai.sublime-color-scheme",

Clojure Sublimed

In-built Clojure

Sorry I don't have more concrete description of the problem but does this look "correct"?

edit: the file I'm looking at is a .cljc file but this obviously reframe stuff here, I've tested with .clj files too and they have the same "problem"

It appears that I've introduced a bug via #51, in erase_eval. Whenever an eval is erased, all Evals in that view are also removed from conn.evals_by_view.

Currently I see:

  ^123 x  ^[:dynamic true] x

at: https://github.com/tonsky/sublime-clojure/blob/master/syntax_test_clojure.cljc#L97

Are these supposed to pass?

Specifically, the constructs:

^123 x

and

^[:dynamic true] x

don't seem syntactically valid.

When standing inside successful evaluation, Ctrl+I should toggle between compact one-line truncated view (first) and expanded pretty-printed view (second):

Note: do not use clojure.pprint, better implement it yourself: same idea, but sans the part where it tries to fit keys/values into 80 chars

With the default Clojure syntax, go-to definition works with namespaced functions within the project. When using Clojure-Sublimed, this no longer works.

Below shows go-to definition working with default syntax on the right, not working with Clojure-Sublimed on the left, and then working in Clojure-Sublimed when the namespace is removed.

If i evaluate a file thats requires any lib, it returns a java.io.FileNotFoundException. This is the test script i'm using:

(ns clj-init.core
(:require [java-time :as t]))

(defn test-01
[]
(println (t/local-date-time)))

and this is the exception it returns:

java.io.FileNotFoundException: Could not locate java_time__init.class, java_time.clj or java_time.cljc on classpath. Please check that namespaces with dashes use underscores in the

It works just fine if i run it on lein repl or Intellij Cursive

Does someone have any ideia on how can i fix it?

If you are standing between two top forms and there’s one on the same line left of you, eval it? E.g. this:

should eval (range)

Time reported now is measured in python client, which includes overhead for creating session, client-server communication and serialization. Most times you are interested in your code performance, though.

This is way too off:

Right now we compare content of regions. Feels like comparing interval boundaries might be more efficient

" Autocomplete. Static analysis is much simpler and much more reliable than requiring an always-live connection to the working app."

What sublime package provides autocomplete for Clojure. Have been searching for something and have not been able to find anything.

Open to suggestions/recommendations.

I was about to do the install and noticed there weren't uninstall instructions.

We clone the session on each eval, but never close the created sessions. This means that the total number of sessions in the nREPL server continues to rise. This is unnecessary inefficiency.

Related to #20.

Right now on each eval we clone session. This enables parallel evaluation, but disables modifying thread-local vars (set! etc).

Some people might not like it, so might be a good idea to being able to turn it off

Hey Nikita!

I'm rolling into Clojure and setting up dev env, and I've heard in your talk on Clojure/north in Toronto the story about this package. That's why I've installed it. But SublimeREPL doesn't work with it by default. It runs lein repl in background, opens new tab for *REPL* [clojure], however when I send any selected code there it says it can't find a REPL for clojurec.

I've fixed this by defining user configs for Sublime REPL inside ~/Library/Application Support/Sublime Text 3/Packages/User/SublimeREPL/config/Clojure. I've added Main.sublime-menu:

[
     {
        "id": "tools",
        "children":
        [{
            "caption": "SublimeREPL",
            "mnemonic": "R",
            "id": "SublimeREPL",
            "children":
            [
                {"caption": "Clojure",
                 "id": "Clojure",
                 "children":[
                    {"command": "repl_open", 
                     "caption": "ClojureC",
                     "id": "repl_clojurec",
                     "args": {
                        "type": "subprocess",
                        "encoding": "utf8",
                        "cmd": {"windows": ["lein.bat", "repl"],
                                "linux": ["lein", "repl"],
                                "osx":  ["lein", "repl"]},
                        "soft_quit": "\n(. System exit 0)\n",
                        "cwd": {"windows":"c:/Clojure",
                                "linux": "$file_path",
                                "osx": "$file_path"},
                        "syntax": "Packages/sublime-clojure/ClojureC.tmLanguage",
                        "external_id": "clojurec",
                        "extend_env": {"INSIDE_EMACS": "1"}
                        }
                    }]
                }
            ]   
        }]
    }
]

And Default.sublime-commands:

[
    {
        "caption": "SublimeREPL: ClojureC",
        "command": "run_existing_window_command", "args":
        {
            "id": "repl_clojurec",
            "file": "config/Clojure/Main.sublime-menu"
        }
    },
]

They defines new REPL as clojurec and also applies sublime-clojure to it.

Now REPL for ClojureC is available in menu:

And I've checked the syntax highlighting by testing it with the one of the strings from your testing files. Before:

Now:

And of course everything works properly with sending selected code into REPL.

I'm not sure whether it's a big deal or not, because I haven't had any Clojure experience yet, but when I googled plugins for REPL I got an impression that this one is the most popular for this purpose. So maybe you need to improve the docs by adding Troubleshooting section.

I enabled the following keystroke, and while it works, the port auto-detection logic doesn't seem to fire so I have to manually type the port into the little command window that pops up. Is it possible to fire the command from a keystroke, but have it auto-detect the port number, as happens when this command is run manually via the command palette?

In my user keymap file:

    {"keys": ["ctrl+j"],
     "command": "sublime_clojure_connect"},

E.g. if you want to call (clojure.tools.namespace.repl/reload) you use this command and pass it as a string

I'm attempting to connect to a server hosted by Shadow-CLJS:

{:deps        {:aliases [:common]}
 :nrepl       {:port       5555
               :middleware []}
 …}

There are no error messages in the log, as I can see.

Parsing might be done much more efficiently on Clojure side, but it will require sending full file for each command. Worth it?

• Ctrl+I on any symbol
• Edit inside region

Expected: info panel is removed
Actual: info panel stays

Keep a dict for evals only in particular view

Reduces network latency and change of errors

• What CLJS REPLs exist
• What needs changing

When standing on a symbol, run a command that will require it as a namespace. Seems something like (clojure.pprint/pprint :abc) doesn’t work simply because clojure.pprint has not been required

Hi, I see that this package contains a greatly improved Clojure syntax. Will this ever be added into the default packages repo, https://github.com/sublimehq/Packages? Users of Sublime Text can make pull requests, and eventually the changes get added to ST's beta/stable versions.

E.g. start REPL and try to eval plus form in a file like this:

(ns abc)

(+ 1 2)

Command send to nREPL will have {"ns": "abc"}, but abc has not been evaluated yet so it doesn’t exist. This causes an error, even though code could be evaluated just fine in user namespace. Or, alternatively, abc might be required first, before evaluation.

I'm new to clojure, sorry if this is a misguided question.

The basic "Clojure REPL: Evaluate" command seems to try to evaluate only the character at my cursor, not the top most form. Any idea what is wrong with my setup, or if this is some kind of bug?

With my cursor between ( and + I get this result:

With the entire line selected, I get 2

Stuff like double whitespace, line breaks, etc

Check if anyone is already doing something like this? Cljdoc?

I don't know if this is the result of using alabaster, but given issues here and there, it may be coming from how Clojure Sublimed treats parentheses.

When using Clojure's character literal, it's displayed correctly for most characters. For lists, however, it seems to treat the parenthesis like a character and part of the form. For example, the following code prints Klay (#3), but highlights the character literal as part of the str form.

(def name "Klay")
(def lb-pos 3)
(println (str name " (#" lb-pos \)))