From e9501e77d4efb1ccc4d179d049933be2df1aa8e0 Mon Sep 17 00:00:00 2001 From: Arun Prakash Jana Date: Wed, 4 Jan 2017 06:49:18 +0530 Subject: [PATCH] Note on --fixtags. --- README.md | 3 ++- buku.1 | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 55b6cea..9806f7f 100644 --- a/README.md +++ b/README.md @@ -227,6 +227,7 @@ Shell completion scripts for Bash, Fish and Zsh can be found in respective subdi - Bookmarks with immutable titles are listed with bold `(L)` after the URL. - **Tags**: - Comma (`,`) is the tag delimiter in DB. A tag cannot have comma(s) in it. Tags are filtered (for unique tags) and sorted. Tags are stored in lower case and can be replaced, appended or deleted. + - Releases prior to [v2.7](https://github.com/jarun/Buku/releases/tag/v2.7) support both capital and lower cases in tags. From v2.7 all tags are stored in lowercase. An undocumented option `--fixtags` is introduced to modify the older tags. It also fixes another issue where the same tag appears multiple times in the tagset of a record. Run `buku --fixtags` once. - **Update** operation: - If --title, --tag or --comment is passed without argument, clear the corresponding field from DB. - If --url is passed (and --title is omitted), update the title from web using the URL. @@ -244,7 +245,7 @@ Shell completion scripts for Bash, Fish and Zsh can be found in respective subdi - --sreg : match a regular expression (ignores --deep). - --stag : search bookmarks by a tag, or list all tags alphabetically with usage count (if no arguments). - Search results are indexed serially. This index is different from actual database index of a bookmark record which is shown in bold within `[]` after the URL. -- **Encryption** is optional and manual. AES256 algorithm is used. To use encryption, the database file should be unlocked (-k) before using buku and locked (-l) afterwards. Between these 2 operations, the database file lies unencrypted on the disk, and NOT in memory. Also, note that the database file is *unencrypted on creation*. +- **Encryption** is optional and manual. AES256 algorithm is used. To use encryption, the database file should be unlocked (-k) before using `buku` and locked (-l) afterwards. Between these 2 operations, the database file lies unencrypted on the disk, and NOT in memory. Also, note that the database file is *unencrypted on creation*. - **Proxy** support: environment variable *https_proxy*, if defined, is used to tunnel data for both http and https connections. The supported format is: http[s]://[username:password@]proxyhost:proxyport/ diff --git a/buku.1 b/buku.1 index 300306b..b63a805 100644 --- a/buku.1 +++ b/buku.1 @@ -41,6 +41,7 @@ Bookmarks with immutable titles are listed with bold '(L)' after the URL. .IP 5. 4 \fBTags\fR: - Comma (',') is the tag delimiter in DB. A tag cannot have comma(s) in it. Tags are filtered (for unique tags) and sorted. Tags are stored in lower case and can be replaced, appended or deleted. + - Releases prior to v2.7 support both capital and lower cases in tags. From v2.7 all tags are stored in lowercase. An undocumented option --\fIfixtags\fR is introduced to modify the older tags. It also fixes another issue where the same tag appears multiple times in the tagset of a record. Run \fBbuku --fixtags\fR once. .PP .IP 6. 4 \fBUpdate\fR operation: @@ -66,7 +67,7 @@ Bookmarks with immutable titles are listed with bold '(L)' after the URL. - Search results are indexed serially. This index is different from actual database index of a bookmark record which is shown in bold within '[]' after the URL. .PP .IP 9. 4 -\fBEncryption\fR is optional and manual. AES256 algorithm is used. To use encryption, the database file should be unlocked (-k) before using buku and locked (-l) afterwards. Between these 2 operations, the database file lies unencrypted on the disk, and NOT in memory. Also, note that the database file is \fBunencrypted on creation\fR. +\fBEncryption\fR is optional and manual. AES256 algorithm is used. To use encryption, the database file should be unlocked (-k) before using \fBbuku\fR and locked (-l) afterwards. Between these 2 operations, the database file lies unencrypted on the disk, and NOT in memory. Also, note that the database file is \fBunencrypted on creation\fR. .PP .IP 10. 4 \fBProxy\fR support: please refer to the \fBENVIRONMENT\fR section.