Hi! I just made an obsdian alternative in terminal after searching for an Obsidian like TUI and got nothing. So I built one myself.
Wow, looks really nice, and the README’s super comprehensive. I don’t know if I missed it or not, but do you support inter-note link navigation (like Obsidian WikiLinks)? I know markdown-oxide did this with LSP actions, but I’d love to know more about your plans for navigation/lsp-like features, if any
Beautiful
I'm too far down the org roam rabbit hole to ever come out but... If you get org support give me a holler. Looks really nice
Thanks! tbh, I've never heard about org-roam, probably because of the Emacs thing, I've never really used Emacs. I'll look into it :)
It basically implements Roam / Obsidian features inside Emacs Org directories by installing a SQLite layer to manage linking and node management. Its a beautiful piece of software, its feature complete and finished.
A paragraph or two on your motivation for this and the benefits of this approach would be helpful. Thanks!
Yeah sure :) The motivation is actually really that simple. I was searching for a markdown editor similar to Obsidian with a terminal user interface, but I couldn't find any that really fit the needs of a proper markdown tool like Obsidian. Though Ekphos isn't yet reaching what Obsidian is capable of, we're surely getting closer and closer. But I want to take only what really matters from Obsidian, so it doesn't get bloated and people can really focus on writing the markdown
looks promising but i prefer nvim instead of learning a new tool.
Ekphos uses Neovim keybindings btw :)
It is very pretty but curious if there are any advantages over Obsidian?
Feature wise, not all will be implemented due to the limitations of a terminal user interface, but it has upsides in performance and being lightweight, plus native nvim keybindings for nvim users
Why not (n)vim or emacs and some plugins?
I was thinking a plugin wouldn't be sufficient for extending it beyond a regular markdown editor, so I went for a full standalone app instead for better upgradeability, optimization, etc.
So you say it's inspired by Obsidian (and call it an "alternative") but notably missing from your table of syntax support are [[wikilinks]], which for many (I would guess most) users would prevent this from being a drop-in replacement, even for just viewing a vault. Is there a reason you chose not to support them?
Yes, internal links will be introduced in the next version along with other features like standard theming and more. Ekphos is currently in a rapid development stage and is slowly reaching core markdown feature parity with Obsidian. Feel free to open a discussion in the gitHub repo for things that would be nice to add to Ekphos :)