thanks for submitting :) if anyone has any questions, lmk!
HN user
tjdevries
I think "best-effort" would be a good tagline for emacs
glad you are enjoying it :)
Oh cool, this is my video :)
If you have any questions, I'm happy to answer them. It's been a fun and interesting project.
I'm not sure what you don't like? Sorry, must just be missing your point.
<3 glad to hear people are enjoying this combo
My pleasure :) I have tons of fun doing it!
Awesome
One of us! One of us! One of us! ;)
Ok, got some responses from him (I don't know what any of these things mean haha):
vimtex works perfectly on neovim (in fact, the main developer uses neovim) and is very well documented
texlab (the latex lsp server) also does build and forward search (although there's a small bug at the moment)
Oh, and backward search needs neovim-remote (\o/ mhinz); just use nvr --remote +"%line" "%file" as backward search command
https://github.com/lervag/vimtex/blob/5d1335d095d11f48a6744f...
(the vimtex dev uses Zathura, so that may be an alternative viewer to look into)
I have to phone a friend in this one. I don't know much about latex in neovim these days.
I pinged a buddy of mine to hopefully be able to respond here though!
Rolling release is kind of hard. We want to make sure that we keep our promises that we've set forth in `:help api-contract` and other expectations about semver. We think this is very beneficial for the plugin writing community. It's also hard because sometimes we merge something into master, before a release, and then recognize that a change to an API, an extension, etc. may be necessary for a feature to truly be great. Rolling release can make some of these things very hard.
However, we're hoping to release more often now to prevent this kind of situation.
I'm not 100% the person to talk to about releases, I primarily just try and write code to make Lua more fun to use :)
Side Note: You can install the HEAD of neovim easily with brew. `brew install neovim --HEAD` I think will do that for you. I'm not sure if that's what you mean by source/HEAD packages or not (I have no idea anything about Mac).
Wow, this is such an incredibly kind message! I had a really big smile on my face reading it. :)
I really appreciate it and hope I can live up to the standard I'm trying to set. Hope you have a really great day!
Hi, tjdevries here.
Happy to try and answer any questions about the podcast or neovim generally :)
Hi!
Let me know if there is anyone/anything you'd like to see on Friday! Looking forward to releasing nvim 0.5 :)
Thanks,
TJ
That's great to hear :) As you write more plugins, make sure to submit ideas to Neovim core about how to make Lua even easier and/or more integrated!
Yup!
We want to create interfaces to make this simpler for people to use.
One example is here: https://github.com/mjlbach/neovim-ui which is just in a separate repo to make it easier to work on rather than one huge PR.
This is an extension of the ideas that I started in https://github.com/nvim-lua/popup.nvim and a few other places.
The idea would to be to create interfaces that users, plugins and/or GUIs could override to provide a unified experience while still being customizable for users.
(and as a self plug, I think we have a lot of interesting ideas in telescope.nvim about UI that could be upstreamed over time)
I'll ignore the other parts I disagree with in this post, since it's cool to have different views but I just wanted to post that it may someday be possible to run vim9script plugins in neovim :)
I'm working on a project that might allow at least 90% or higher compat here: https://github.com/tjdevries/vim9jit
Of course, vim9script isn't complete yet, so the spec isn't all the way done, but it may someday be possible to run them in neovim.
Additionally, if someone actually just wanted to port all the C code to run or has some other way to make vim9script run, neovim is not opposed to making that happen.
You can do something like this:
``` " Does: " For wrapped lines, does gj/gk " For large jumps, adds a spot on the jump list function! tj#jump_direction(letter) let jump_count = v:count
if jump_count == 0
call execute(printf('normal! g%s', a:letter))
return
endif
if jump_count > 5
call execute("normal! m'")
endif
call execute(printf('normal! %d%s', jump_count, a:letter))
endfunction
```and map j and k to this
My pleasure :)
https://twitter.com/TeejDeVries/status/1396881477263036417 ;)
(I hope you are in on the meme, otherwise I am sorry for posting our "inside joke" response)
unacceptable ;)
Wow thanks!
btw I'm tj :]
It always feels really nice knowing that people are getting excited by your work. Thanks for the shoutout!
(I'm tjdevries)
Happy to answer any nvim questions while I'm here.
Great <3 Hope you enjoy it! It was a lot of fun making it
Thanks :) Hope you enjoy it!
No problem :)
Yeah (and I've said this elsewhere) I think people should use the tools that make them productive! So if that's fzf (or something else) then keep using that.
I honestly just made telescope for fun on stream to start with to explore some ideas about fuzzy finding that I thought would be fun. It just happened to be that people liked it and it grew.
We have a pretty active gitter group & people hanging out in the issue tracker, so feel free to ask questions there!
I would say it's more integrated but also more flexible (only within neovim though. I don't have any good solution to run telescope from command line at this moment).
Each aspect of telescope can be customized (so you can change the sorting algorithm, the previewer, the search text, the format of the UI, etc). It was designed for vimmers to spend endless hours configuring (which is my favorite pasttime) ;)
The speed difference should be less now (for most of the pickers, I haven't fixed all of them yet), but fzf is (and probably always will be) faster than telescope.
It's a bit difficult to explain in short amounts, but I will hopefully put together a youtube series and/or some writing where I can explain it more succinctly. I usually feel like I have too much to say when it comes to telescope.
Ultimately though, I think if fzf is working well for you then I probably would not switch. fzf is really awesome!
Shortest "killer feature" is probably the re-use of native vim buffers inside of telescope. So one cool thing is when it does a preview, it will show you the literal buffer (so it will have exactly the same colors, syntax highlighting, etc.) wherever possible.
Longer answer is I think it's quite cool to be able to not have to serialize/deserialize everything within telescope, so you can pass around objects (a.k.a. lua tables) that have function references, etc. that allow for very fun extension of the general API.
Another part I guess is that every part (that I have been able to think of thus far) is customizable. So you can change (per-search) the sorting algorithm, the display, the highlighting, the preview, the search text, etc. So you can fine-tune each aspect of it for the particular search or just your general preferences.
Also, I made it just because I was having lots of fun with it. I think fzf is a super awesome application (and plugin), so if it's working well for you I don't think I would switch!
Yeah, I contributed to Denite and have talked to shougo about Denite as an inspiration for telescope.
It's a great project. I just added a note (which is the least I can do for the projects) here: https://github.com/nvim-telescope/telescope.nvim/commit/d466...
Hi everyone, I'm the creator of telescope :)
Happy to answer some questions / give my thoughts about telescope here.
Thanks!