Prepare tpnote version v1.22.7

Cargo.toml

@@ -15,7 +15,7 @@ license = "MIT/Apache-2.0"
 readme = "README.md"
 repository = "https://gitlab.com/getreu/tp-note"
 rust-version = "1.70.0"
-version = "1.22.6"
+version = "1.22.7"
 
 [profile.release]
 strip = "symbols"

docs/build/man/man1/tpnote.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "TP-NOTE" "1" "2023-10-06" "Version 1.22.6" "Tp-Note documentation"
+.TH "TP-NOTE" "1" "2023-10-14" "Version 1.22.7" "Tp-Note documentation"
 .hy
 .SH NAME
 .PP
@@ -966,7 +966,7 @@ Valid values are: `\f[V]off\f[R]', `\f[V]short\f[R]' and
 In order to achieve this, the user must respect the following convention
 concerning absolute paths in local links in Tp-Note documents: When a
 document contains a local link with an absolute path, the base of this
-path is considered to be the the directory where the marker file
+path is considered to be the directory where the marker file
 `\f[V].tpnoteroot\f[R]' resides (or `\f[V]/\f[R]' in non exists).
 The option `\f[V]--export-link- rewriting\f[R]' decides how local links
 in the Tp-Note document are converted when the HTML is generated.
@@ -1017,10 +1017,20 @@ situation is simpler as the \f[I]text\f[R] property never changes.
 However, there is one exception: when the text property contains an
 autolink starting with `\f[V]tpnote:\f[R]' or `\f[V]http:\f[R]' only the
 file stem is displayed.
-For example, the autolink: `\f[V]<tpnote:dir/my file.md>.\f[R]' is
-transformed into `\f[V][my file](<tpnote:dir/my file.md>)\f[R]' during
-the HTML rendition process.
-This explains why it appears as `\f[V]my file\f[R]' in the browser.
+For example, the Markdown autolink:
+`\f[V]<tpnote:dir/123-My File.md>.\f[R]' is transformed into
+`\f[V][My File](<tpnote:dir/123-My File.md>)\f[R]' during the HTML
+rendition process.
+This explains why it appears as `\f[V]My File\f[R]' in the browser.
+.PP
+As mentioned above, the shortest way to refer to other Tp-Note
+documents, is indicating their sort-tag only.
+For example, the above links can be shortened to
+`\f[V]<tpnote:dir/123>.\f[R]' and
+`\f[V][my file](<tpnote:dir/123>)\f[R]'.
+If the other document is located in the same directory, the links are
+even shorter: `\f[V]<tpnote:123>.\f[R]' and
+`\f[V][my file](<tpnote:123>)\f[R]'.
 .SH METADATA FILENAME SYNCHRONIZATION
 .PP
 Consider the following Tp-Note file:

docs/source/tpnote--manpage.md

@@ -1,10 +1,10 @@
 ---
-title:      TP-NOTE(1) Version 1.22.6 | Tp-Note documentation
+title:      TP-NOTE(1) Version 1.22.7 | Tp-Note documentation
 subtitle:   manpage
 author:     Jens Getreu
-version:    1.22.6
+version:    1.22.7
 filename_sync: false
-date:       2023-10-06
+date:       2023-10-14
 lang:       en-GB
 ---
 

docs/source/tpnote--manual.md

@@ -2,8 +2,8 @@
 title:    "Tp-Note: save and edit your clipboard content as a note file"
 subtitle: Organize your notes with your favourite editor and markup language
 author:   Jens Getreu
-date:     2023-10-10
-version:  1.22.6
+date:     2023-10-14
+version:  1.22.7
 filename_sync: false
 lang:     en-GB
 ---

tpnote/Cargo.toml

@@ -91,11 +91,11 @@ serde.workspace = true
 serde_yaml.workspace = true
 structopt = "0.3.26"
 thiserror.workspace = true
-time = "0.3.29"
+time = "0.3.30"
 tera.workspace = true
 toml.workspace = true
-tpnote-lib = { path = "../tpnote-lib", default-features = false }
-#tpnote-lib = { version = "0.28.2", default-features = false}
+#tpnote-lib = { path = "../tpnote-lib", default-features = false }
+tpnote-lib = { version = "0.28.2", default-features = false}
 webbrowser = { version = "0.8.12", optional = true }
 
 [target.'cfg(windows)'.dependencies]