Description
Something I've missed for a long time in scvim is using thisProcess.nowExecutingPath in a .scd file to get the current buffer's absolute path.
I think the way to achive this is to implement Document support for scvim. I have a proof-of-concept here which works for neovim using the neovim-remote tool. It should be easy to adopt for regular vim as well which already include the --remote-expr flag by default.
Implementing Document for scvim comes with some issues though, because you get a "duplicate class" conflict when using the IDE (ScIDE.sc also implements Document). I have looked at ScelDocument, which inherits another implementation of Document (found in editors/scel), so I'm guessing scel-users suffer the same problem with the "duplicate class" error in the IDE. Maybe someone using emacs/scel could confirm this? I'm hoping there is some way to only include SCVim.sc when running sclang with the -i scvim flag, but I haven't found one yet.
Does anyone with more experience with Document have any thoughts on this?