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
while playing with contexts configuration, I found I needed more control over what files and folders should be set as context.
More specifically, I work with projects having hidden folders that actually contain important code, (e.g. /.deployment folder that contains files about deployment).
To overcome this, I momentarily created a "clone" function starting from the existing, public one, that is used as resolve for the file context:
I wanted here to still respect .gitignore, but include also hidden files.
WDYT about having the configuration table that's used within utils.scan_dir as a parameter of the function function M.files(winnr, opts, with_content)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
while playing with
contexts
configuration, I found I needed more control over what files and folders should be set as context.More specifically, I work with projects having hidden folders that actually contain important code, (e.g.
/.deployment
folder that contains files about deployment).To overcome this, I momentarily created a "clone" function starting from the existing, public one, that is used as
resolve
for the file context:that's because I could set up the block where we state the directories to be scanned, making it like so:
I wanted here to still respect
.gitignore
, but include also hidden files.WDYT about having the configuration table that's used within
utils.scan_dir
as a parameter of the functionfunction M.files(winnr, opts, with_content)
?Beta Was this translation helpful? Give feedback.
All reactions