I have these hooks enabled on many of my projects, but for some reason forgot them here which led to the issue described in https://github.com/zoni/obsidian-export/pull/181 This should help prevent that from happening again.
3.0 KiB
Basic usage
The main interface of obsidian-export is the obsidian-export
CLI command.
As a text interface, this must be run from a terminal or Windows PowerShell.
It is assumed that you have basic familiarity with command-line interfaces and that you set up your PATH
correctly if you installed with cargo
.
Running obsidian-export --version
should print a version number rather than giving some kind of error.
If you downloaded a pre-built binary and didn't put it a location referenced by
PATH
(for example, you put it inDownloads
), you will need to provide the full path to the binary instead.For example
~/Downloads/obsidian-export --version
on Mac/Linux or~\Downloads\obsidian-export --version
on Windows (PowerShell).
Exporting notes
In it's most basic form, obsidian-export
takes just two mandatory arguments, a source and a destination:
obsidian-export /path/to/my-obsidian-vault /path/to/exported-notes/
This will export all of the files from my-obsidian-vault
to exported-notes
, except for those listed in .export-ignore
or .gitignore
.
Note that the destination directory must exist, so you may need to create a new, empty directory first.
If you give it an existing directory, files under that directory may get overwritten.
It is also possible to export individual files:
# Export as some-note.md to /tmp/export/
obsidian-export my-obsidian-vault/some-note.md /tmp/export/
# Export as exported-note.md in /tmp/
obsidian-export my-obsidian-vault/some-note.md /tmp/exported-note.md
Note that in this mode, obsidian-export sees some-note.md
as being the only file that exists in your vault so references to other notes won't be resolved.
This is by design.
If you'd like to export a single note while resolving links or embeds to other areas in your vault then you should instead specify the root of your vault as the source, passing the file you'd like to export with --start-at
, as described in the next section.
Exporting a partial vault
Using the --start-at
argument, you can export just a subset of your vault.
Given the following vault structure:
my-obsidian-vault
├── Notes/
├── Books/
└── People/
This will export only the notes in the Books
directory to exported-notes
:
obsidian-export my-obsidian-vault --start-at my-obsidian-vault/Books exported-notes
In this mode, all notes under the source (the first argument) are considered part of the vault so any references to these files will remain intact, even if they're not part of the exported notes.
Character encodings
At present, UTF-8 character encoding is assumed for all note text as well as filenames. All text and file handling performs lossy conversion to Unicode strings.
Use of non-UTF8 encodings may lead to issues like incorrect text replacement and failure to find linked notes. While this may change in the future, there are no plans to change this behavior in the short term.