chore(docs): update with deterministic order
|
Before Width: | Height: | Size: 136 KiB After Width: | Height: | Size: 100 KiB |
|
Before Width: | Height: | Size: 188 KiB After Width: | Height: | Size: 212 KiB |
|
Before Width: | Height: | Size: 212 KiB After Width: | Height: | Size: 583 KiB |
@@ -20,7 +20,7 @@ If that doesn't work, then:
|
||||
|
||||
Once you have Dev Tools open, click on "Console" tab:
|
||||
|
||||

|
||||

|
||||
|
||||
Copy-paste (or screenshot) the logs. It's better to provide not just errors, but the whole log, which might provide context while analyzing the bug.
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 100 KiB After Width: | Height: | Size: 136 KiB |
|
Before Width: | Height: | Size: 583 KiB After Width: | Height: | Size: 188 KiB |
@@ -1,5 +1,5 @@
|
||||
# "TriliumNext Notes" Not Opened
|
||||

|
||||
# "TriliumNext Notes" Not Opened
|
||||

|
||||
|
||||
When running TriliumNext for the first time or updating to a newer version, macOS will prevent its execution.
|
||||
|
||||
@@ -13,4 +13,4 @@ To bypass this issue, follow these steps:
|
||||
|
||||
| | |
|
||||
| --- | --- |
|
||||
|  <br> <br>The privacy settings in “System Settings”, showing the alert that TriliumNext was blocked. |  <br> <br>The confirmation screen to bypass the run restrictions. |
|
||||
|  <br> <br>The privacy settings in “System Settings”, showing the alert that TriliumNext was blocked. |  <br> <br>The confirmation screen to bypass the run restrictions. |
|
||||