5 ms·

my initial reaction, half OT: Ooof, random "ASCII" (actually: Unicode) art & dev-chosen colors, my bane of the "modern" CLI applications. That drawing you like

my initial reaction, half OT: Ooof, random "ASCII" (actually: Unicode) art & dev-chosen colors, my bane of the "modern" CLI applications. That drawing you like? Doesn't work for me, give me the raw output please. Those colors you love? Aside of red-green weakness being the most dominant factor, what you're really doing is trying to set things apart, connotating color with semantics as well. It's nice this works fine on your white-on-black terminal. Have you tried this on a white-on-firebrick terminal? Yellow-on-green? Or anything else than _your_ "normative" setup? Man ... Also not sure the information presented is adequate. E.g. consider commit 76(2941318ee1) - jj makes it look like that was committed to that repository, while it was done to another. The git presentation looks more spot-on (for that particular commit, while the rest of the display is just a mess - ASCII art that does not add semantics, random colors); also where is 1e7d displayed in jj's output? Why is jj's order different? I remain unimpressed by both UIs. " Create a file at ~/.jjconfig.toml" ... $XDG_CONFIG_HOME ? When is that working copy committed? When I run jj? Why bother, when it's not working asynchronously and automatically? And if you commit working copies, do you sync under the hood with stuff the other folks you collaborate with? If not, why bother? Oh nice, a command to fix "stale" workspaces.. how about you don't let workspaces go stale? This may all seem to make sense to git-minded people, given the comments here. To me, neither jj nor git make sense (as fossil-minded person who has to work with git), so shrug enjoy.... ..but please fix that ASCII Art and Color Stuff, thank you very much.

toastal 3y ago
I don’t mind color, but pushing beyond the 16 colors is often a stretch without a very specific use case & bound to lead to a lack of legibility for some unless both foreground & background are defined—which has a tendency to look just as bad in a terminal. Similar issues happen with CSS when folks define color but not background color. But the one CLI trend that annoys me is using Emoji terminal. I often find their colors and shapes to be too distracting, commanding too much of the visual hierarchy of output. They also have a tendency to kind of fall apart when some characters or combinations of characters are missing or they no longer line up with the monospace output. A big part of CLI output is being able to scroll through the logged output, but the Emoji actually make visual scanning more difficult.
alrs 3y ago
Does it honor NO_COLOR? If not, then I have https://github.com/alrs/nofun https://github.com/alrs/nofun
cannam 3y ago
> It's nice this works fine on your white-on-black terminal I was curious about this as well, as I found the images in the README a bit hard to read. In fact the program itself seems to use quite sensible colours in my white-background terminal, and it also respects the NO_COLOR environment variable.
- ephaeton 3y ago
  I often use 5%-black-on-90%-white (and vice versa) and various colored setups that bear semantics to me (like work context, for example, authenticated user, preferred REPL, ...) and as soon as you leave a monochrome world, those colors tend to break down completely. But, TIL about NO_COLOR!
rslabbert 3y ago
All the colours can be adjusted or turned off entirely in the config. [1] A number of different graph styles are supported [2], and failing that, you can completely customise the output template [3] $XDG_CONFIG_HOME/jj/config.toml is supported, that's where I keep mine. The working copy is updated whenever you run jj by default, but watchman is also supported (recently added). [4] In my experience, the command to fix the stale workspaces only needs to be run in exceptional cases where a bug got triggered and a command failed to complete or if you're doing manual poking around. It's a mindset shift, but it's well worth it in my opinion. [1] https://github.com/martinvonz/jj/blob/main/docs/config.md#ui-settings https://github.com/martinvonz/jj/blob/main/docs/config.md#ui... [2] https://github.com/martinvonz/jj/blob/main/docs/config.md#graph-style https://github.com/martinvonz/jj/blob/main/docs/config.md#gr... [3] https://github.com/martinvonz/jj/blob/main/docs/templates.md https://github.com/martinvonz/jj/blob/main/docs/templates.md [4] https://github.com/martinvonz/jj/blob/main/docs/config.md#filesystem-monitor https://github.com/martinvonz/jj/blob/main/docs/config.md#fi...
necauqua 3y ago
Wow, you really just looked at a screenshot, got mad, and then went to write this shallow hate message. > my bane of "modern" CLI applications Ok boomer, I guess you're also a Rust hater too - because I love that every last CLI written in Rust is not garbage because clap is so good and so ubiquitous All the colors and unicode graph can be configured and disabled through config and CLI flags, and the default pager is less which supports NO_COLOR and piping and everything else that less does. It literally has an extensive template system as one of the features to make the log output ANYTHING you would want: adjust some colors that you hate? sure (also there's a config for color names that are used in templates, for colorblind or contrast adjustments etc) add/remove/adjust some info (that you hate)? sure just list full commit ids to be machine-readable that match some revset? - absolutely Man, why do I feel so second-hand embarassed from reading this dumb ignorant reply, lol

toastal 3y ago

I don’t mind color, but pushing beyond the 16 colors is often a stretch without a very specific use case & bound to lead to a lack of legibility for some unless both foreground & background are defined—which has a tendency to look just as bad in a terminal. Similar issues happen with CSS when folks define color but not background color. But the one CLI trend that annoys me is using Emoji terminal. I often find their colors and shapes to be too distracting, commanding too much of the visual hierarchy of output. They also have a tendency to kind of fall apart when some characters or combinations of characters are missing or they no longer line up with the monospace output. A big part of CLI output is being able to scroll through the logged output, but the Emoji actually make visual scanning more difficult.

alrs 3y ago

Does it honor NO_COLOR? If not, then I have https://github.com/alrs/nofun https://github.com/alrs/nofun

cannam 3y ago

> It's nice this works fine on your white-on-black terminal I was curious about this as well, as I found the images in the README a bit hard to read. In fact the program itself seems to use quite sensible colours in my white-background terminal, and it also respects the NO_COLOR environment variable.

ephaeton 3y ago
I often use 5%-black-on-90%-white (and vice versa) and various colored setups that bear semantics to me (like work context, for example, authenticated user, preferred REPL, ...) and as soon as you leave a monochrome world, those colors tend to break down completely. But, TIL about NO_COLOR!

rslabbert 3y ago

All the colours can be adjusted or turned off entirely in the config. [1] A number of different graph styles are supported [2], and failing that, you can completely customise the output template [3] $XDG_CONFIG_HOME/jj/config.toml is supported, that's where I keep mine. The working copy is updated whenever you run jj by default, but watchman is also supported (recently added). [4] In my experience, the command to fix the stale workspaces only needs to be run in exceptional cases where a bug got triggered and a command failed to complete or if you're doing manual poking around. It's a mindset shift, but it's well worth it in my opinion. [1] https://github.com/martinvonz/jj/blob/main/docs/config.md#ui-settings https://github.com/martinvonz/jj/blob/main/docs/config.md#ui... [2] https://github.com/martinvonz/jj/blob/main/docs/config.md#graph-style https://github.com/martinvonz/jj/blob/main/docs/config.md#gr... [3] https://github.com/martinvonz/jj/blob/main/docs/templates.md https://github.com/martinvonz/jj/blob/main/docs/templates.md [4] https://github.com/martinvonz/jj/blob/main/docs/config.md#filesystem-monitor https://github.com/martinvonz/jj/blob/main/docs/config.md#fi...

necauqua 3y ago

Wow, you really just looked at a screenshot, got mad, and then went to write this shallow hate message. > my bane of "modern" CLI applications Ok boomer, I guess you're also a Rust hater too - because I love that every last CLI written in Rust is not garbage because clap is so good and so ubiquitous All the colors and unicode graph can be configured and disabled through config and CLI flags, and the default pager is less which supports NO_COLOR and piping and everything else that less does. It literally has an extensive template system as one of the features to make the log output ANYTHING you would want: adjust some colors that you hate? sure (also there's a config for color names that are used in templates, for colorblind or contrast adjustments etc) add/remove/adjust some info (that you hate)? sure just list full commit ids to be machine-readable that match some revset? - absolutely Man, why do I feel so second-hand embarassed from reading this dumb ignorant reply, lol