Request: whitelist setting in config file about dotfiles HOT 4 CLOSED

It's a good idea. I think some users would like a per-host option as well (for instance .quiltrc comes in handy when working with Debian packages but likely isn't needed in other distros or OSX.

The UI will require some changes to support this - at the very least the list command should indicate whether it's whitelisted (and thus subject to linking) or not.

Here is one question I have: Is it okay that some of the supported features are only available if you edit the configuration file? Or, IOW is it okay that the command-line interface only supports basic functionality and advanced features require configfile editing?

If we say it's okay, then feature requests like #16 become much easier to deal with - and I think that's a good feature to have as well.

from dotfiles.

@jbernard: Seems reasonable to me.

from dotfiles.

I think a config-file option like trusted=[…] would allow you whitelist specific files. If the trused option is found in the config file, then all files not list there are considered "untrused" and would only be sync'd with the --force option perhaps.

from dotfiles.

I suspect you may not care about this anymore and after some thought, I'm not sure if there is a lot of demand for this feature still. I accept that this might be a wrong assumption. If I am, please reopen the bug and we can discuss.

I'm nearly done with the next major version which brings some pretty cool features, so check it out if you're interested.

Cheers

from dotfiles.