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
I really like how organized your lua/pde folder is!
I think grouping plugin configs by language is a good match for how we think about what our editors support (e.g. "Am I set up for Python development? TypeScript development?").
I'm considering doing the same (grouping configs by language) and was curious what made you choose the nvim/lua/pde structure over nvim/ftplugin or nvim/after/ftplugin.
Were ftplugin/* files something you considered? Any benefits to one approach over the other?
The text was updated successfully, but these errors were encountered:
I really like how organized your
lua/pde
folder is!I think grouping plugin configs by language is a good match for how we think about what our editors support (e.g. "Am I set up for Python development? TypeScript development?").
I'm considering doing the same (grouping configs by language) and was curious what made you choose the
nvim/lua/pde
structure overnvim/ftplugin
ornvim/after/ftplugin
.Were
ftplugin/*
files something you considered? Any benefits to one approach over the other?The text was updated successfully, but these errors were encountered: