Fork me on GitHub
#vim
<
2019-06-03
>
Hukka09:06:44

@dominicm Not sure at what level the ugens in overtone work, but I guess they could go as far as generating every value at 48kHz for as long as the sample plays

Hukka09:06:36

The pretty printed output doesn't look like that, but there's still quite a lot. Not that much that it should take multiple seconds, but I have no idea what things it goes through when introspecting objects

1
Olical12:06:23

Another small Conjure progress thing: The develop branch contains virtual text for single line eval results as well as quick doc lookup now! https://twitter.com/OliverCaldwell/status/1135526143250116608 https://github.com/Olical/conjure/pull/39 If anyone ends up sort of beta testing this beta branch of beta software then let me know how you find it. Especially let me know if you manage to break things and think you know how you did it πŸ˜„ oh it also looks up documentation and inserts it as virtual text as you type instead of just in normal mode. Now I'm going to spend the afternoon using it! (next up is declarative connections with a .conjure.edn file so you no longer need to make your own ConjureAdd mappings!)

dharrigan12:06:42

Doesn't this require neovim master to work (virtualtext?)

Olical13:06:47

Nope, virtual text has been out for a long time now. It's floating windows that aren't released as far as I know.

dharrigan13:06:57

ah, right okay. thanks!

dave12:06:55

Looks great! I can't wait til it hits master

Olical13:06:46

Will probably be tonight or tomorrow tbh, if I don't encounter any issues.

πŸŽ‰ 1
dharrigan13:06:14

I have questions....

dharrigan13:06:20

Trying out conjure πŸ™‚

dharrigan13:06:27

Direct, or in this channel?

Olical13:06:50

Maybe just thread off of here?

dharrigan13:06:15

Kewl. It's more on operational stuff than anything else

dharrigan13:06:11

Is there a way to turn off the log completely - I'm not interested in seeing the conjure log most of the time and is there a way to turn off the display of the documentation (shown as virtual text)? If I want to see documentation, I can press K and the log can pop up, but having it appear everytime is a bit annoying πŸ™‚

dharrigan13:06:43

On the github page, it lists a handful of g: options, but nothing I can see about turning things off

Olical13:06:54

So not yet to either of those because nobody had asked πŸ˜… I'm happy to add config though, just didn't want to add a bunch nobody needed really.

Olical13:06:57

YAGNI and whatnot

Olical13:06:17

What about eval virtual text for single line output?

dharrigan13:06:31

Of course, totaally undrstand, so yes please, options to disable the log and the documentation

dharrigan13:06:46

the eval virtual text of functions is a feature yes please that I've been waiting for

dharrigan13:06:57

(I didn't take to acid plugin really)

Olical13:06:08

I think I like quick doc because I have the memory of a goldfish, I like having the args there the whole time. Didn't think it'd be everyone's cup of tea

dharrigan13:06:32

No problem, a way to disable then, for those who want to see the doc when pressing K, otherwise quiet πŸ™‚

dharrigan13:06:49

perhaps enabled by default, with an option to disable.

Olical13:06:19

I'll probably let you toggle both of those features tbh, can't hurt. So you don't mind not seeing the log window ever even if it contains stderr/out? You just open it when you want?

Olical13:06:42

which is fine, I can work that out, I only just added the changes to update the log buffer without opening a window in the current develop branch

Olical13:06:46

So now it's doable

dharrigan13:06:07

Put it like this, at the moment I'm used to fireplace. When I eval a form, I have it mapped to nmap <silent> <Leader>e :Eval<CR>

dharrigan13:06:09

notice the silent

dharrigan13:06:22

I don't want anythig to appear, for I have confidence that it will eval

Olical13:06:26

Yup, so you want no output unless you ask.

dharrigan13:06:34

if there's a stderr, then yes, do display what is the problem

dharrigan13:06:56

but for normal-day-to-day evals, I trust that the eval will work, so I don't need to be told it worked.

Olical13:06:00

:thinking_face: I think maybe the current develop branch will almost be what you want then (minus the quick doc)

Olical13:06:09

Normal evals should no longer open the log buffer

Olical13:06:20

They appear as virtual text unless they're big, then it opens the log

πŸ‘ 1
dharrigan13:06:24

basically, I take the view that your editor (ide) should be as quiet as poossible, and only flag errors/exceptions.

dharrigan13:06:48

Perhaps you need a #conjure channel

dharrigan13:06:02

for keeping this in a thread is annoying (I'm not a big fan of threads)

Olical13:06:36

Yeah me neither.

dharrigan13:06:43

start a channel πŸ™‚

Olical13:06:49

See #conjure for future stuff πŸ˜„ should stop me polluting #vim as much! (sorry for the noise!)

dharrigan13:06:39

I think annoucements of updates to the plugin, or calls for testers are still okay πŸ™‚ (or anything really), after all it's directly in the set of ...`for discussion on all things (neo)vim` πŸ™‚

dharrigan13:06:53

but having a separate channel is good, for more indepth questions/answers/discussion πŸ™‚

πŸ‘ 1
dominicm17:06:54

@olical I for one welcome you in #vim (over #conjure even). As a fireplace user I enjoy the updates, and we're too small a group to be splintering into even smaller ones.

Olical17:06:18

I'll still post things here, just kinda moving the deep discussions about random settings and things to its own channel. I agree that vimmers need to band together

Olical17:06:37

I just felt bad about using this channel as my personal feedback loop πŸ˜…

dominicm17:06:45

I like giving input on random settings to help shape it to be better for me on the future ;)

benedek17:06:53

I feel a bit out of place but still enjoying the conversation now and then ;)

markx22:06:09

We should use threads more.

benedek12:06:09

i am just not a vimer. love the avatar

mynomoto22:06:29

I never thought we would have a problem of many tools to choose for clojure on vim.

πŸ˜‚ 1
markx22:06:41

So what’s the recommended way to use refactor nrepl with vim?