-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to follow links #32
Comments
We can follow the configuration object approach. The behavior would be disabled by default, since there is some risk of infinite recursion if a link points to a parent dir that Could you create a PR with this feature? |
I am working on it, and have a draft in my fork already, but need to look into it more deeply why it does not yet work as expected... |
Good! Feel free to ask in this thread anything you need, although I see your fork already has a good shape. |
Hi @Marwe, just revisiting some issues. Did you managed to get it work? |
No, I am missing a potentially small piece, as it seems and did not find time to dig into it again. If you want to look at the current state see branch followlinks: BTW, I added a make target |
Hm, currently I get a |
Nice idea!
Just to know, what's the current issue?
Check that you have |
An improvement for our workflows would be to allow following links.
We use (soft) links within the filesystem to use the data in different contexts, but the plugin stops at links and does not follow them.
Files in linked directories are not available, since the link itself does not match the pattern.
A global fix is relatively easy, I implemented it with the additional option
followlinks=True
in os.walk, but maybe for an implementation an option with a GUI checkbox would be better (settings
object inLoadThemAllDialog.py
)? The latter needs changes in different places.The text was updated successfully, but these errors were encountered: