Allan Odgaard 6aa871576f Don’t read user settings from file::path_attributes ...

The reason for this is mainly that the path given to path_attributes() might be a virtual path, in which case using that to obtain settings can cause problems. For example if the (virtual) path is ‘/net/some/long/path’ (rmate) then we’ll hit that path locally, but stat’ing paths under /net can take seconds.

Also, the ‘scopeAttributes’ read from the user settings isn’t technically path attributes. Though the feature this allows is that we can scope the encrypt/decrypt export/import commands to ‘attr.enable-encryption’ and then put something like this in a project’s .tm_properties:

    [ private/** ]
    scopeAttributes = "attr.enable-encryption"

2013-05-15 15:45:36 +07:00

..

src

Don’t read user settings from file::path_attributes

2013-05-15 15:45:36 +07:00

tests

Remove path attributes from document_t

2013-05-12 23:04:57 +07:00

target

Initial commit

2012-08-09 16:25:56 +02:00