But that would mean maintaining two editors. I can’t see that being a sensible design choice.
At the moment there’s two underlying engines (edit and preview) and there are inconsistencies at times and no true source view since the edit view reflects some markdown. With WYSIWYG there should surely just be one engine for edit with fast update to view for most of the screen (depending on design choices).
With any of these a true source view has be available because the plaintext of the underlying document must always exist.
It did occur to me that the source view might not actually be pure source, but more akin to text editors which are set up to highlight code.
Yeah, the “Editor” view at the moment is basically a souped-up source editor. It does syntax highlighting, and the syntax highlighting styles are being taken advantage of to do some presentation (headings, italics, etc). The current editor is the source view for the future WYSIWYG, and if they polish the WYSIWYG view up enough, I can see a case for ditching the preview altogether — and perhaps toning down the styles in the source editor.
Mmm. Text Editors usually have different highlight modes set by language. With option for none - though I don’t know many and remember fewer, so I might be wrong. But some mode control would be useful.
I use both vscode and obsidian very heavily, so directionally I am interested in this thread. I wouldn’t agree fully about integrating obsidian into vs code nor would I rule that out if there’s a good usecase for it.
Based on the additional context, I see that the OP is okay with writing vs code inside vs code and wants a graph view isnide vscode. If that’s the main issue, there are useful extensions that can do that as suggested by other replies.
I would actually prefer to do so inside by default inside obsidian and when I need to copy paste image into it, I then open using typora. Typora is still my default app for markdown files.
Subscribing to this thread in case, there’s some new and interesting usage by developer-thoughtworkers who use both software heavily
Hi, thanks for the useful information about the plugins for vsc. After a glimpse over the Foam and the Dendron, I’m wondering the difference between these two plugins.
Hi, I’m no expert on either of them. There’s also Memo I think. I just installed them to look.
My impression is that Foam is directly trying to offer similar functionality to Roam, but with markdown documents. It’s going down the block route with quite a complex UID system.
Dendron is different and trying to have more of a hierarchical structure to notes but also having the links.
Foam has a degree of first mover advantage in the VSCode space.
Those I’ve seen commenting that they prefer one or the other tend to have clear preferences. Many Dendron users appear comforted by the use of folders.
I wish that it was possible to use the Obsidian MD editor on MD notes external to a vault. That could be through stand alone “Obsidian Lite” app, or via an Obsidian VS Code plugin.
The need for this is that I have too many notes for them to fit into one, or even four vaults (without performance grinding to a halt), so invariably I also have lots of MD notes (not necessarily PKM notes, but just general stuff) living in my macOS file system (outside of the vaults) that I need to view/edit now and again. At present I use VS Code to do this to avoid having to introduce another MD editor (like Typora) into my workflow, but it’s jarring moving between the two editors.
Of course, this is a workaround until I can just shove all my 40K notes into one Obsidian vault and it work with the lightening speed that I currently enjoy with Obsidian.
I do wish obsidian had a lot of the text-editing niceties of vs code - but it’s understandable given the scope of both apps. I have faith that many of these will come in time. The speed of development in obsidian is impressive.
The Open With plugin for Obsidian is excellent, and has the advantage of being able to open files from your vault in multiple applications, including but not limited to VS Code.
There are a few things that I like about VS Code more than Obsidian, so I was initially on the hunt for Obsidian plugins to make it feel more like what I wanted. That seemed to be a dead end, so then I was hoping for the same thing as the OP. That’s also clearly not an option, but in the end I found that I can make VS Code do enough things like Obsidian that it’s a better option for me. I’m sad to say that I’m going to bid Obsidian farewell for now, but I’ll check back in on occasion and see if the situation has changed. It really is a fantastic tool. This is helpful if anyone wants to go the same route: Suping Up VS Code as a Markdown Notebook — Andrew Kortina
For people who want to keep Vscode as their work environment, i suggest to give Dendron a chance:
Just open Dendron as your workspace and add your obsidian vault to it.
Obsidian could be a simple ide, but it is better suited for pkm. Not to argue with sb, but did you notice how different and much more complex an ide, especially “Vscode” is?
true, Dendron is no longer being actively developed, but this does not mean that this plugin is broken. Over time, it may become obsolete because of better plugins for VSCode. But Dendron is ok if sb wants to stay with VSCode (and i understand that, as i use VSCode almost daily) i think it is a good suggestion.
True, although Foam, which AFAIK is still an active project, might be a better bet. Even though the docs say it was inspired by Roam, Foam appears to be based on plain .md files like Obsidian rather than blocks in an outline like Roam and Logseq.
