Hi, I am using your plugin to write tests on a very old plugin.
Unfortunately this plugin calls the builtin vim function expand in a lot of places.
In my (first) test, I am doing exactly what you do in yours: I read into a new buffer the content of a fixture. Unfortunately, because it is an unnamed buffer, the expand doesn't return a value and the function I am testing doesn't work as expected.
As a workaround I am doing:
new
call PasteCodeFrom('myscenario')
write MyFile.extension
[etc...]
as you can imagine, my local folder is full of this written buffers :)
Can you share with me a trick I can use in these situations?
Regards 🙏
Hi, I am using your plugin to write tests on a very old plugin. Unfortunately this plugin calls the builtin vim function
expandin a lot of places. In my (first) test, I am doing exactly what you do in yours: I read into anewbuffer the content of a fixture. Unfortunately, because it is an unnamed buffer, theexpanddoesn't return a value and the function I am testing doesn't work as expected.As a workaround I am doing:
as you can imagine, my local folder is full of this written buffers :) Can you share with me a trick I can use in these situations? Regards 🙏