I just use Pandoc and specify all .md files on the command line. Here is an incomplete command line: pandoc [some options] 1.md 2.md 3.md.
Source files go last, after all other options, on the command line.
I found two things.
For me the link has to be written '( ./6.md )' with a space before and after the file specification.
Then I found the ebook-convert app wants html files for inputs.
It complains that the inputs are "binary"
"The lookup names are pubdate (publication date) and date (calibre's "Date" column, usually the date you added the book to calibre)."
First, I don't have any insight into CLI calibre and you might get a better answer from Mobileread or by posting a bug, but my guess is that the # character must be reserved exclusively for fragment identifiers for HTML. So it is most likely a feature, not a bug.
Think about it. If the file name were allowed to contain a #, then you would not be able to ...
Converting from mobi to pdf is almost always going to be a problem. Both are rendered formats. The problem could come from anywhere. Two ideas:
First, try to obtain an epub copy instead of a mobi file. It's easier to convert from epub to pdf than from mobi to pdf.
Try decompiling the mobi file (go to mobileread to find a tool that can do so).
Calibre does not provide any compression tools, but indeed one could use third party tools to compress files in the directory structure. The predominant files to target would be DJVU and PDF files. Using ImageMagick's convert utility, it is not difficult to do programmatic compression (write a script that recursively goes through the library directory ...
Calibre (free, open source) can convert between various formats, including mobi to epub.
The command-line ebook-convert is also a part of Calibre:
Also, there are third party tools to enable Calibre to remove DRM, if that is needed.
tags:"=Classics.English" or tags:"=Classics.Russian" or tags:"=Classics"
can be reduced to
It will show all the files whose tags start with "Classics"
Another variation is
If you omit the ^, then it will show those files too whose tags have "Classics" in them, but not necessarily in the beginning. For ...
Short answer, you can't see them in the reader pane.
You'll find the annotations at:
Edit Metadata > Custom medata tab > Annotations
(Presuming you created a custom column called 'Annotations', which is the default name suggested by the plugin.)