summaryrefslogtreecommitdiff
path: root/docs/guide
diff options
context:
space:
mode:
authorGalen Williamson <galen@vector35.com>2025-04-15 11:48:14 -0400
committerGalen Williamson <galen@vector35.com>2025-04-15 11:48:14 -0400
commit7a818034c7952a7219043c6fd548b01c95495410 (patch)
tree4db0f546dd339eb47b004db093ee281e6a8601ab /docs/guide
parent0d1abf5f01797a22e28360767fb3ac86576104f5 (diff)
Fixed indentation on Launching from CLI doc section
Diffstat (limited to 'docs/guide')
-rw-r--r--docs/guide/index.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/guide/index.md b/docs/guide/index.md
index bb536c36..dc5b7d20 100644
--- a/docs/guide/index.md
+++ b/docs/guide/index.md
@@ -1033,9 +1033,9 @@ When you launch Binary Ninja from the command-line, you can control whether or n
* Running Binary Ninja from the command line will try to find a running instance of the same version in which to open any files or URLs passed on the command line, or activate the main window if no arguments are provided.
* For users whose workflow involves running Binary Ninja from a shell, just running `binaryninja` will try to activate a running instance, and if it does, return you to your shell. Otherwise it will launch a new instance of Binary Ninja.
* Running `binaryninja` with a file path (or paths), like `binaryninja /bin/ls /bin/cat`, will
- 1. Try to activate and focus existing tabs for those files in a running instance, or failing that,
- 2. Try to open those files in new tabs in a running instance, or failing that,
- 3. Open those files in a new instance of Binary Ninja.
+ 1. Try to activate and focus existing tabs for those files in a running instance, or failing that,
+ 2. Try to open those files in new tabs in a running instance, or failing that,
+ 3. Open those files in a new instance of Binary Ninja.
* Passing the `-n` or `--new-instance` command line argument will cause a new Binary Ninja application to be launched and any files or URLs on the command line will be opened in the new instance.
## Debugger