#PKM proprietary/online products: *exist*
#Obsidian users: "better keep notes local and in a standard format!"
#Logseq users: "right, but also using #FOSS tools is important for the same reasons, Obsidian is not FOSS, on the other hand there is this new app called Logseq..."
Obsidian users: "it's nice that everyone can use what suit them the best :)"
🤷🏻♂
@post does FOSS software produce better plaintext markdown files?
Is this supposed to be a provocation? 🧐
Just in case you don't know: Logseq stores data in Markdown files just like Obsidian but they are standard Markdown indented lists using dashes.
To some extent one can even use Logseq and Obsidian with the same folder.
It's up to the user to avoid special syntax and this is true both in Logseq and Obsidian (the latter's strenght is the ecosystem of plugins that often adds their own syntax).
Also notice that `#hashtags`,`[[wikilinks]]`, and YAML headers to store metadata are not standard Markdown.
@post I’m not sure what we’re arguing about? I know what Logseq is.
Then maybe you don't what FOSS is?
@post it would take 5 minutes with standard *nix tools to reformat and strip out or convert tags between markdown syntax recursively in a vault.
Obviously tags from obsidian plugins aren’t going to render in MarsEdit.
If you mean Unix tools, those are for plain text, not for Markdown that has tables, indented lists etc.
On the other hand #Logseq not only provides handy HTTP/JSON API, but you can also access the AST with command line tools (using Babashka) that basically means the files are already parsed for your convenience and you can use whatever other tool including the Unix ones to interact with it.
Here there is an example of command line tool (it doesn't depend on Logseq being running nor being installed):
@post I'm talking about sed, awk, grep, tr... etc.
And yes, for markdown that has anything because markdown IS plaintext - even the bullet points.
You're just wrong about that. Markdown is plain text, even the bits that aren't english words. It's not compiled, it's not binary - it's ascii text and it can be manipulated with standard tools if you know what you're doing.
But I get it, you like logseq. That's cool.
OK let's see your Bash script where you reorder the elements of a Markdown table in alphabetical order using sed, awk, grep etc.
It seems to me that it is you who like Obsidian too much to admit FOSS is as much important as standard formats.
Also people who like Unix tools should be happy to see what you can do with Babashka and Logseq's AST.
@post sure. Strip the delimiters, split the fields into an array - sort it, and then print it back with the delimiters.
It’s ok. You can like logseq.
I have nothing against it.
You are the one seriously replying to a joke 🤷🏻♂
You didn't tell me how you located the target table in a MD file that contains something else and how actually replace it with the new one. It's a program on its own, not just some piped Unix commands.
It would have been better if you said "there Markdown editors other than Obsidian and even Markdown command line tools and libraries".
The fact that you mentioned Unix tools for plain text files suggest that you are talking in a theoretical way with no actual practical experience with parsing Markdown. Maybe you don't even know what an AST is.
No offense, but you're taking the stereotype of my joke to a new level.
@post dude. This is a stupid argument.
Can I format a markdown table and sort it in bash, yes absolutely. I worked as a linux engineer for 15 years doing stuff just like that.
I’d use python myself, but absolutely could be bash… in probably < 10 lines.
But the reality is that I would never put a table in markdown in the first place. I’d use a database like a grownup.
I don’t actually give a shit about your work or what tools you use to do it.
Please address whatever issue you have before joining a social platform, bye.
