AstroNvim / AstroNvim/astrocommunity

[pack/lua] Random choice of source formatting pattern on save file

Open
#1,690 2 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Lua
Stars
1.7k
Forks
313
PR merge metrics
No merged PRs in 30d

Description

### Checklist

- [x] I have searched through the AstroNvim documentation
- [x] I have searched through the existing issues of this project
- [x] I have searched the existing issues of plugins related to this issue
- [x] I can replicate the bug with the minimal `repro.lua` provided below

### Neovim version (nvim -v)

NVIM v0.11.4

### Operating system/version

EndeavourOS Linux

### Terminal/GUI

alacritty

### Describe the bug

I use an astrocommunity pack/lua

`~/.config/nvim/lua/community.lua`:
```
...
---@type LazySpec
return {
...
{ import = "astrocommunity.pack.lua" },
...
}
```
This is all, no modifications ever attempted.

### Steps to Reproduce

Unfortunately, I can't supply a way to reproduce the bug. There are two source format styles: one uses two spaces for an indentation, no parentheses for a single argument, etc. Another uses a tab for indentation, function calls always with parentheses for a single argument, etc.

I just cant predict which style will be used for formatting on save file.

### Expected behavior

I expect a single Lua formatting style to be used on save file always. A manual choice is preferable.

### Screenshots

_No response_

### Additional Context

_No response_

### Minimal configuration

```Lua
N/A
```

Contributor guide

Open the contributing guide

Research direction

Start with the reported ~/.config/nvim/lua/community.lua import of astrocommunity.pack.lua and investigate which Lua formatter is selected when saving. The issue provides no reproducible configuration or repository file path, so first establish a minimal reproduction; done means Lua files consistently use one formatting style or expose a clear manual choice.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua, neovim
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.