A Linux/BSD app to add comments to files. The comments are stored in a database, and where possible, in the xattr field of the filesystem. There is a GUI, using Python3+Qt5. There is also a terminal (curses) version and a command-line (scriptable).
Pat Beirne 80e41b5324 touch up | il y a 2 ans | |
---|---|---|
README.md | il y a 2 ans | |
dirnotes | il y a 2 ans | |
dirnotes-cli | il y a 2 ans | |
dirnotes-cli.md | il y a 2 ans | |
dirnotes-tui | il y a 2 ans |
The dirnotes family of apps allows you to add a descriptive comment to a file. The descriptions are stored in two places:
[The MacOS stores its comments in a similar way.]
The dirnotes
app is a GUI app, using the Qt5 framework. At startup, it displays the contents of the current directory, and the comments associated with any of the files or directories.
Simple mouse clicks allow you to tunnel down into directories, or rise up the file system.
You can create/edit comments and choose whether the xattr or database version of the comments take priority,
The dirnotes-tui
is a very similar app, but uses the curses framework to display its activity in a terminal window. This can be handy if you have to work across a network, or if terminal apps are you preference.
The dirnotes-cli
is a command line tool, which may be handy for scripting.
The dirnotes
program displays usage and keystoke info when you press F1. The dirnotes-tui
program display onscreen usage when you press the 'h' key, or F1.
The dirnotes-cli
program has a man page.
In short, you navigate dirnotes
and dirnotes-tui
by using the up/down arrow keys, to enter into a directory.
The -tui version accepts e for edit,
s for sort, M to change between xattr/database priority.
The dirnotes-cli
has options for -l list and -c create a comment.
Each of the 3 apps in the family is self contained.
The dirnotes
app requires Python3 and the Qt5 framework.
The dirnotes-tui
and dirnotes-cli
apps simply require Python3.
By default, the file ~/.dirnotes.conf will be used to load the user's config. This is a JSON file, with three attributes that are important:
- xattr_tag (default:
usr.xdg.comment
)- database (default:
~/.dirnotes.db
)- start_mode (xattr or db priority)
[not fully implemented]
The file comments are located in two locations: a database, and in the xattr properties of the file. Each of these storage locations has its own benefits and limitations:
Comments stored in the xattr properties can be copied/moved with the file, if you
use the correct options for cp
. The mv
utility
automatically preserves xattr. Other programs can also be coerced into
perserving xattr properties:
rsync
tar
mksquashfs
Not all file systems support xattr properties (vfat/exfat does not).
The current implementation of sshfs
and scp
do not support the copy of xattr properties.
If you want to copy files to a remote machine and include the xattr comments, use rsync
with the -X option. Or tar
.
Some editing apps (like vim) will create a new file when saving the data, which orphans the xattr comments. For these apps, use the database system.
Comments stored in the database work for all filesystem types (including vfat/exfat/sshfs)
Comments are personalized to the current user. Another user on the same system will not see these comments.
Files are indexed by their complete path name. Removable filesystems should be mounted in a consistent way, so that the complete path name is reproducable.
Comments stored in the database do not travel with the files when they are moved or copied, unless using the dirnotes family of tools.
Instead of an API, here is how you can get directly at the underlying comment data. If you intend to use the dirnotes apps, try to keep the two versions of the comments in sync.
Use the commands
xattr -l [filename]
to display the comments/author/date on a file. For example:
$ xattr -l /etc/fstab
user.xdg.comment: controls the default mount bindings
user.xdg.comment.author: patb
user.xdg.comment.date: 2022-09-29 08:07:42
The other options on the xattr command line tool allow you to write (xattr -w) or delete (xattr -d) the comments.
The comments are stored in an Sqlite3 database, usually located at "~/.dirnotes.db". The database itself is contained within that file, and its schema is this:
CREATE TABLE dirnotes (name TEXT, date DATETIME, size INTEGER, comment TEXT, comment_date DATETIME, author TEXT)
field | usage | example |
---|---|---|
name | the long filename, using python's os.path.abspath() | /home/patb/projects/dirnotes/README.md |
date | the file's modified date | 2020-01-13 09:25:40 |
size | the byte count of the file | 145 |
comment | a utf-8 string | the readme for the GIT page |
comment_date | the date of the comment itself | 2020-10-03 22:30:19 |
author | the system name of the user who created the comment | patb |
The 'date' and 'size' fields reflect the file's modification date and size at the time of the last edit of the file comment, which is also 'comment_date'.
As comments are editted or appended, new records are added to the database. Older records are are not purged. This gives you a history of the comments, but it means that fetching the most recent comment involves something like
SELECT * FROM dirnotes WHERE name=? ORDER BY comment_date DESC
and just fetch the first record.
The MacOS inherently supports file comments. The Finder app manages most of the user activity. It handles file comments in a similar manner to Dirnotes. Comments are stored in two places:
com.apple.metadata:kMDItemFinderComment
)pList
The user can examine the file comments by opening the GetInfo dialog, and scrolling down to "Comment"
If the Finder is used to copy/move files, the comments are moved properly to both destinations. If you use the os to copy/move the files, you can ask that the xattr properties get moved, but the .DS-Store file will not be updated. That means the Finder will not see file comments on the destination file.
MacOS has AppleScript, by which you can ask the Finder to perform the file copy/move. In this case, the comments are moved properly.
Each app is a standalone file. That means there is a lot of redundancy between the tthree apps. And there may be some inconsistency.
2022-10-04
: All three apps are functioning and usable.
The _configfile is fully implemented.
Themes are not implemented.
Comments are intended to be utf-8, but are strings in some places.
MacOS code is not written yet.
The help dialogs in dirnotes-tui
are meagre.