I ❤ minimalism and suckless™ philosophy. See also plan9 and cat-v.

• outliner: filesystem
  • a folder can group ideas related to a topic.
  • it can contain other files/folders.
  • a link can create lightweight reference.
  • indirections can create complex graphs.
  • metadata like bookmarks, mrus etc., are also files/folders.
  • fuzzy search can be used to quickly bookmark.
  • viewing, editing, opening, etc., can be delegated to shell scripts.
  • bind data + operations like oop.
• explorer: vifm
  • vi-like tui for outline operations.
  • everything is clickable.
  • everything opens in a new dwm window possibly st.
• editor: vis
  • vi-like bindings with structural regexp.
• window-manager: dwm or bspwm
• terminal: st
• automation: rc
• ide: plan9port + suckless

[The above information can be represented as an outline.]

Autogenerate outlines (like zoxide).

URLS can be opened via browser, but what about reverse?

Cooler FS'es?

Need to see if everything: window, process etc., can be mapped to an outline. For example, pid 1 has a window pid/win/1 and output pid/out/1/<outline>.

If interprocess communication happens via files (like Plan 9), such outlines can integrate well with the environment, allowing for enhanced scripting possibilities without creating new data-structures. A file-system can actually store lists, dictionaries, trees etc.

• oberon (a2)
• plan9[port] (acme, rc, rio)

• erlang
• es
• ghc
• io
• lua
• python (pypy)
• scheme (chez)
• smalltalk (cuis)
• tcl (tk)

• bindfs
• docker
• ffmpeg
• fonts (consolas, dejavu, go, noto)
• gvfs-mtp
• mat2
• sysstat
• xclip
• xdotools
• xorg-server-xephyr
• xorg-xhost
• xpra
• xsel
• xserver-xorg-input-synaptics
• xshkd
• xss-lock
• xtitle

• abduco
• dvtm
• fzy
• git (cola, gui)
• gnu-netcat
• jj
• lemonbar
• maim
• meld
• mocp
• mpv
• qutebrowser
• recoll
• scid
• shellcheck
• slock
• socat
• st
• strace
• tabbed
• tgpt
• vifm
• vim
• vis
• xournalpp
• yt-dlp
• zathura (djvu, ps)
• zoxide