A file-based task manager
ngp.computer
Update readme for use of symlinks vs hardlinks
+2
-2
readme
+2
-2
readme
···
28
28
29
29
https://github.com/junegunn/fzf
30
30
31
-
tsk workspaces must be created on filesystems that support hard linking.
31
+
tsk workspaces must be created on filesystems that support symlinking.
32
32
33
33
Task-level metadata requires Linux's xattr(7) API and a filesystem that supports
34
34
it. Patches that implement this for other operating systems are welcome.
···
59
59
New tasks are created with the `tsk push` command. A title is always required,
60
60
but can be modified later. A unique identifier is selected automatically and a
61
61
file with the title and any body contents supplied are stored in the
62
-
.tsk/archive folder. A hardlink is then created in the .tsk/tasks folder marking
62
+
.tsk/archive folder. A symlink is then created in the .tsk/tasks folder marking
63
63
the task is "open." The task is then added to the top of the "stack" by having
64
64
its tsk-ID and title added to the .tsk/index file.
65
65