rxvt-unicode | Git mirror repo

short: no, you can't

longer: I pointed out in Rebinding CTRL-ALT-[C|V] to CTRL-SHIFT-[C|V] in URxvt >= 9.20 that the binding for these is essentially hardcoded in urxvt without an easy way to change them (aside from external scripts or modifying the program itself).

TL;DR: use a different user (e.g. hadoop) instead of root.

I found the solution but not the deep understanding on what is going on. Despite how sad I can be, here's the solution I found:

Running with root user:

I am not sure if you can force the rich console from a gradle script, as the detection happens likely before the script is interpreted.

NativeServices class provides the integration with the console. If you look at the source code, there are two messages possibly printed in log:

Native-platform terminal integration is not available. Continuing with fallback.

Unable to load from native-platform backed ConsoleDetector. Continuing with fallback.

The latter might give you more information why. Try running the gradle script with --debug. You will likely find out that you are missing a native library that is either not available in cygwin or it is, but is not on library path.

I believe it works when you specify the rich console from the command line, because gradle forces the colours even though the console doesn't indicate it supports them.

Does it work if you don't use the cygwin console in Windows native command line or maybe GitBash?

There is a workaround how you can make this work. You can create an alias in cygwin that will always add the --console=rich.

If you are using gradle wrapper, you can edit the gradlew script and add the command line parameter. To make it automated, you can change the wrapper task to alter your script in the doLast part.

You might need to install Term::ReadLine::Perl or Term::ReadLine::Gnu as well. Try something like:

urxvt is not xterm, so $TERM should be rxvt-unicode and not xterm-256color.

I didn't figure this out right until the very end of typing my question, when I was adding the urxvt configuration. I suppose thinking about what information might be relevant to put into a SO question is can lead to solving your own problem. Rather than deleting everything, I thought I might as well post nonetheless and perhaps it will be useful to someone else out there.

The thing is, I added that env setting a long, long time ago when I was experimenting with Arch Linux and urxvt for the first time. I must admit, I did not really spend too much time thinking about it. I recall all I cared about at the time was having unicode characters, fonts and colors displayed properly (in addition to a pretty looking color scheme). Setting $TERM to xterm-256color seemed to work at the time, and in all this time using the system, it continued seeming to work, until today. There were glitches here and there, of course, and perhaps they were the result of this. Then again, perhaps they were due to something else. I have to say I am rather amused at how silly and simple the problem turned out to be.

It is also interesting to see the strange behavior this error led to. I'm still curious to know why exactly my mistake leads to the behavior I document in the question. I might return to this just for kicks when I have some time.

EDIT

This exact issue is mentioned in ncurses' FAQ, as pointed out by Thomas Dickey.

..., in mid-2017, an update to the xterm terminal description added the ECMA-48 REP (repeat character) control. It was part of xterm since January 1997, but a terminal description using the feature was part of xterm only (not ncurses).

Terminal emulators that use TERM=xterm but do not support this xterm feature exhibited bugs once this feature was introduced to ncurses. rxvt was unaffected since it does not use TERM=xterm, or rather, as it should not use TERM=xterm, as I had been doing.

REP is used to indicate that the preceding character in the data stream, if it is a graphic character (represented by one or more bit combinations) including SPACE, is to be repeated n times, where n equals the value of Pn. If the character preceding REP is a control function or part of a control function, the effect of REP is not defined by this Standard. REP - ECMA-048

I should also mention that the ncurses FAQ includes an excellent discussion concerning why people tend to use TERM=xterm, and why they should not, straight from the horse's mouth!

You should probably check your **.Xresources/.Xdefaults ** the problem can be from there . termite uses ~/.config/termite/config and Urxvt uses .Xresources .