251–260 of 282 posts
Earlier quoted context omitted.
I just access my markdown files from Obsidian through nextcloud. When I'm on my phone I just use a simple markdown editor, when I'm on my PC I use Obsidian.
Do you use any plug-ins for that? Obsidian tells me it only supports Obsidian Sync and iCloud out of the box.
The killer app for markdown would be a collaborative editor that displays the raw markdown and formatted markdown side-by-side and makes both sides editable. Tech people can use `#` and `*` on one side for formatting, product people can use normal text-editor buttons like "header1", "italics", etc.
Earlier quoted context omitted.
The nextcloud Markdown editor shows a live view while you edit... Its called "Notes"
You know what has live view all the time? RTF. What’s wrong with WYSIWYG?
Indeed, I also realized that bookmarks are worthless on the long run. When choosing a note taking / knowledge management app, the main decision point was if it has a Firefox extension that can capture a web page into markdown and automatically save into my notes. I used to use Joplin, lately switched to Obsidian. Both offer this functionality.
What drove you to switch to Obsidian? I'm considering it myself and have been playing around with Obsidian the past couple of days after about 4 years of Joplin, 2 of which with a self hosted Joplin Server. I'm tired of basic features being missing and extensions breaking because they're no longer maintained, and basic features like linking between notes while writing a note not being built in.
During my long sabbatical, I wanted to take notes on my phone, a LOT. Joplin sucks at that, clumsy, non-user friendly android client.
Tried obsidian (first on mobile) and it is superb. I had to install a couple extensons (S3 sync, "Ink" for drawing with a pen), and it just works. It's so good, I sometimes even edit tables on my phone. With Joplin, note taking on my phone was just dumping thoughts in random formats to it and later fixing it on my desktop.
Like Joplin, Obsidian also has a Firefox extension to capture a web page I to markdown.
So after a couple days of trial, I realized that all the features Joplin has, obsidian has it too, with a much better (and snappier) UX on both my Linux desktop and Android. The only thing I wish for of it was Open Source. But oh well, I'm not dogmatic about that anymore
Earlier quoted context omitted.
> Making * always be used for bold This is probably to support potential ambiguities and intraword emphasis e.g. underscore is a common pseudo-space so doesn't support intraword use but * does e.g. is_not_italic this*is*italic. I recently implemented a commonmark parser for emphasis. Holy shit it's painful. I regret doing it but it became a battle I refused to surrender. It's way harder than I expected because of the…
> This is probably to support potential ambiguities and intraword emphasis e.g. underscore is a common pseudo-space so doesn't support intraword use but * does e.g. is_not_italic this*is*italic. That seems like a legacy spec mistake they had to adhere to. I'd expect this_is_italic to work and for _ literal usage to require is\_not\_italic
I can see it as a choice from the "plain text first" philosophy i.e. the things you typically write in plain text should not need escaping. My intuition pump is that you can copy-paste an email into .md without edits or surprising rendering.
As such, it's doomed to never satisfy everyone. Personally I never use intraword emphasis and I typically only have underscores in non-code names i.e. `this_is_normally_code`.
Also, as an old person, I will tell you that 1) I got my first personal computer in 1979 and have been trying to keep my bon mots archived ever since. I have tried a million things and have learned one key lesson: It's not really worth it. I literally have a footlocker filled with old disk drives (remember, since 1979!) and I have never, ever gone back more than a few years, hell, more than a year. Now that disks are…
Earlier quoted context omitted.
In my defence, the comment I was replying to mentioned "renderers" and "converters". Furthermore IMHO, any text editor is a Markdown reader. If you want it formatted as is it were "markup" then might I suggest converting to e.g. PDF using Pandoc and then using one of the many capable viewers.
Noted, re the other comment. But... come on. You might just as well say any text editor is a browser, because you can technically read HTML with it. You can also technically read Word documents with a text reader.
Earlier quoted context omitted.
You can use this bookmarklet to create new pages: data:text/html, then save them as HTML-files. You can use another bookmarklet to turn existing pages or files into editable pages.
You can't easily take text and make it red that way, only edit the existing content.
Earlier quoted context omitted.
Interesting. Why not HTML? Browsers have native basic WYSIWYG editing built in, and almost every screen we look at is nowadays HTML, including the code editor. On a ` element, calling document.execCommand('bold') will make selected text bold in WYSIWYG mode. See https://jsfiddle.net/z0umpb3x/12/ for the concept. The main idea here is that I don't want to know any syntax like RTF, nor I want to use any tools.
I'm not the parent commenter but I'm going to guess because HTML is horrible at WYSIWYG. If your editing tool changes or if your switch editors, they will all botch your HTML anywhere you make edits. RTF is basically "it just works," very much like "Microsoft Word Light."
Earlier quoted context omitted.
RTF isn’t a better option than MD, plaintext is. We start with the premise that we are talking about plain text, as in plain text, texts. But pretty soon we are into colours, then maybe images and videos, and then what all not. But MD still is closest to plaintext because in most cases MD (or a similar scheme), even when not rendered, can be read easily in its plaintext formatting.
Honestly plaintext has a pretty bad record as a format, with all of the UTF-16, Latin-2, Shift JIS, and so on. I’d suggest paper, or for true archival storage, parchment and stone.