ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

Main Area and Open Discussion > General Software Discussion

I'm thinking of going primitive, with discursion into zettelkasten

<< < (101/244) > >>

Dormouse:
Which format is good for what?  [[]] is for internal zettel links, right?  I see []() used more broadly in other applications.  In the zettel context, they should be interchangeable.  Or obsidian should have a feature to deal with the two types.
-superboyac (June 22, 2020, 07:00 PM)
--- End quote ---
Remember Obsidian isn't a zettelkasten program  - it's just capable of being used as one. [[]] is a wiki link, []() is the conventional markdown syntax. Obsidian prefers the former because it's simpler, but can understand the latter.

This whole class of software is rooted in wikis.
Wiki to outliner (Workflowy), pure wiki type outliner to hybrid with multiple outlines (Dynalist), to Roam with bidirectional links and idiosyncratic selections of markdown syntax in its database/documents (some if its syntax taken directly from Dynalist), to Obsidian which uses actual markdown files. The most commonly referred to traditional alternative to the last two is Tiddlywiki and its offshoots.

I haven't used zettlr, but I think it's designed purely zettelkasten and doesn't have the whole setup around bidirectional links?

Dormouse:
I've been very hesitant to commit to zettel because i first want to know the tools I'm going to use.  I think this will work for now.
-superboyac (June 22, 2020, 07:01 PM)
--- End quote ---
Before committing too hard to zettel, it's worth thinking about Andy Matuschak's evergreen notes.
I'm not following either really. I think they have a strong appeal to those who are attracted to a rigid system. I do subscribe to atomicity, though I think there are a variety of ways to achieve it, and I do believe it is important both to think and to record the results of the thinking. And I use a whole variety of links. The problem with thinking is that it takes the time it takes, and insights, leaps and eurekas are only possible when your mind is open rather than on a trail or on a schedule.

Nod5:
brainstorm: plaintext note content hierarchy via indentation

I more and more like the idea of hierarchical notes via pythonic indentation
  with 2 spaces instead of 4, for compactness
  minimal yet very readable in code editor set to show whitespace and fixed width font
  problem: markdown and asciidoc use space/tab indentation for other things
    markdown treats 4 indentation spaces as a code block
    markdown collapses e.g. 3 or 14 spaces to no indentation
      https://stackoverflow.com/editing-help#advanced-lists
      https://stackoverflow.com/questions/40023013/tab-space-in-markdown
    https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/

Any ideas/workarounds on using such compact pythonic indentation effectively in markdown based notes apps/systems?

Comparison examples

1. pythonic indentation (2 spaces)
Note: markdown collapses these indents and shows all on one line if not two suffix spaces.

Sun
  big
  hot
  bright
    https://en.wikipedia.org/wiki/Sun#Sunlight

2. Markdown nested list

- Sun
    - big
    - hot
    - bright
        - https://en.wikipedia.org/wiki/Sun#Sunlight

3. Markdown nested list alternating bullet characters (more compact, but still extra characters)

- Sun
  + big
  + hot
  + bright
    - https://en.wikipedia.org/wiki/Sun#Sunlight

Examples screenshot from VS Code with raw and preview tabs
I'm thinking of going primitive, with discursion into zettelkasten

Wishes unlikely to come true
I wish markdown by default rendered indentation as indentation! For code blocks there is already the three fence ``` prefix/suffix.

I even wish that minus - and plus + at line start (with/without indentation) defaulted to not be interpreted as bullet point list formatting. They should function as list formatting characters only when preceded by a line prefixed with some other character that would start a list. For example a dot . character.

Dormouse:
Wishes unlikely to come true
I wish markdown by default rendered indentation as indentation! For code blocks there is already the three fence ``` prefix/suffix.

I even wish that minus - and plus + at line start (with/without indentation) defaulted to not be interpreted as bullet point list formatting. They should function as list formatting characters only when preceded by a line prefixed with some other character that would start a list. For example a dot . character.
-Nod5 (June 23, 2020, 03:25 AM)
--- End quote ---
You could make them true yourself. Fork an appropriate FOSS project by inserting your preferred changes to syntax and then describe it as GFM, or whatever the original is, with Nod extensions.
When you have enough followers,  you can overwhelm the Canutes involved in agreeing standards.

superboyac:
evergreen notes
-Dormouse (June 22, 2020, 07:57 PM)
--- End quote ---
I am interested...
I went to this siite
https://notes.andymatuschak.org/
(very cool site design btw)
but i don't get what evergreen notes are.  Is there a sample I can see somewhere?  Even zettel, its best to see examples than to figure out the philosophy through the flowery discussions.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version