New answers tagged

0

One way I can get the correct DISPLAY is by querying the DISPLAY variable assigned to gnome-terminal-server with the following cat /proc/$(pidof "gnome-terminal-server")/environ | tr '\0' '\n' | grep ^DISPLAY=


2

You can examine /proc/${pid}/environ. That contains the process' initial environment. Here, $$ is the pid of the running shell. Note also that the variables are nil-character delimited. The -e option to cat will cause it to print non-printable characters (like the nil character), and the sed converts the representation of the nil characters to newlines. $ ...


0

Not sure about GNOME settings but what I do is.. In my KDE setting, I set my extended monitor as Main and set it to extend. So when I have to use only my 2nd screen I switch of the first monitor so, Automatically ,the 2nd monitor becomes the primary and only one. And when I turn on the first monitor. It extends the 2nd one.which is primary. Thank You In KDE ...


1

Automatically detected modes cannot be deleted. Ping developers: https://gitlab.freedesktop.org/xorg/xserver/-/issues/353 You can try creating and using a custom EDID file for your monitor: https://wiki.archlinux.org/title/Kernel_mode_setting#Forcing_modes_and_EDID


0

Autostart script solution Before you start reading, make sure, that in your Power Management preferences the display is set to Never to be put to sleep when inactive. So, I did a lot of digging, and thanks to the official forum (source link) I got my answer: Place the below script to this location: ~/.config/autostart/ Script: #!/bin/sh sleep 10 &&...


0

In my case, TERM was set equally on both machines, but on one of them, the vim setting t_te got a different setting from the system wide vimrc. Solution can be found here: https://vi.stackexchange.com/questions/432/prevent-vim-from-clearing-the-terminal-after-exit I.e., just :set t_te= in your ~/.vimrc .


0

xdotool is a "command-line X11 automation tool". That's the very first line of the man page. It requires X. your AWS Ubuntu instance is probably not running X. While you can install it, it's not something that's usually installed or used on an AWS instance. w3m is a text-based web browser. While it can run in an X terminal emulator, X is ...


Top 50 recent answers are included