Follow on buffer switch

[Tweekism]

Is there any appetite for an option that makes vivify follow you when you switch buffers?

[tuurep]

As an idea: would love this

In practice (implementation): is it a hard problem?

I think one problem related to this would be that different browsers work differently in regards to reusing browser tabs: #117 (comment) onwards

[tuurep]

The remaining big question I think is:

In which cases exactly does this happen? Some kinda on-buffer-switch autocmd, but like, exactly what?

[jannis-baum]

I'd guess it should happen on BufLeave. Question is if there's a way we can figure out what the next buffer will be from there.

[tuurep]

Yeah and do we have to have a sense of "is Vivify currently running for this buffer, or not" ?

[jannis-baum]

Not quite but we also don't need it. We can just POST anyways and all clients that exist on the path will update. Or none if there aren't any. That's how the scrolling & auto updating works as well :)

(#103 will introduce a reply that will let you know how many clients there are but it's not necessary for us to read that reply here, no reason to overcomplicate it ^^)

[twidxuga]

+1 on this feature. Would love to have Vivify follow me around when I browse my markdown "second brain" in nvim. This would remove the need to open additional browser tabs or explicitly call vivify again.

In a previous similar project, I used BufEnter for markdown typed files to make the switch, triggering a push of the new file's content to the server (though this may not be applicable to vivify).

[Tweekism]

Created issue and added to queue

#140 (comment)