|
@@ -10,7 +10,7 @@ Table of Contents
|
|
|
* [LIMITATIONS](#limitations)
|
|
* [LIMITATIONS](#limitations)
|
|
|
* [PROGRAMMER NOTES](#programmer-notes)
|
|
* [PROGRAMMER NOTES](#programmer-notes)
|
|
|
* [MacOS](#macos)
|
|
* [MacOS](#macos)
|
|
|
- * [DEVELOPMENT STATUS](#status)
|
|
|
|
|
|
|
+ * [DEVELOPMENT STATUS](#development-status)
|
|
|
|
|
|
|
|
## SYNOPSIS
|
|
## SYNOPSIS
|
|
|
|
|
|
|
@@ -146,7 +146,7 @@ As comments are editted or appended, new records are added to the database. Olde
|
|
|
|
|
|
|
|
and just fetch the first record.
|
|
and just fetch the first record.
|
|
|
|
|
|
|
|
-### MacOS {#macos}
|
|
|
|
|
|
|
+### MacOS
|
|
|
|
|
|
|
|
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:
|
|
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:
|
|
|
|
|
|
|
@@ -162,7 +162,7 @@ If the Finder is used to copy/move files, the comments are moved properly to bot
|
|
|
|
|
|
|
|
**MacOS** has AppleScript, by which you can ask the Finder to perform the file copy/move. In this case, the comments are moved properly.
|
|
**MacOS** has AppleScript, by which you can ask the Finder to perform the file copy/move. In this case, the comments are moved properly.
|
|
|
|
|
|
|
|
-## DEVELOPMENT STATUS{#status}
|
|
|
|
|
|
|
+## DEVELOPMENT STATUS
|
|
|
|
|
|
|
|
Each app is a standalone file. That means there is a lot of redundancy between the tthree apps. And there _may_ be some inconsistency.
|
|
Each app is a standalone file. That means there is a lot of redundancy between the tthree apps. And there _may_ be some inconsistency.
|
|
|
|
|
|
