diff options
| author | Christian Brabandt <cb@256bit.org> | 2023-09-30 12:49:18 +0200 |
|---|---|---|
| committer | Christian Brabandt <cb@256bit.org> | 2023-09-30 12:49:18 +0200 |
| commit | e085dfda5d8dde064b0332464040959479696d1c (patch) | |
| tree | b9d30e78eb9335de6f2db790f888f0a9bd9514d7 /runtime/doc/editing.txt | |
| parent | 1f025b01e29be6fce907d0379602b45031d6998f (diff) | |
patch 9.0.1962: No support for writing extended attributesv9.0.1962
Problem: No support for writing extended attributes
Solution: Add extended attribute support for linux
It's been a long standing issue, that if you write a file with extended
attributes and backupcopy is set to no, the file will loose the extended
attributes.
So this patch adds support for retrieving the extended attributes and
copying it to the new file. It currently only works on linux, mainly
because I don't know the different APIs for other systems (BSD, MacOSX and
Solaris). On linux, this should be supported since Kernel 2.4 or
something, so this should be pretty safe to use now.
Enable the extended attribute support with normal builds.
I also added it explicitly to the :version output as well as make it
able to check using `:echo has("xattr")`, to have users easily check
that this is available.
In contrast to the similar support for SELINUX and SMACK support (which
also internally uses extended attributes), I have made this a FEAT_XATTR
define, instead of the similar HAVE_XATTR.
Add a test and change CI to include relevant packages so that CI can
test that extended attributes are correctly written.
closes: #306
closes: #13203
Signed-off-by: Christian Brabandt <cb@256bit.org>
Diffstat (limited to 'runtime/doc/editing.txt')
| -rw-r--r-- | runtime/doc/editing.txt | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/runtime/doc/editing.txt b/runtime/doc/editing.txt index 46279110a7..a015c8462a 100644 --- a/runtime/doc/editing.txt +++ b/runtime/doc/editing.txt @@ -1,4 +1,4 @@ -*editing.txt* For Vim version 9.0. Last change: 2023 Sep 22 +*editing.txt* For Vim version 9.0. Last change: 2023 Sep 27 VIM REFERENCE MANUAL by Bram Moolenaar @@ -1097,6 +1097,13 @@ will get the ACL info of the original file. The ACL info is also used to check if a file is read-only (when opening the file). + *xattr* *E1506* *E1507* *E1508* *E1509* +xattr stands for Extended Attributes It is an advanced way to save metadata +alongside the file in the filesystem. It depends on the actual filesystem +being used and Vim supports it only on a Linux system. + Vim attempts to preserve the extended attribute info when writing a file. +The backup file will get the extended attribute of the original file. + *read-only-share* When MS-Windows shares a drive on the network it can be marked as read-only. This means that even if the file read-only attribute is absent, and the ACL |