5 ms·

Show HN: A terminal tool for Logseq journal entries

35 points by jrswab 2y ago

Creator here. I built lsq to solve a simple but annoying workflow problem: having to leave the terminal just to make quick notes in Logseq. Technical details: - Written in Go using Bubble Tea for the TUI - Reads Logseq's config.edn for format preferences - Supports both external editor ($EDITOR) and TUI modes - Handles both Markdown and Org formats Core design decisions: 1. Zero-config default installation (uses standard ~/Logseq path) 2. Single command to open today's journal (just 'lsq') 3. TUI mode for Logseq-specific features (TODO/priority cycling) The project started as a simple editor launcher but evolved to include a TUI when I realized certain Logseq features couldn't be easily replicated in a standard text editor. Code and installation instructions are in the repo. Feedback and contributions welcome.

kaushikrabha 2y ago
[flagged]
Gys 2y ago
Some screenshots would be nice ;)
- jrswab 2y ago
  I'll add some to the repo when I get a chance.
snthpy 2y ago
Awesome. I was just looking for something like this this week. I was thinking logseq + nvim + textual but bubbletea is also great.
- jrswab 2y ago
  If you run `lsq` without `-t` it will open with what you have defined as `$EDITOR`.
solarkraft 2y ago
As a semi-aside: Are there headless tools for interacting with Logseq databases, especially queries? This would be super useful for automations.
- solarkraft 2y ago
  Logseq can expose an HTTP API: https://docs.logseq.com/#/page/local%20http%20server https://docs.logseq.com/#/page/local%20http%20server This is less ideal than a library due to the complexity of running it; setting it up on a server will probably be annoying. But it should give you a lot of the power Logseq has, it apparently being the same API as plugins get to use.
- jrswab 2y ago
  I don't know of any at the moment. That said I do want to add the ability to search pages and navigate links within the Logseq graph. This would have to be in the TUI as I don't want to maintain several plugins for various editors.
- cldwalker 2y ago
  When Logseq is running locally, you can use its [local http server](https://docs.logseq.com/#/page/local%20http%20server https://docs.logseq.com/#/page/local%20http%20server) to do this. https://github.com/logseq/nbb-logseq https://github.com/logseq/nbb-logseq is useful for automations and is already used to create github actions e.g. https://github.com/logseq/publish-spa https://github.com/logseq/publish-spa. In the upcoming database version, nbb-logseq is able to read and write Logseq graphs completely independent of the app - https://github.com/logseq/docs/blob/feat/db/db-version.md#scripting https://github.com/logseq/docs/blob/feat/db/db-version.md#sc...
  - jrswab 2y ago
    Thank you for this! I'll check it out as I do want to add the ability to navigate to pages from with the TUI. And at some point add in search functionality since I use it a lot within the Logseq app.
basedrum 2y ago
Thank you! I also wanted this
- jrswab 2y ago
  You're welcome! I'm glad it's not some niche thing that only I needed XD If you have any idea that will make your workflow easier add an "issue" on GitHub so I can keep track of it.
dodorz 2y ago
Is there an equivalent tool for Obsidian?
- jrswab 2y ago
  I don't know but since obsidian uses plan text files like Logseq does you should be able to update the code a bit and point LSQ to your directory. My default it opens up the files in your $EDITOR

35 points by jrswab 2y ago

kaushikrabha 2y ago

[flagged]

Gys 2y ago

Some screenshots would be nice ;)

jrswab 2y ago
I'll add some to the repo when I get a chance.

snthpy 2y ago

Awesome. I was just looking for something like this this week. I was thinking logseq + nvim + textual but bubbletea is also great.

jrswab 2y ago
If you run `lsq` without `-t` it will open with what you have defined as `$EDITOR`.

solarkraft 2y ago

As a semi-aside: Are there headless tools for interacting with Logseq databases, especially queries? This would be super useful for automations.

solarkraft 2y ago
Logseq can expose an HTTP API: https://docs.logseq.com/#/page/local%20http%20server https://docs.logseq.com/#/page/local%20http%20server This is less ideal than a library due to the complexity of running it; setting it up on a server will probably be annoying. But it should give you a lot of the power Logseq has, it apparently being the same API as plugins get to use.
jrswab 2y ago
I don't know of any at the moment. That said I do want to add the ability to search pages and navigate links within the Logseq graph. This would have to be in the TUI as I don't want to maintain several plugins for various editors.
cldwalker 2y ago
When Logseq is running locally, you can use its [local http server](https://docs.logseq.com/#/page/local%20http%20server https://docs.logseq.com/#/page/local%20http%20server) to do this. https://github.com/logseq/nbb-logseq https://github.com/logseq/nbb-logseq is useful for automations and is already used to create github actions e.g. https://github.com/logseq/publish-spa https://github.com/logseq/publish-spa. In the upcoming database version, nbb-logseq is able to read and write Logseq graphs completely independent of the app - https://github.com/logseq/docs/blob/feat/db/db-version.md#scripting https://github.com/logseq/docs/blob/feat/db/db-version.md#sc...
- jrswab 2y ago
  Thank you for this! I'll check it out as I do want to add the ability to navigate to pages from with the TUI. And at some point add in search functionality since I use it a lot within the Logseq app.

basedrum 2y ago

Thank you! I also wanted this

jrswab 2y ago
You're welcome! I'm glad it's not some niche thing that only I needed XD If you have any idea that will make your workflow easier add an "issue" on GitHub so I can keep track of it.

dodorz 2y ago

Is there an equivalent tool for Obsidian?

jrswab 2y ago
I don't know but since obsidian uses plan text files like Logseq does you should be able to update the code a bit and point LSQ to your directory. My default it opens up the files in your $EDITOR