Zomg, they still have Yast?!? That was the main thing that drove me away ages ago!

I think it comes from a lack of formal typing instruction leading to a hunt and peck by index finger style of typing.

That’s why Arch has the AUR. :)

Switch to something that always delivers the latest KDE Plasma. That’s old.

I even wrote a function to parse a json for some configuration details, and loop through it to dynamically create more named functions from that json profile. I use it at work for automating my cloud account logins with a single profile name from the command line. :)

But then I’d have to run Nix.

Functions are best for this.

Mandrake and Win4Lin, was an amazing time. Back when corporate had you running windows 98se, and you could run it in Mandrake Linux sooo much faster than native. Miss that.

Don’t waste time doing that, just run real Linux.

This doesn’t belong in here.

Get 'im, boys!

I’m picturing Daffy Duck and Bugs Bunny swapping hunting signs on a tree… “Linux season!” “GNU season!”, back and forth. The rest of us just watching like Elmer Fud.

Don’t know about everyone else, but here are some of mine:

• Stick to posix compliance shell code, wherever possible
• Please wrap your variables with { }. Just please.
• Global variables being exported in all caps
• Local variables in lower case
• $() instead of ` `
• Comment anything complicated, comment what section, comment usage
• Include usage output if options are not recognized
• Use case instead of if / elif, where possible
• 80 characters or less per line, where possible
• HERE docs in designated section, marked by comment blocks
• Comment your functions immediately above it’s definition
• Add comment “#End of function Xyz” at line immediately below a function, with replacing Xyz with name of that function
• 2 space indentation
• Multi-line strings: First line open with quote and first line of string, followed by a backslash , subsequent lines properly indented and backslashed. Last line, properly indented and close quoted.
• Break up multiple piping of commands with |\ and a new line where it makes sense to look nice, assisting readability
• Echo what the script is doing once in a while if the user will be waiting for a while
• Please don’t do shar archives, or byte located binary extractions, make a script and a separate tarball - Helps a ton if we have to change it, like say… swapping out a bundled java runtime built for x86_64 with one for aarch64
• If the script will run for a very long time, check for tmux or screen and also the TMOUT variable… Give a warning to the user their connection might time out before the script is done if they don’t unset TMOUT, and try using tmux or screen to allow the script to continue in the background, even if you do get disconnected
• Make use of logger
• I try to organize a script this way: 1. Shebang, 2. Initial variable definitions, 3. Functions, 4. runtime execution code, which might be best outside of a function, and calling functions. 5. Clean-up (remove pid and lock files, tmp files, etc etc.)

Then don’t ever get rid of your own place, so you can prove you’ve only been dating, not living together.

I got a temporary ban from, I suspect, the only mod in here to have personally blocked me. The mod log accuses me of breaking the rules 1 & 2. Based on the timing, it aligns with my comments in this post. They neither broke the community bulleted rules (about Linux, no misinformation), nor did they break rules of 1 & 2 of lemmy.ml. There was no bigotry, no racism, sexism, ableism, homophobia, transphobia nor xenophobia. TThere were no individuals disrespected. I seek clarification of how my posts broke the rules, in DM’s please. I am not seeking further ban, just clarification of how those rules cover the opinion that one editor is less than another, lacks necessary features when compared with editors more standard across POSIX compliant systems, and that relying upon its existence could lead to situations where one could be ill equipped for systems where it is not installed, due to it not being such a standard.

I post this as a comment, as I cannot seem to message the entire group of moderators for this community all together, especially where one appears to be unreachable to me… something I don’t think mods of a community should do or even be capable of if they are to carry out their duties properly.

I ask the mods (preferably the mod who took the action, since no mod username is in the modlog… that’s a separate issue) to DM me and delete this or message me here, which ever is preferred. Can’t go navigating safely in here if the alleged offense wasn’t clearly communicated and explained how it violated said rules. I’m not even sure which comment, specifically, was at issue. Right now it feels like something I said was just deeply unpopular with one or more mods, and summarily punished and random rules tossed out.

I’ll delete this in a few days if no mods respond. But clarification without further punishment would be appreciated.

Thank you.

Removed by mod

Removed by mod

Why on Earth would you use that thing?

Books, periodicals, internet searches, practicing everything at home on a personal equipment until you’ve got it all mastered. If one can’t learn that way, take courses. The way the rest of us did it. Once you’ve got that, you have the ability to learn anything new coming… and can hit internet forums with well formed questions, complete with context. Staying on nano/pico, there is just no excuse if you’ve already been heavily using linux for 3 years or more. It’s an editor for those who are still in the beginning of the SELF learning phase. It should never be included in any distro’s default install except for school classroom centered distros. Just because something is easy to use doesn’t mean it’s installed as a standard everywhere. Folks learning this as their craft need to learn how to sit in front of any Linux or Unix and use standard tools to achieve what they need to do. That means learn your Vi. Learn your Posix shells like Ksh, Bash, Zsh, Dash, not the nano of shells, fish! Learn your Python, your Perl. Learn your SysV ‘isms in addition to your SystemD. Learn your csh (tcsh will do). Learn your terminal control codes. Learn your SysRq funtions. Learn your tmux, your gnu screen. Learn with and keep handy your books for awk, sed, patterns, perl. Learn your mkfs’, the different filesystems and their benefits, their options and tools, how to resize. Learn your MD raid. Learn your LVM. Learn various encrypt at rest options. Learn containers. Study and remember the differences between gnu, bsd, and sysv tools like tar, cpio, find, and even ps. Books books books! Practice practice practice! Study study study!

And when you got that done, look up and see what you’ve missed while you were doing all that, and start in on all that new stuff. Wash, Rinse, Repeat. Never stop reading, studying, practicing, learning.

That’s how. Oh, and delete nano!!!

Well yeah, for computers in kindergarten schools.