jotaen

It’s cool that you’ve launched a native app for TaskTXT. I think the UI concept is terrific, as it let’s me see and manipulate my plain data, but then also dynamically amends it with useful extra info…

I realised that I made a small mistake in my code sample above, but I can’t edit the post anymore. It should have been: [x] Example item [ ] Subitem [ ] Another Sub-Sub I…

> It's optional, so I'd assume it's for people who want to start the sentence from same aligned column. Yes, visual alignment is the first purpose; the other is if you want to sort y…

You’d be free to format your titles like that, if you prefer. The only restriction for titles is that the line cannot start with whitespace or `[`. Not sure what you mean by the text wrapping bit, but…

I’ve tried to implement the item nesting in the [x]it! Sublime Text plugin. The problem there was that I didn’t manage to implement strict rules for subitems. If you consider the following example: …

Thanks for your feedback. I think for the status characters there are a lot of imaginable variations and preferences. In the end, I thought that restricting the spec to a single character per status w…

[x]it! files are UTF-8 encoded by default. The predefined syntactical elements (such as checkboxes, priorities, or due dates) are composed from ASCII characters, but outside of that (e.g. in item desc…

Thanks for your detailed notes, I’ll look through your links. Just to clarify for context, the “letter” definition is only relevant for tags, so outside of #tags (in item descriptions, or group titles…

With [x]it!, lexicographic sorting of lines works as well, as long as you stick to the following rules: - Write due dates first (if you use due dates) - Pad your priority with dots (if you use priorit…

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 …

Per specification, [x]it! files must be UTF-8 encoded. (See https://github.com/jotaen/xit/blob/main/Specification.md#fil... ) You can use Unicode characters in item…

> It would be simpler to just use the ISO date format. [x]it! is supposed to be edited (editable) by hand, and from an end-user perspective, I personally find ISO-8601 in its entirety relatively co…

Thanks for sharing your notes. Nesting of items is not supported, although the idea has come up. It’s on hold right now – that’s mostly due to practical reasons, because it’s relatively hard to implem…

The maintainer wrote something about this here: https://support.hogbaysoftware.com/t/where-is-taskpapers-fil... …

I’ve never used TaskPaper, but the capabilities of the data format look somewhat similar. I think the difference is primarily a philosophical one: [x]it! is a file format with a formal specification t…

For reference, this is the discussion around subitems / nesting: https://github.com/jotaen/xit/discussions/2 As mentioned in that ticket, I’m still reluctant to ad…

rodo looks quite cool! It’s interesting to see how common the syntax is with these formats, so there seem to be “natural” patterns. [x]it! doesn’t try to be opinionated about what you use it for. So y…

Creator here. [x]it! was deliberately designed as a strict data format that stands on its own, as I think this makes it easier to create tooling and work with the data programmatically. However, I thi…

Maybe worth noting that the 9-euro ticket is only for local public transport, such as buses, subways, or regional trains. Only the latter (RE) are operated by Deutsche Bahn, whereas buses and subways …

Same here: I regularly take long-distance train rides throughout all Germany, both with ICE (the fast one) as well as RE (the regional one), and for me it works smoothly for the most part.

Nesting is currently being worked on https://github.com/jotaen/xit/discussions/2 , as there are some questions to be figured out first. (Note that the [x]it! specificati…

Yes. What I did is try to choose default (common) scopes that have a high chance of being coloured the way I want, e.g. for the `[x]` token I use `markup.inserted` which is for markup diffs, so it sho…

I’m seriously considering to make that mandatory via the spec. :D

Have you also tried checking all the items?

I didn’t include nesting in the first edition of the draft, because there might be some implications with it and I was curious for feedback on this. https://github.com/jotaen/xit&…

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 us…

You can have lexicographic ordering with [x]it!, as long as you stick to a specific structure, which is: - Write due dates first - Pad your priority with dots - Don’t use line breaks within descriptio…

Yeah, I agree – as great as a separate file spec is, it’s only half the story without tools that provide useful functionality on top of it. For my current purposes, it’s syntax highlighting that makes…