A space biologist by training and a (Arch)Linux user by passion #ArchLinux #Linux #KISS #FOSS #terminal, #python https://www-gem.codeberg.page
As others said, the Arch wiki is so well made that it should be the only source you need. Videos will not bring you anything given your background. The main difference with other distros will be the package manager.
A video about the install process will just be someone reading the wiki to you, and a video to “explain” pacman to you will be overkill ;)
This recent post may be of interest to you: https://lemmy.ml/post/27474047
You may also find some ideas here or there.
I personaly use the power of neomutt and notmuch, but it’s not a GUI option if that’s what you’re looking for.
I will not reiterate what others have well explained Re: the use of &, though it’s surprising to see someone able to use dwm before getting control of the basics of the command-line :)
Coming back to your issue, have you applied the patch and recompiled dwm? Also, you may want to take a look at the note on this patch’s github (which was last updated 13 years ago).
There are a lot of software alternatives depending on your needs and preferences. You may want to take a look here or there.
Linux is full of options to let you build the best system for you. That means you’ll have to invest some time to decide what you want (starting with the distro). Moving to Linux is discovering a brand new world where it’s easy to get discouraged and flooded by the freedom you’re given.
In your efforts of developing a new desktop, I’d suggest to look around for already existing Linux desktops focused on visually impaired users. While they may go beyond what you’re suggesting in your post (screen reader, text speech, braille output…) you may still get some inspiration from them.
Maybe you can find some inspiration here.
One of my favorite alternatives to the default commands.
Note to OP: you don’t want to use obsidian, but obsidian.nvim is not related and not dependent on the software with the same name. Obsidian.nvim offers a Zettelkasten approach too.
https://github.com/epwalsh/obsidian.nvim
https://youtu.be/5ht8NYkU9wQ
No one’s job is to screen PKGBUILD of AUR packages so it’s technically not safe to use them. That being said the large community is keeping an eye on these packages and, while problems are not fully preventable, malicious stuff are caught pretty quickly.
So, to contrast with my first statement, one could argue that it’s mostly safe to use AUR. That’s even more true for packages used by a ton of people because issues/risks will be flagged almost immediately should they ever exist. That’s the case for browsers, especially when developers themselves offer an AUR package (like Librewolf: https://librewolf.net/installation/arch/).
Packages from the AUR basically do what is written in the PKGBUILD and install script so that’s why everyone will instruct you to learn about that before installing AUR packages with an helper. That’s too much for some people though and at the end of the day you also have to trust the person who wrote the source code and which is compiled locally.
Nothing is 100% safe. I personally have 96 AUR packages installed because there’s no other packages available (this includes stuff like my windows manager, python tools, 3D slicer, web browser…).
Same for me. It’s frustrating to not see this one getting more popularity.
Can add chawan to this list.
https://sr.ht/~bptato/chawan/
Reviews are good to learn about each printer features if you don’t like to read. Then, just do a check list and see which machine has the best specs for your needs. At least that’s my approach when buying printers because at the end of the day they’re all extremely similar and capable all things considered. A consideration that may only matter to few is the proprietary/open-source aspect.
Reviews will only emphasize bells and whistles you may not even need. Everyone will comment on their personal experience which will vary with the machine they have and the gap can be huge for the same machine because it’s a piece of hardware/software and some may have flaws despite all the quality checks.
This is my neovim visual config:
-- General colors
vim.api.nvim_set_hl( 0, "Normal", { bg = "none" } )
vim.api.nvim_set_hl( 0, "NormalFloat", { bg = "none" } )
vim.api.nvim_set_hl( 0, "NormalNC", { bg = "none" } )
vim.api.nvim_set_hl( 0, "LineNr", { bg = "none" } )
vim.api.nvim_set_hl( 0, "SignColumn", { bg = "none" } )
vim.api.nvim_set_hl( 0, "Folded", { bg = "#4b4b4b" } )
vim.api.nvim_set_hl( 0, "FoldColumn", { bg = "none" } )
vim.api.nvim_set_hl( 0, "Visual", { fg = "#000000", bg = "#de935f" } )
vim.api.nvim_set_hl( 0, "NotifyBackground", { bg = "#000000" } )```
-- Spell checking
vim.api.nvim_set_hl( 0, "SpellLocal", { fg = default } )
vim.api.nvim_set_hl( 0, "SpellRare", { fg = default } )
vim.api.nvim_set_hl( 0, "SpellCap", { fg = "#de935f", italic=true } )
vim.api.nvim_set_hl( 0, "SpellBad", { fg = "#ff0000", italic=true } )
-- Markdown
vim.api.nvim_set_hl( 0, "htmlBold", { bold=true } )
vim.api.nvim_set_hl( 0, "htmlItalic", { italic=true } )
vim.api.nvim_set_hl( 0, "htmlStrike", { fg = "#ff0000", strikethrough=true } )
vim.api.nvim_set_hl( 0, “Normal”, { bg = “none” } ) is probably what would work for you.
Thanks for writing this response so I don’t need to spend the time and efforts you did to write it :) Hopefully OP find it useful.
I’m in the same boat. I’m running the same Arch for 15 years now. The only cleaning is for old packages and config files. Also, if you remove the packages correctly, the maintenance should be minimal.
There should be no need to do a fresh install of the OS. This is another great benefit versus others. Even when I change my machine, I just install an image of my old system so it’s fully functional right away.