vim-pipe does not support use case when real file name or extension is required

[gamato]

vim-pipe does not seem to support use-cases when file name or extension is important.
For instance I've got a tool that behaves depending on file extension.
Is there a way to make it work with vim-pipe ?

[krisajenkins]

vim-pipe works on filetype, which (usually) works based on extension. So if your two different extensions have two different filetypes in vim, you should just be able to set a different vim-pipe command for each type.

[gamato]

Unfortunately that does not help in this case. The tool cannot be explicitly told what to do, it takes action(s) based on extension(s) of file(s) passed on command line. So passing Vim buffer via stdin is no go. I need the file to be either created, like the trick with <(cat), but with real name; or I need Vim buffer to be saved and real file path passed to the tool. Is it possible, either of mentioned, please ?

[Walfisch]

Have you tried using % as a placeholder for the current filename?

let b:vimpipe_command="echo  %"

You can use a more sophisticated File pattern to set a custom command, eg all files ending with Haha.txt:

autocmd BufNewFile,BufRead *Haha.txt let b:vimpipe_command="echo  %"