Yochem van Rosmalen

> Actually, this info is already on the job, try nvim_get_chan_info(&channel) in a terminal buffer. Oh wow, didn't know! Thanks, I'll try it out in the upcoming days.

Working solution: ```lua vim.api.nvim_create_autocmd('TermOpen', { callback = function(ev) local chans = vim.api.nvim_list_chans() for _, chan in ipairs(chans) do if chan.buffer == ev.buf then if #chan.argv

I understand that how to present the URL needs discussion, but simply emitting OSC8 for all markdown links wouldn't hurt right? This just actively tells the emulator "Hey, this is...

I agree with @echasnovski here. How would the example provided in the description deal with other ftplugin code that does not simply set buffer-local options? Looking at the current ftplugin...

That's true. Not sure how prevalent that is (for the ftplugins currently maintained by Nvim). It seems that Justin's proposed solution would also break appending to `b:undo_ftplugin`. Current options I...

> I am not going to add defensive checks to a "hot" codepath Understandable, I agree it should just give the shell error. I might be able to look at...

Ah yes, forgot to mention it. That's also the idea indeed! On that note, should this plugin be an almost compatible replacement for both, or just replace the common functionality...

> It should be a functional replacement, but no need to replicate the full interface (unless it's natural). Noted! > And just for the record (I understand that this is...

I might need some help with the parsing of `b:match_words`. The original implementation uses a lot of regex kungfu to achieve things like escaping certain chars, supporting backrefs and more...

Thanks, I'll try t do that more. The problem is that there is a lot of manual parsing involved, e.g. manually finding capture groups, and then swapping the backrefs with...