A couple of those Obsidian features (and more) come out of the box with Vimwiki if configured in Markdown mode. I use it rather interchangeably with Obsidian since they grok the same format and file structure.
Reconstructing Obsidian Features in Vim and Bash
31–40 of 47 posts
Re: Reconstructing Obsidian Features in Vim and Bash
#32For me the main benefit of Obsidian is live-rendering editor + other handy features. Not having to look at two panes side-by-side (or having to parse the markdown format in my head) is such a QOL improvement. Neovim might never be able to provide complete live-rendering. I don't blame it though, I wouldn't want terminals to become a rendering engine. Edit: Grammar
Funny enough, Obsidians live rendering has shown me that plaintext sucks, and that I want richtext and data structures for my stuff. Just that there is no good tool for this. Notion and its clones are the best in that regard, but they suck in their own regard, mainly because they are online-only. And considering how many tried to replicate Notion in obsidian-extensions (and failed), I'm not the only one I guess. Ther…
One plug-in in beta, but has quite a large following in the Obsidian community to achieve what you’re describing with Obsidian is the make.md plug-in.
Re: Reconstructing Obsidian Features in Vim and Bash
#33Earlier quoted context omitted.
Everyone is re-inventing "show codes" from Wordperfect 5 and other similar platforms because no one who is inventing these things has ever used Wordperfect 5. That said, re-solving this problem is turning up some nice new U/X patterns that (as far as I know) weren't around in the older platforms ("show codes on cursor", "local modal editing for format", etc.)
What editors have those two new ux's? I'd like to try them out ("show codes on cursor", "local modal editing for format", etc.)
Obsidian's editor is "show codes on cursor" by default. As you navigate through the rich text expression it changes to the markdown format that produces that expression. You're always in a line / block of Markdown, but the rest of the document is rendered.
"local modal editing" is most often seen in richer IDE experiences like Darklang v0.2's IDE and the Hazel type-directed-holes experiments.
There are more interesting takes as well (Lighttable's live forms, lots of Vic's experiments) but I'm definitely seeing more instances of the first two experiences these days.
Re: Reconstructing Obsidian Features in Vim and Bash
#34I also only found out about Obsidian recently and I've become interested in switching. So far for my notes for the last several years I've just been using raw tex files with TexStudio, and creating various level subsections with macros bound to key combos as needed. It works quite well with the navigation tree and MDI, but Obsidian sounds like it might be a better solution.
The great thing about Obsidian is that it still uses plaintext (it's not obsidian exclusive, i know). In case of issues with the tool, you can view and edit files in an editor. It also makes syncing stuff / backups very easy. Since you're probably having a kind of syntax already it won't be hard to change. With a proper keyboard, it's super fast to create and link notes. On mobile it sucks hard. Things like "[text](l…
Isn't the licensing an issue? As far as I can tell you can't use Obsidian at your workplace without an annual commercial license, which is fair enough but maybe too heavy a lift for many.
Re: Reconstructing Obsidian Features in Vim and Bash
#35Earlier quoted context omitted.
Everyone is re-inventing "show codes" from Wordperfect 5 and other similar platforms because no one who is inventing these things has ever used Wordperfect 5. That said, re-solving this problem is turning up some nice new U/X patterns that (as far as I know) weren't around in the older platforms ("show codes on cursor", "local modal editing for format", etc.)
What editors have those two new ux's? I'd like to try them out ("show codes on cursor", "local modal editing for format", etc.)
Guessing what they mean by show codes on cursor. Showing markdown around the cursor is now in Obsidian, but previously it was in Typora, FoldingText, and a circa 2016 web app called "usecanvas":
There may be examples prior to that, but that's the earliest that I recall.
I'm not sure what is meant by local modal editing - is that describing what logseq does? It switches a block to plain markdown when you're editing it.
I thought word perfect show codes was in another pane, but it's been a very long time since I've seen it, and I didn't use it personally.
Re: Reconstructing Obsidian Features in Vim and Bash
#36What, we're talking about wikis and vim, and not mentioning vimwiki? https://github.com/vimwiki/vimwiki I tried a whole bunch of personal wikis over the years (I see Zim has been mentioned, that's one of the ones I remember trying) and this is the only one that stuck. The github page shows some basic markdown, but it also handles nested checklists (parent nodes can be partially checked off) and understands tables (au…
[deleted]
Re: Reconstructing Obsidian Features in Vim and Bash
#37Earlier quoted context omitted.
Funny enough, Obsidians live rendering has shown me that plaintext sucks, and that I want richtext and data structures for my stuff. Just that there is no good tool for this. Notion and its clones are the best in that regard, but they suck in their own regard, mainly because they are online-only. And considering how many tried to replicate Notion in obsidian-extensions (and failed), I'm not the only one I guess. Ther…
I've become a big fan of LogSeq for these reasons. In LogSeq, you have pages and trees of data (aka blocks[1]. All can be cross-referenced or embeded between each context. It's quite nice. 1: https://docs.logseq.com/#/page/the%20basics%20of%20block%20r...
Looks clean and nice, if only it wouldn't be an Electron app…
Re: Reconstructing Obsidian Features in Vim and Bash
#38What, we're talking about wikis and vim, and not mentioning vimwiki? https://github.com/vimwiki/vimwiki I tried a whole bunch of personal wikis over the years (I see Zim has been mentioned, that's one of the ones I remember trying) and this is the only one that stuck. The github page shows some basic markdown, but it also handles nested checklists (parent nodes can be partially checked off) and understands tables (au…
Shameless plug: there's also wiki.vim [0], which I believe is starting to be a real contender to Vimwiki.
Regardless: In my experience, Vim + wiki with some additional plugins for fast searching and navigation is a very good combo!
Re: Reconstructing Obsidian Features in Vim and Bash
#39I wrote a vim plugin which is my daily wiki driver. It uses Hugo as markdown indexer.
Re: Reconstructing Obsidian Features in Vim and Bash
#40Earlier quoted context omitted.
The great thing about Obsidian is that it still uses plaintext (it's not obsidian exclusive, i know). In case of issues with the tool, you can view and edit files in an editor. It also makes syncing stuff / backups very easy. Since you're probably having a kind of syntax already it won't be hard to change. With a proper keyboard, it's super fast to create and link notes. On mobile it sucks hard. Things like "[text](l…
Isn't the licensing an issue? As far as I can tell you can't use Obsidian at your workplace without an annual commercial license, which is fair enough but maybe too heavy a lift for many.
Yes. Professional use requires licensing. Too bad as our workplace forces the use of OneNote, which imho is lacking.