Fork me on GitHub
Anthony Khong02:10:59

On the existing buffer, same here, my expectation would be that it appends to the existing buffer and better yet if it could scroll to the bottom as well 😄


Hmm now we're getting into the realms of what I could add as configuration. Behaviour of the log/hud when a message appears and you can't see it, there could be 2-3 behaviours :thinking_face:

👍 3

Thanks @olical, it certainly makes sense now when I know it, was just hard to understand why at first. I quite like the behavior as-is (as it's appending to the existing buffer but not scrolling down). Maybe adding a message "This window was opened as the log buffer cursor was not at EOF" to the repl window could help first-timers understand why it opened


when setting flags, should we be using 'true' or v:true, or does it matter?


Vim Script didn't support booleans originally, so there is no true or false. v:true and v:false are the ones to use in viml these days but I think they map to 0 and 1 in some cases?


Use true and false in fennel


so inside of my vimrc? use 'true'?


errr. in the context of, for example, let g:conjure#client#clojure#nrepl#completion#with_context='false'


Nope that's = v:false because it's vim script


Sorry if I wasn't clear 😬


It's a confusing topic


I think you can set it to 0 too and get the same result. You don't want to use a string of false though since that's truthy


I just use 0 and 1 for flags. Didn't even know about the v:true or v:false variables


Yeah, they work fine too, I think v:true magically ends up being true in lua rather than 1 somehow too. Sometimes. It must attach some extra metadata or something?


I like using v:true and v:false over 0 and 1 just for clarity.


I think there's also a v:null but who knows what that means...