Mercurial > vim

comparison runtime/doc/editing.txt @ 33408:dcfbfe57141c v9.0.1962

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 9.0.1962: No support for writing extended attributes Commit: https://github.com/vim/vim/commit/e085dfda5d8dde064b0332464040959479696d1c Author: Christian Brabandt <cb@256bit.org> Date: Sat Sep 30 12:49:18 2023 +0200 patch 9.0.1962: No support for writing extended attributes 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>
author Christian Brabandt <cb@256bit.org>
date Sat, 30 Sep 2023 13:00:06 +0200
parents 62a34e280593
children b21a1fc34254
comparison
equal deleted inserted replaced
33407:c476e82af6a7 33408:dcfbfe57141c
1 *editing.txt* For Vim version 9.0. Last change: 2023 Sep 22 1 *editing.txt* For Vim version 9.0. Last change: 2023 Sep 27
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
1095 Vim attempts to preserve the ACL info when writing a file. The backup file 1095 Vim attempts to preserve the ACL info when writing a file. The backup file
1096 will get the ACL info of the original file. 1096 will get the ACL info of the original file.
1097 The ACL info is also used to check if a file is read-only (when opening the 1097 The ACL info is also used to check if a file is read-only (when opening the
1098 file). 1098 file).
1099 1099
1100 *xattr* *E1506* *E1507* *E1508* *E1509*
1101 xattr stands for Extended Attributes It is an advanced way to save metadata
1102 alongside the file in the filesystem. It depends on the actual filesystem
1103 being used and Vim supports it only on a Linux system.
1104 Vim attempts to preserve the extended attribute info when writing a file.
1105 The backup file will get the extended attribute of the original file.
1106
1100 *read-only-share* 1107 *read-only-share*
1101 When MS-Windows shares a drive on the network it can be marked as read-only. 1108 When MS-Windows shares a drive on the network it can be marked as read-only.
1102 This means that even if the file read-only attribute is absent, and the ACL 1109 This means that even if the file read-only attribute is absent, and the ACL
1103 settings on NT network shared drives allow writing to the file, you can still 1110 settings on NT network shared drives allow writing to the file, you can still
1104 not write to the file. Vim on Win32 platforms will detect read-only network 1111 not write to the file. Vim on Win32 platforms will detect read-only network