Path: ...!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: candycanearter07 Newsgroups: comp.os.linux.misc Subject: Re: What programs do you make sure are installed on a new Linux install? Date: Sun, 14 Jul 2024 16:20:06 -0000 (UTC) Organization: the-candyden-of-code Lines: 106 Message-ID: References: Injection-Date: Sun, 14 Jul 2024 18:20:06 +0200 (CEST) Injection-Info: dont-email.me; posting-host="dbf946a48c3ba77a74d47423cb04007e"; logging-data="246314"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/dYr4wj6jHGCE7f1DP3HL9AEeDjfIvlEpXb9538vkbOQ==" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:6PM3vRfI3+Eoxfr7aBmFCqtfP1Y= X-Face: b{dPmN&%4|lEo,wUO\"KLEOu5N_br(N2Yuc5/qcR5i>9-!^e\.Tw9?/m0}/~:UOM:Zf]% b+ V4R8q|QiU/R8\|G\WpC`-s?=)\fbtNc&=/a3a)r7xbRI]Vl)r<%PTriJ3pGpl_/B6!8pe\btzx `~R! r3.0#lHRE+^Gro0[cjsban'vZ#j7,?I/tHk{s=TFJ:H?~=]`O*~3ZX`qik`b:.gVIc-[$t/e ZrQsWJ >|l^I_[pbsIqwoz.WGA] wrote at 07:16 this Sunday (GMT): > On 2024-07-13, candycanearter07 wrote: >> Borax Man wrote at 11:54 this Friday (GMT): >>> On 2024-07-10, candycanearter07 wrote: >>>> Borax Man wrote at 09:31 this Wednesday (GMT): >>>>> On 2024-07-08, candycanearter07 wrote: >>>>>> Borax Man wrote at 10:25 this Monday (GMT): >>>>>>> On 2024-07-07, candycanearter07 wrote: >>>>>>>> Borax Man wrote at 01:10 this Sunday (GMT): >>>>>>>>> >>>>>>>>> Just wondering what programs (aside from the coreutils/X11 and other >>>>>>>>> elements that make up a basic install), do you consider to be a vital >>>>>>>>> part of YOUR Linux install? What are the little additional tools that >>>>>>>>> you can't live without, or just consider to be necessary that maybe >>>>>>>>> others wouldn't? >>>>>>>>> >>>>>>>>> For me, its >>>>>>>>> - fortune >>>>>>>>> - cowsay >>>>>>>>> - xpenguins >>>>>>>>> - fvwm(3) >>>>>>>>> - oneko >>>>>>>>> - emacs >>>>>>>>> - mc >>>>>>>>> - zsh >>>>>>>>> - asclock (using the FreeAMP theme) >>>>>>>>> - PCManFM >>>>>>>>> - star >>>>>>>>> - urxvt >>>>>>>>> - xpat2 >>>>>>>>> - xlock >>>>>>>>> - links >>>>>>>>> - most >>>>>>>>> - lftp >>>>>>>>> - lzip >>>>>>>>> - xclip >>>>>>>>> - screen >>>>>>>>> - lrzsz >>>>>>>>> - gcc/g++/gdc >>>>>>>>> - nasm >>>>>>>>> - locate >>>>>>>>> - dar >>>>>>>> >>>>>>>> >>>>>>>> I'm sure I'm forgetting some here, but >>>>>>>> >>>>>>>> git obviously >>>>>>>> krita >>>>>>>> aseprite >>>>>>>> screen >>>>>>>> rxvt-unicode >>>>>>>> cool-retro-term >>>>>>>> audacious >>>>>>>> mpv (and the ffmpeg dependency) >>>>>>>> imagemagick >>>>>>>> picom >>>>>>>> vim >>>>>>>> n30f >>>>>>>> xscreensaver (yes i use it as my locker) >>>>>>>> screen >>>>>>>> less >>>>>>>> rofi >>>>>>>> bucklespring (optional) >>>>>>>> mc (optional) >>>>>>>> >>>>>>>> aptitude (if on debian based) >>>>>>>> >>>>>>>> >>>>>>>> sidenote thank you for mentioning xpenguins i have been looking for a >>>>>>>> replacement for AMOR (amazing misuse of resources) forever since it wont >>>>>>>> compile for me under debian >>>>>>> >>>>>>> I always have both XScreenSaver and XLockmore. >>>>>> >>>>>> >>>>>> Do they work together? >>>>> >>>>> Not really! I generally just use xlock when I want to lock my screen. >>>>> XScreenSaver, well, my kids enjoy watching the bouncing cows, they think >>>>> its hilarious! >>>> >>>> >>>> Oh, IG I'll stick to XSS then. Do you run them directly from >>>> /usr/lib/xscreensaver? (or libexec) >>> >>> Its built into the menu for FVWM. My FVWM config, which is based on an >>> old template that came with FVWM or FVWM95 has a menu for ScreenSavers >>> which lists the xlock ones and also for XScreenSaver to start it, or >>> start the demo. Thats perhaps why I use them, because in the very early >>> days when I started using Linux, I found them in the menu entry here. >> >> >> Oh, interesting. XFCE doesn't have those, but the binaries are stored in >> /usr/lib(exec)/xscreensaver so its easy to run from there. > > FVWM has this thing called "pipe menus", where you can construct a menu > dynamically from the output of a program. I'm sure other window > managers have this, but this means you can call xlock to list all the > screensaver types, then construct a menu which launches the locker from > that. Neat! I know you can implement that relatively easily with something like dmenu. -- user is generated from /dev/urandom