kdheepak

I see taskwarrior-tui being mentioned a couple of times in this thread. If anyone is interested in why or why not to use taskwarrior-tui, the biggest advantage of taskwarrior-tui are 3 fold:

1. Previously you would have to type `task report`, `task add …`, `task report` again to see how your priorities have changed. With the TUI you can get live feedback.

2. By default, the TUI comes out of the box with intuitive (in the author’s opinion) single-key press actions that map to various taskwarrior subcommands on single or multiple tasks.

3. The UI lets you as a user run 9 custom bash scripts as shortcuts that can extend features without changing the source code.

There are a few things not so good about it though.

1. Everything is accomplished by shelling out to the taskwarrior `task` cli, which has some nuances in parsing command line arguments, and all the corner cases haven’t been ironed out.

2. The calendar feature, the contexts feature, styling features etc are all underbaked or incomplete.

3. This was the author’s first Rust project and definitely needs some refactoring love.

The author definitely recommends reporting any issues or feature requests. He’s also extremely appreciative of the fact that people use the tool and advocate it to other people on threads like this!

Source: I’m the author :)

In my opinion, one argument for internally representing `String`s as UTF8 is it prevents accidentally saving a file as Latin1 or other encodings. I would like to read a file my coworker sent me in my favorite language without having to figure out what the encoding of the file is.

For example, my most recent Julia project has the following line:

    windows1252_to_utf8(s) = decode(Vector{UInt8}(String(coalesce(s, ""))), "Windows-1252")

Figuring out that I had to use Windows-1252 (and not Latin1) took a lot more time than I would have liked it to.

I get that there's some ergonomic challenges around this in languages like Julia that are optimized for data analysis workflows, but imho all data analysis languages/scripts should be forced to explicitly list encodings/decodings whenever reading/writing a file or default to UTF-8.

Thanks for posting the donation link and the reminder, I've made a donation as well.

Vim has shaped so many aspects of my professional life; I'll forever be grateful to Bram for his work and contributions. Rest in peace, Bram.

I just want to share my appreciation for the maintainers of his package. Sometimes I’m amazed how much work people put into a corner of the internet just because they care.

I’m very excited for this release! Congrats to everyone that worked so hard on this and the language in general!