You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which configuration?
Type (custom or builtin): builtin
Filetype: lua
Formatter: luaformat
Expected behavior
Open a lua file with neovim
Open another a different file (:e <name-of-another-lua-file>
Format it :Format
The text of <name-of-another-lua-file> should be replaced with its formatted text.
Actual behaviour
The text of <name-of-another-lua-file> is replaced with the formatted text of the first opened file.
Additional context
I'm not sure why this is happening. I suspected it had to do with the plugin appending the path of the buffer to the CLI call string, however setting the no_append=true while maintaining the buffer's absolute path as the first argument did not fix the issue.
Setting the default config to use no arguments fixed the issue.
Note: although usage of lua-format says that lua files to format must occur before options, the files can occur before or after; tested with version 1.3.6.
The text was updated successfully, but these errors were encountered:
Which configuration?
Type (custom or builtin): builtin
Filetype: lua
Formatter:
luaformat
Expected behavior
:e <name-of-another-lua-file>
:Format
The text of
<name-of-another-lua-file>
should be replaced with its formatted text.Actual behaviour
The text of
<name-of-another-lua-file>
is replaced with the formatted text of the first opened file.Additional context
I'm not sure why this is happening. I suspected it had to do with the plugin appending the path of the buffer to the CLI call string, however setting the
no_append=true
while maintaining the buffer's absolute path as the first argument did not fix the issue.Setting the default config to use no arguments fixed the issue.
Note: although usage of
lua-format
says that lua files to format must occur before options, the files can occur before or after; tested with version 1.3.6.The text was updated successfully, but these errors were encountered: