Replies: 1 comment
-
#845 Should be solved in |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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