It definitely happens in my mixed java/clojure codebase. It doesn't happen when I try to reproduce it 😛. It also doesn't happen in the same code-base when I start with mvn clojure:repl.

any ideas why killing an inf-clojure buffer wouldn’t kill the corresponding repl process?

reefersleep: I can't help with the eval of a form from point in arbitrary position anywhere in said form, but you cane activate picture-mode to move point to empty rows and columns that have no characters, including whitespace

oh, erm, @reefersleep *

@redbeardymcgee: I found out the first part: cider-eval-defun-at-point. Thank you for the tip about picture-mode! Emacs seems to be bursting with functionality

does that eval the top-level fn?

the top-level sexp

Of course, sexp

yes it does :)

Yeah I went source spelunking on github, but you can't follow symbols there so i got lazy and quit

why i'm always curious about implementation details I'll never understand

@redbeardymcgee: because they are so much fun

@jcsims: sounds unlikely - comint processes are usually killed with the buffer they are attached to

@seancorfield: there’s nothing special about the browser

just invoke this command and should be good to go

the command is autoloaded, though

and I’m guessing Emacs Live doesn’t generate the autoload stubs

which is done automatically when using package.el

you might have require the ns browser manually before being able to use it

or just add the autoload directive manually in your config

a lot of “non-essentials” commands are auto-loaded to speed up the initial CIDER load-time

Out of interest roughly when is the release of 0.10.0 expected?

rickmoynihan: Likely before the conj

if we can kill the remaining bugs

Cool

worst case scenario - before ClojureX

(I hope I’ll do a presentation about CIDER 0.10 there)

if you take a look at the recent development - it’s conference-driven

I’ve made a push to release something on the previous conj

and then on EuroClojure

if people were inviting me to talk about CIDER all the time it would have way more releases

the conj is a good target for one more reason - make sure everything works with Clojure 1.8

CIDER 0.10 will likely be the final release supporting Clojure 1.5 & 1.6

and after it we might bump the requirements to 1.7

to be able to live in the brave new world of feature expressions

@bozhidar: have you submitted your talk synopsis yet?

To ClojureX? Yes.

Cool. I’ll double check that we got it.

great

bozhidar: yeah it’s strange - the lein process seems to hang around afterwards, and every time I kill the buffer, then start inf-clojure there’s another process. It might just be the application itself that’s causing issues. I might investigate later, but I think I’m actually moving back to Cider because I miss a few things

though I really like having M-. working without connecting to a repl

has anyone looked at a fallback to using tags if you’re not connected to a repl?

it has been suggested a few times and it’s certainly doable

my main issue with tags is keeping them in sync with the code

projectile was really helpful for me in that aspect, but tags alone wasn’t nearly as good as using the connected repl

I’ll take a look at what’s needed to add a tags fallback, because I know I would use it

well, it will as simple as adding one check to cider-find-var regarding the presence of a connection

Cider has plenty of advantages over inf-clojure - in general I believe that inf-clojure is a good way to get your feet wet without being overwhelmed

but when you want to do some serious work, cider would provide more tactical support for you

There's a namespace cache that contains pretty much all the information you need for M-.

Someone on the clojure listsuggested storing this cache in a file so that it would work even without a repl

The advantage over a TAGS file is that you wouldn't need to run a secondary executable to update it. The disadvantage is that it only updates when you connect to a REPL

anyone using boot+cider find that cider-find-var takes you to a file in ~/.boot/cache/tmp?

@malabarba: interesting idea (which can still be combined with a fallback to tags)

@jstokes: you can file a bug for this I guess (especially if it happens all the time)

You were right @bozhidar https://clojurians.slack.com/archives/cider/p1444814772000200 although now I get Invalid function: (cider-doc-lookup var) when I press enter next to any symbol in the namespace browser. I guess something else needs to be required…?

just file an issue on github and I’ll take a look at this later

we’ve done a ton of internal changes in 0.10

and unfortunately our automated tests are few, so regressions are quite common

and s produces Symbol’s function definition is void: when-let — maybe CIDER is relying on a package that Emacs Live does load?

seems you’re having some issues with dash.el

I’m guessing requiring it manually should fix your problem

You think this is more an Emacs Live issue than CIDER?

if it’s a missing library it’s certainly an Emacs Live issue

I’m not sure how it handles package deps

that’s why I encourage people to just use package.el, as it’s the only standard package management we’ve got

I’ll open an issue in Emacs Live’s GitHub for now...

roger that

ping me there if you need my input at some point

Thanks. I tagged you in https://github.com/overtone/emacs-live/issues/220

I love Emacs Live as an overall package but its quirky handling of packages is very frustrating at times!

btw, if somebody has a moment to drop by Clojure’s JIRA, please upvote http://dev.clojure.org/jira/browse/CLJ-706

we deserve some deprecation mechanism and this would definitely be useful in CIDER (it could treat deprecated stuff specially)

hey, I’d like to make an emacs shortcut which would evaluate some clojure code witin connected repl. what the magic cider function should I use?

michal: you have many options, check here: https://github.com/clojure-emacs/cider#keyboard-shortcuts

@bozhidar: I agree that cider has much more over inf-clojure, hence why I’m coming back to it The cache that @malabarba mentioned sounds promising for my use case - I connect to a repl in the project I’m working on all the time, but occasionally I want to check something in a different project that updates infrequently