I created a simple Bash script that will always disable the default/internal monitor on your laptop when using AR glasses (or any other external monitor). I find this useful for when using AR glasses such as the XReal One which allows you to change the mode from regular mode to ultra-wide mode and when doing this, it will act as your unplugging the XReal ones and plugging in XReal one again in a new mode, causing the interal laptop display to become enabled.
To keep the laptop display always off, weather the laptop lid is either closed or open, this simple bash script will always disable the laptop screen every X seconds (You can change it by changing the wait variable)
Simply copy this script and create a new bash script such as disable-display.sh, make the script file executable and add it to your startup applications and it will run in the background. You will need to run xrandr command with all of your displays enabled to get the names of the displays and change the variable names in the script accordingly.
NOTE: This script may not work with a full Wayland setup and may only work on X11.
Enjoy
#!/bin/bash
#RUN xrandr TO GET THE NAMES OF THE DISPLAYS AND SET THE VARIABLES TO THESE NAMES
readonly default_display="eDP"
readonly external_display="USB-C-0"
readonly wait=5
while true; do
#Check if there is an external display connected
if xrandr | grep -q "$external_display connected"; then
#Disable the internal display
xrandr --output $default_display --off
fi
sleep $wait
done
Serious question, why use a semicolon to put do and then on the end of the previous line?
Especially when do/done are the open and close control directives for a block.
Don’t you think bash looks much cleaner when you use it how it was designed?
I’d write
for the same reason I’d write
or in another language
Because it’s all part of the same statement and having a single line with just
door{seems silly and implies (to me) that the lines aren’t related.Agreed.
I also use this VSCode extension which formats my bash code using
shfmthttps://open-vsx.org/extension/foxundermoon/shell-format
deleted by creator
It just looks weird to me to stick a semicolon into the middle of a line when a compound command isn’t actually needed.
So you’d rather it all be on one line? I’d only do that if it’s a very simple command, otherwise you’re just making the code harder to read.
No the opposite. I think more shorter lines makes it easier to read than fewer longer lines.
isn’t exactly harder to read than
though, is it? And going back to my original point, I don’t like
while truebeing on its own as to me it looks like it’s meant to be a separate statement rather than part of thedo/doneblock.Its a personal style choice.
With a blank line before the ‘while’ and another after the ‘done’ its a nice little easy to identify block. I don’t know how the ‘while’ would look like its not a part of that block.
A midline semicolon just looks ugly to me so I don’t do it unless it is the only way to make a statement work.
In defense of OP, I do this a lot and go for similar moves in other languages too if the conditional bit is just a line or two. Pro choice!
Bash doesn’t ever look clean.
It’s just a brace on same line/new line stylistic choice with extra steps.
About that, I used to also think that brace on new line is clearer, but after seeing a lot more code I have switched sides, both are clear enough to me, so I’d rather have fewer lines
Yes totally a personalstyle choice. To me, using a semicolon to save a line looks more ugly ; then ;)
Not OP but this is how I learned it and how it’s presented in the help file.
Thats the concise help text to keep it short and easy to read.
The first line in the GNU Bash manual section on loop constructs says “Note that wherever a ‘;’ appears in the description of a command’s syntax, it may be replaced with one or more newlines.”