Fork me on GitHub
#conjure
<
2020-07-27
>
Aron13:07:40

Is there some way to change the font size just in the hud? or introduce wrapping somehow? the first ~10 words are rarely enough for me to understand what's going on, clojure(script) errors are often very much written in a style which combines full information with full obscurity, even googling them fully doesn't always yield results, so having only part of it and then going for a hunt in the logs if I don't see it slows me down even more than my own newbishness.

Olical16:07:56

I'm afraid not, no, vim has no concept whatsoever of font sizes. This is entirely down to your terminal or GUI. I highly doubt any of the GUI frontends let you do this either although I've never checked

Olical16:07:43

You could set let g:conjure#log#hud#width = 1 maybe, that'd use the full width of your editor for the HUD which might help a little?

Olical16:07:53

I tend to just open up the log in a tab quickly if there's a long line

Olical16:07:57

Or in a horizontal split

Olical16:07:37

But yeah, I agree that lots of things fly off screen, it's not really the norm though, so the norm has been optimised for which is things that fit within ~80-100 characters (pretty printed data)

Olical16:07:22

I could maybe add some text wrapping but that'll break all sorts of formatting which would suck. Especially if you're printing ASCII tables or something to stdout, I want to preserve your output exactly as it is.,

uwo17:07:43

Is there a hook for processing errors planned? That would allow the user to print exceptions how they like. haha, am i asking the same question again šŸ˜„ do we just override some nrepl middleware?

uwo17:07:38

at the moment I'd really like to see the ex-data printed, if it exists -- for instance

Olical17:07:51

Hooks through custom autocmds are on my radar

Olical17:07:56

Output middleware... not so much

Olical17:07:10

I think if nREPL can do it, I'd lean on that

Olical17:07:31

But I'm being pulled in 100 different directions today so I just wanted to reply but there's other points to be made here!

uwo17:07:01

sorry to pile on! your project is just so kick-ass!

Olical17:07:16

Oh no not at all! It's a good question and I wanted to give it some kind of response just in case I forget to do so

Olical17:07:32

I'm really hoping there's something that can be done in Clojure / nREPL land to make them pretty

Olical17:07:36

Maybe even middleware :thinking_face:

Olical17:07:03

Because I don't want to tackle getting that right atm, formatting errors without missing key info etc is HARD and I'd rather someone else did a project that specialised in that, if that makes sense?

šŸ’Æ 3
Olical17:07:15

Otherwise I end up being a jack of all trades, master of none

uwo19:07:23

šŸ’Æ

Aron20:07:27

I almost never have anything anywhere pretty printed, much less in the HUD, it's always just text. The one exception I remember seeing formatting is when I connect to the app. Otherwise it's just logs and text without any formatting. Or error messages from the logs. Very much not formatted, just in the middle of everything

penryu20:07:42

Hi all! I've used conjure v2 for months happily, but I bumped the tag from v2.1.2 to v4.1.0 with vim-plug, and it is just showing it has having a pending update. Conjure is never loaded, regardless of the filetype (`.clj`) or presence of .nrepl-port. Even completely uninstalling and reinstalling the plugin doesn't resolve this. I feel like I'm missing something really basic.

Olical21:07:12

:thinking_face: I've never seen vim-plug give this message, have you tried rm -rfing the repo vim-plug cloned?

Olical21:07:09

You're not missing anything, if you have an nREPL port file it'll just connect the first time you open a Clojure file

penryu21:07:50

I'm also confused because none of the :Conjure... commands are available. Let me check my installation again, and have a proper nrepl session going.

Olical21:07:08

:thinking_face: you don't need the install compile script now either

Olical21:07:11

That might be causing you issues!

Olical21:07:14

And preventing the update

Olical21:07:31

It's all compiled for you, no JVM involved at all, it's just Lua in the repo

penryu21:07:08

verified that :PlugClean is correctly removing the entire git clone. and I've removed the do: 'bin/compile' bit too.

Olical21:07:25

I'd imagine that was the culprit

penryu21:07:33

sorry, I meant, I did that when I bumped to v4.1.0. I haven't had it the tag was bumped. I was gonna try re-adding it until you said it's no longer required.

penryu21:07:22

I'm still not completely convinced I didn't mess something up in my install. I'll run through the paces again, aware of the major prepl->nrepl change. Maybe that'll help.

Olical21:07:09

Oh! I see!

Olical21:07:17

And sorry to drop prepl->nrepl onyou

Olical21:07:22

I promise it's for the best

penryu21:07:00

Not a problem at all! I should have read the release notes before bumping 2 major versions. šŸ˜…

penryu20:07:55

I've looked at the vim-plug docs a few times, and found D to list the pending updates, but having trouble finding out how to APPLY them

penryu20:07:33

I'm starting to think the "pending" updates are just changes on master that aren't in the tag. So that leaves me with "conjure just isn't loading"

penryu21:07:38

And... now I'm questioning my own sanity... conjure only supports nrepl now? Nvm. Found the nrepl announcement in the v3 release.

Olical21:07:48

Yeah, sorry, this'll be pretty jarring since I rewrote everything to fix several fundamental flaws that were causing bugs I couldn't fix (race conditions because Conjure was a combination of VimL and Clojure in another process)

Olical21:07:15

So now everything is Lua (compiled from a lisp), runs within Neovim's process and is basically the same UX but refactored

penryu21:07:59

No worries! I remember you being concerned with some fundamental issues, and am glad the nrepl issues got ironed out.

Olical21:07:12

I'm reaaaaly sorry about having this as a potentially unpleasant surprise. I promise the new version is much better in basically every way, it'll just take a sec to get accustom.

šŸ™ 3
Olical21:07:32

There's no config to learn, every config value is just let g:conjure#..., so hopefully there's nothing to learn really

Olical21:07:34

Mappings are the same

Olical21:07:09

Everything is nREPL with optional CIDER now, but that experience is just so much better. I tried my best to make prepl work, but it was just too much duct tape for my liking in the end. Now we have shadow-cljs + full completion support šŸ˜„

šŸ‘ 3
Olical21:07:26

Also it supports multiple lisps as a core design principal šŸ™‚

šŸ˜„ 3
Olical21:07:57

I think that's all of the main things covered šŸ˜… but yeah, I just hope it's not too much of a bad surprise. I've been really busy on the project

penryu21:07:11

I'm just really glad all the multiple lisps got sorted out. looking forward to the clj+cljs

penryu21:07:24

Update: ā€¢ Yes, if I remove the tag entirely, vim-plug will pull master and after update, will show "Already up to date" ā€¢ If I use a tag, vim-plug status will just show "OK", and "pending updates" will be the commits in master downstream from the tag ā€¢ nvim is still not loading conjure at all, even after a full clean of the plug checkout. commands like :ConjureRefresh are not defined; :Con<tab> just lists 'confirm', 'const', and 'continue'

penryu21:07:00

So pending updates mystery is solved, and not the culprit. For some reason, conjure just isn't being loaded/sourced? Gonna do a verbose startup to see where it's going wrong. Entirely possible it's a problem on my side.

penryu22:07:06

@olical Yep, all me, and I'm sorry for the noise! Somewhere along the line my vim->`nvim` symlink got lost, and the built-in /usr/bin/vim has been playing doppelganger, and the has('nvim') in plugin/conjure.vim was rightly returning false. Many apologies @olical! I'll fire up :ConjureSchool and start reaping the benefits of all your work! šŸ™

šŸŽ‰ 3
penryu22:07:10

Just as a matter of curiosity, do other people do the same, and still type vim when you want neovim? Or have you retrained your fingers to type nvim?

Olical22:07:18

I use nvim and this šŸ™‚ https://asciinema.org/a/39054

penryu22:07:35

Brute force finger re-education. Nice. šŸ™‚

Olical22:07:16

I should've shocked myself each time or something šŸ˜…

Olical22:07:43

Worked eventually

Chase23:07:45

I just alias v to nvim and get real lazy with it

šŸ‘ 3
aaroncoding03:07:20

I also alias v to nvim

thanks2 3
penryu09:07:07

I settled on alias vim='echo you mean v; false', which I found out also helps when I try to tab complete filenames... because it doesn't.

šŸ‘ 3
nate22:07:07

hey @olical would you be open to re-adding in the folding of long results?

Olical07:07:27

Yep! Of course! I have it on my list still, I'll give it a little hammock time today, maybe over my first haircut since COVID-19 šŸ‘€

nate13:07:00

Awesome, thank you.