Differences

This shows you the differences between two versions of the page.

--- project:vo [2015/05/26 11:26] – 91.89.129.106
+++ project:vo [2017/12/11 18:41] (current) – [wish list] 88.65.214.4
@@ Line 99: / Line 99: @@
 ===== wish list =====
-  * after checking in, the file is left behind without write permissions. In general this reminds you to to use ''vo'' instead of a plain editor. Nevertheless there are some rare cases where this behaviour causes problems and sould be allowed to leave a writeable file.
+  * after checking in, the file is left behind without write permissions. In general this reminds you to use ''vo'' instead of a plain editor. Nevertheless there are some rare cases where this behaviour causes problems and it should be allowed to leave a writeable file.
   * if a file has been already opened with ''vo'' a second invocation complains about the file already being open and terminates - BUT checks in the open file first, leaving the first ''vo'' with a readonly file.
-  * if the very first action is "vo -i <filename>" the RCS subdirectory is not created
+  * try harder to determine who's performing the edit - <code> w | awk -v t="$( tty < /dev/fd/2 )" '{sub("/dev/","",t);if ( $2 == t ) { print $1"@"$3 a}}' </code>
+  * on the very first check in, report these parameters to the rcs log:
+    * mtime
+    * ctime
+    * owner, group
+    * permissions
+    * sha256
+    * attribs
+    * acl
+  * add a "-c" option to create a non-existing file
+  * if the very first action is "vo -i <filename>" the RCS subdirectory is not created - but should be
   * integrate with etckeeper
   * integrate with other version control systems like svn, git
+  * integrate some sort of blacklist to prevent files from being bothered by RCSat all.
+  * when detecting an RCS unaware modification record file time stamps
+  * add rcshist command to packet or better: its functionality to vo