xit-sublime
xit
xit-sublime | xit | |
---|---|---|
5 | 24 | |
19 | 1,034 | |
- | - | |
3.7 | 0.0 | |
7 months ago | 4 months ago | |
Python | ||
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
xit-sublime
- A plain-text file format for todos and check lists - [x]it!
- XIt is a plain-text file format for todos and check lists
-
Show HN: A plain-text file format for todos and check lists
That’s how it works in Sublime, yes. You have a regex-based parsing engine that you configure via a YAML file, and there you assign scopes to the tokens.[1]
As a default, the [x]it! Sublime Package uses the available default scopes. The user can choose to override the associated colours in their local settings.[2]
[1]: https://github.com/jotaen/xit-sublime/blob/main/xit.sublime-...
[2]: https://github.com/jotaen/xit-sublime#syntax-highlighting--c...
xit
-
My productivity app is a never-ending .txt file
I use the same system but with highlighting/formatting of https://xit.jotaen.net
I even learn how to create a plugin for the IntelliJ IDEA and created one for highlighting this format (love idea hotkeys and workflow).
- Staff / Principals / EMs - How do you organize your work and keep track of the multitude of streams, docs, notes etc?
- Ask HN: How you maintain your daily log?
-
Show HN: Tuido, a Terminal Todo List
This is my personal todo app, which I made a while back after the original https://xit.jotaen.net/ post. tuido is written in go, with the bubbletea tui framework.
My daily workflow involves creating YYYY-MM-DD.md and taking notes, many of which are effectively low-level todos that fall below the threshold for more public or involved issue trackers. Problem was that these half-hazard todos weren't tracked at all.
After seeing the [x]it spec, it seemed clear that a little tooling could fix this. I've been reasonably happy with it.
-
A plain-text file format for todos and check lists
There currently are a bunch of editor plugins and one CLI tool. You find a collection of tools (all third-party) linked from the project website: https://xit.jotaen.net
- It: A plain-text file format for todos and check lists
- Show HN: 一个纯文本文件格式的工作日程和检查清单 (Show HN: A plain-text file format for todos and check lists)
What are some alternatives?
todo.txt - ‼️ A complete primer on the whys and hows of todo.txt.
logseq - A local-first, non-linear, outliner notebook for organizing and sharing your personal knowledge base. Use it to organize your todo list, to write your journals, or to record your unique life.
nb - CLI and local web plain text note‑taking, bookmarking, and archiving with linking, tagging, filtering, search, Git versioning & syncing, Pandoc conversion, + more, in a single portable script.
vimwiki - Personal Wiki for Vim
neorg - Modernity meets insane extensibility. The future of organizing your life in Neovim. [Moved to: https://github.com/nvim-neorg/neorg]
todo.md - TODO.md file format - todomd.org
GitJournal - Mobile first Note Taking integrated with Git
orgmode - Orgmode clone written in Lua for Neovim 0.9+.
ConsoleJournal
orgajs - parse org-mode content into AST
zim-desktop-wiki - Main repository of the zim desktop wiki project