Bug#932375: RE: RE: Re: Bug#932375: UXTerm: reversion of colors won't work

2019-07-20 Thread Md Ayquassar

I know about the -rv option. It's one-off, i.e., you have to provide it again 
and
again. As for .xinitrc, I thought that wayland doesn't source it on startup.

 > > Anyway, having said all that, what's the "official" way to have the
 uxterm
 > > default colors *automatically* white-on-black now?
 >
 > well... it's not a bug in xterm,
 > but rather a deficiency in packaging or configuration.

 The command-line option -rv is the easy way to turn on reverse-video:

 -rv This option indicates that reverse video should be simulated by
 swapping the foreground and background colors. The
 corresponding resource name is reverseVideo.

 and if I wanted to make my .xinitrc more portable, I'd use -fg and -bg


Bug#932375: RE: RE: Re: Bug#932375: UXTerm: reversion of colors won't work

2019-07-20 Thread Thomas Dickey
On Sat, Jul 20, 2019 at 06:01:08AM +0300, Md Ayquassar wrote:
> Now properly formatted such that the html output is ok.
> 
> $ echo $XDG_SESSION_TYPE
> 
> wayland
> 
> $ echo $DESKTOP_SESSION
> 
> gnome
> 
> $ cat /etc/X11/default-display-manager
> 
> /usr/sbin/gdm3
> 
> After taking a look at the reason why they dropped support for loading
> .Xresources by default (cf. 
> https://bugzilla.redhat.com/show_bug.cgi?id=1225384),
> I decided to test whether that old reason is still valid. It is not:
> 
> $ cat ~/.Xresources
> 
> UXTerm*reverseVideo: true
> 
> $ time xrdb -merge ~/.Xresources
> 
> real 0m0,018s
> 
> user 0m0,012s
> 
> sys 0m0,006s
> 
> This time spent is clearly below what a human would need to type in "xrdb 
> -merge
> ~/.Xresources" manually and way below what a human is able to perceive. But
> complaining on this regression might belong to a different bug, I guess.
> Anyway, having said all that, what's the "official" way to have the uxterm
> default colors *automatically* white-on-black now?

well... it's not a bug in xterm,
but rather a deficiency in packaging or configuration.

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature


Bug#932375: RE: RE: Re: Bug#932375: UXTerm: reversion of colors won't work

2019-07-20 Thread Thomas Dickey
On Sat, Jul 20, 2019 at 08:39:00AM -0400, Thomas Dickey wrote:
...
> > This time spent is clearly below what a human would need to type in "xrdb 
> > -merge
> > ~/.Xresources" manually and way below what a human is able to perceive. But
> > complaining on this regression might belong to a different bug, I guess.
> > Anyway, having said all that, what's the "official" way to have the uxterm
> > default colors *automatically* white-on-black now?
> 
> well... it's not a bug in xterm,
> but rather a deficiency in packaging or configuration.

The command-line option -rv is the easy way to turn on reverse-video:

   -rv This option indicates that reverse video should be simulated by
   swapping the foreground and background colors.  The
   corresponding resource name is reverseVideo.

and if I wanted to make my .xinitrc more portable, I'd use -fg and -bg

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature


Bug#932375: RE: RE: Re: Bug#932375: UXTerm: reversion of colors won't work

2019-07-19 Thread Md Ayquassar

Now properly formatted such that the html output is ok.

$ echo $XDG_SESSION_TYPE

wayland

$ echo $DESKTOP_SESSION

gnome

$ cat /etc/X11/default-display-manager

/usr/sbin/gdm3

After taking a look at the reason why they dropped support for loading
.Xresources by default (cf. 
https://bugzilla.redhat.com/show_bug.cgi?id=1225384),
I decided to test whether that old reason is still valid. It is not:

$ cat ~/.Xresources

UXTerm*reverseVideo: true

$ time xrdb -merge ~/.Xresources

real 0m0,018s

user 0m0,012s

sys 0m0,006s

This time spent is clearly below what a human would need to type in "xrdb -merge
~/.Xresources" manually and way below what a human is able to perceive. But
complaining on this regression might belong to a different bug, I guess.
Anyway, having said all that, what's the "official" way to have the uxterm
default colors *automatically* white-on-black now?