Projects tab similar to taskwarrior summary

[aniketgm]

This is more of UI request

Description

When I run taskwarrior, this is what I get (screenshot below, tw is my alias for task command)

And this is what I see the Projects tab in taskwarrior-tui.

Expectation

Is there a way to get the Projects tab similar to what taskwarrior is displaying (filled rectangular boxes instead of '=') ?

Version

[kdheepak]

Currently taskwarrior-tui just runs task summary as a process and puts that output into the view:

taskwarrior-tui/src/pane/project.rs

Lines 121 to 125 in 5e9c22a

	let output = Command::new("task")
	.arg("summary")
	.output()
	.context("Unable to run `task summary`")
	.unwrap();

I'm surprised it is showing anything different in this case.

[aniketgm]

Currently taskwarrior-tui just runs task summary as a process and puts that output into the view:

I'm not aware much about Rust. From what I can understand, the .output() might be doing something internally that is converting the filled rectangles to '='. If not the unwrap() function. Correct me if I'm wrong.

[kdheepak]

.output() just reads the stdout of running task summary, and .unwrap() is a rust way of converting a result into a value (think try: parse_to_string(cmd.output()); else: raise Exception("Raise an error and stop the application") in Python).

I think either

1. taskwarrior's task is behaving differently when called in the context of Command::new(task).arg(summary), or
2. there's some terminal setting that's causing task summary to behave differently in taskwarrior-tui

I'll try to replicate the issue on my end, and that will help give me some idea as to what is going on.

[flugsio]

This is in taskwarrior, it outputs = and no colors when stdout is not to a terminal, for example task summary | cat, it's common to provide different features for TTY/non-TTY

It can be overriden like this task rc._forcecolor=1 summary https://github.com/GothenburgBitFactory/taskwarrior/blob/8dd29e0a8a2640eecc9b5510a9d252540b2fd146/src/Context.cpp#L268

It could also be faked, here's a random crate, but that could cause issues. For example if the process expects the user to give some input, it could for example provide an pagination interface and never terminate.

edit:
here's what it looks like when putting _forcecolor=1 in ~/.taskrc. The ansi color escape codes would need to be parsed

[aniketgm]

here's what it looks like when putting _forcecolor=1 in ~/.taskrc. The ansi color escape codes would need to be parsed

Hey, no pressure, do we have any changes for this ? As mentioned by @flugsio , the ansi codes would need to be parsed.
@kdheepak, I was looking at ansi parser yesterday and found this ansi-parser crate. Might help.