Hello Arch, my old friend :)

Goodbye Pop OS it was a fun couple-o-years but I’m ready for a new adventure!

It’s been a long while since I tried a new Linux distro.
I had been on Pop OS for the past few years and for a decade before that, it was always Debian. I had tinkered for months with Arch manual install on my old Thinkpad T400 and it still runs well, but I haven’t used it in years.
Today I chose to take the great grand leap again into the fascinating world that is ARCH LINUX, and I’m so thrilled! More specifically Endeavour OS (it so purdy).


During the setup, I must have clicked the Accessibility option for that screen-reader? A quick search and I was able to remove it sudo pacman -Rsn orca.

Next I installed neofetch, I’ve always been a fan. Tried to include it in my .bashrc but was shocked to learn that vim wasn’t installed. I tried vi and POOF! But I want neovim, so I have that now.

Can I uninstall vi? Could I just make a simple alias for vim=nvim?

I’m not gonna go installing shit like crazy, but the one thing I absolutely require is nodejs and npm for work. The /packages page shows latest releases ARE available … totally love this :smiley: :stuck_out_tongue: )

Do yall have any pointers for the happy new guy?!

I’m reading through the FAQ, packages, aur.packages, and list of applications pages.

BTW: my numpad doesn’t work? I’m heading to the Wiki.

And the “top bar” disappeared on my bottom monitor! But I’m sure I can find a solution before someone replies … READY SET GO!!!

EDIT #1: A quick clarification, I chose the install with bspwm :slight_smile:


If vi is being provided by the vi package you can remove it. You should check first to ensure vi isn’t being provided by something you want to keep. You can check with:

pacman -Qo /usr/bin/vi

Thanks for the quick reply :slight_smile:

After running that command, I get /usr/bin/vi is owned by vi 1:070224-5

I have no clue what that means.

Which install? Offline XFCE or online and DE of your choice?

It means the package vi is providing vi so you can remove it if you want to.

sudo pacman -R vi

Apologize for not being thorough. I will include my response in my post above as well.

I opted for the bspwm :+1:

Would not sudo pacman -Rsn vi be more preferable?

What’s the difference there?
sudo pacman -Rsn vi

-R removes the package whereas -Rsn removes the package and other files that are not required by other applications.

I recommend looking at this to compare the different commands within Linux distros:


I’m getting some wierd previews answers on this so please check the ArchWiki.

1 Like

So coming from Debian where I would typically run sudo apt remove package && sudo apt autoremove && sudo apt autoclean so then sudo pacman -Rsn package does it all in one shot?!

Very nice! :+1:

I would say that some things the Arch way does better, but in some things the Debian way does better. I am talking about package management here. This is my personal opinion, not EnOS or Arch. I prefer the Arch setup, but nothing is perfect…yet! :wink:

1 Like

auto remove in Debian seems pretty hardcore. If you choose to remove things via the terminal in Arch I would recommend you review what you are about to do. Probably obvious but just a friendly heads up!

1 Like

With OUT a doubt - I shall Google everything.

I have another problem for you :confused: I hooked up my 2nd monitor and ran arandr to generate my dualscreen.sh script. Then removed 2nd monitor and ran it again for my singlescreen.sh.

They’re in the default location ~/.screenlayout/ but dummy me, I deleted the original file that was there named monitor.sh. I’m guessing that if I were to restart/reload the bspwm config file, something unpredictable would happen because I deleted it :confounded:. I’m looking at the bwspwm config file and it DOES call ~/.screenlayout/monitor.sh, but I have overridden it with my own script.

Is there any way that I can have BOTH dualscreen.sh & singlescreen referenced in the config, so that if one fails, the other runs?

I hope that makes sense?!?!

1 Like

I too was on PopOS for about a year (Solus before that), but after Cosmic was released I encountered a handful of bugs (bluetooth was broken, Gnome settings had issues, Cosmic wasn’t yet 100% stable imo), so I decided to try EndeavourOS. Granted, to the PopOS teams credit, all those issues have since been resolved. Now the beauty of PopOS is it works out of the box very very well. And that’s fine for most users, but over time I just wanted something more; I wanted to dive deeper and learn more about my system. I knew an Arch based system was that first step towards that endeavour (see what I did there :wink: ).

I’ve forgotten where I was going with all of that, but the point is, hello fellow former PopOS user and welcome to the purple side of life :enos:

This forum, the EndeavourOS wiki, along with the Arch wiki, are the best resources I’ve had the pleasure of using. I hope you enjoy your time :slight_smile:

1 Like

Eek! I get where you’re coming from but that is beyond my experience. I have only done dual monitors when I used Mac stuff really, I tried running those in Linux with arandr and it can be done but I will have to pass you on to others who know more!

The was my reason for using it in the first place :slight_smile: Bought a brand new machine (first one in years) and maxed out the RAM with 32GB and disk space with a 500GB M2 and 1TB SSD. So I really need something with a solid history of “just working”, like you said, out of the box :wink:

first step towards that endeavour

bwahahaaa, I DO see whatcha did there!

1 Like

I frequently disconnect from my 2nd screen when I go with elsewhere.

I’m sure I can run either screen manually from terminal when needed. But I’m afraid of breaking bspwm on my FIRST DAY!

YIKES! lol

I’m currently watching a YouTube video. The channel Distrotube, familar with it? That guy got me to go back to Arch & choose bspwm over i3-WM or any other :wink:

1 Like

I use i3wm, my preferred options is to use autorandr:

autorandr --save screen1

autorandr --save screen2

Which save both configurations. You can then add the following to your config to load automatically

autorandr --change

If you are on logged in your session and want to swap lets say from screen 1 to 2 configuration you could open terminal and autorandr screen2

Edit: I switch frequently different monitor config between home and work. One thing I learned is to logout of the session then disconnect, and reconnect to my other setup. With autorandr it normally recognizes my saved profiles :+1:

Yes! Like to watch it too, nice wm videos. Because of him I tried xmonad, but didnt like it that much. But discovered qtile instead!

1 Like

Also on my “Forever Growing List of Things To Try”.