I use awk all the time. a very common and probably simplest reason I use it is it’s ability to handle variable column locations for data.
if you know you always want the last field you can do something like
awk ‘{print $NF}’
but usually using it as for performing more advanced operations all in one go without having to pipe something three times.
sure you can do grep cut grep printf, but you can instead do the pattern matching, the field, the formatting, whatever you need to all in one place.
it’s also got a bunch of more advanced usage of course since it’s its own language. one of my favorite advanced one liners is one that will recognize if it is going to print a duplicate line anywhere in your output and prevent it. in cases where you don’t want to sort your output but you also want to remove duplicates it is extremely helpful and quick rather than running post-processing on the output in another way.
all that said main reason I use it is because I know it and it’s fast, there’s nothing you can do in awk that you can’t do in Python or whatever else you’re more comfortable with. The best tool for the job is the one that gets it done quickly and accurately. unless your environment is limited and it prevents the installation of tools you’re more familiar with then there’s no real reason to use this over Python.
I use awk a good bit. Not as much as when I was doing data work, though. It’s better than cut at splitting on whitespace in many contexts. Lots of other nice uses like variable scope, regex, and summing
I’m not familiar with any differences the surface go might have from other surfaces I have used but the surface kernel has always fixed every issue I have had with them. I currently use a surface laptop 4 and I can’t even use Bluetooth without the surface kernel. As far as breaking the install goes, the instructions for installation and switching are truly as simple as copy and pasting 5 or 6 terminal commands. I really would recommend the surface kernel before any other fixes.
So yeah, Xfce looks the same as it did 10 years ago.
And?
Desktop environment is meant to launch apps and give me windows and maybe have a file manager. Xfce does that. It's a desktop environment.
Hey, "modern" desktop environment enthusiasts, if you bring Compiz back from the dead, give us luddites a call, will you? Ohhhh you kids should have seen it back in the day. Windows and Mac users saw Compiz in action and were, like, "wat." You don't get them to react that way to modern Linux desktops, no. And all that is lost now. Thanks Wayland.
I don’t know if Lemmy can do it yet, but I remember Reddit and also Facebook( I think) lets you set a minimum account age to post in a community. So we might want to get our mods to do that.
I’ve tried GNOME 45 extensively and I just don’t see how it’s better.
Even looking at the screenshots I don’t understand how GNOME 45 is better than GNOME 2. It doesn’t even LOOK better. You need extensions to get basic functionality like a window list and tray icons.
Then there’s the bad parts, like every window now has different decorations, doesn’t work with nvidia, etc.
There’s nothing wrong with angryposting, but it needs a kernel of truth which this is missing.
I set mpv as the root window which worked well. I stopped using it a while back, but if you are interested, I could dig up the simple script for you (literally one or two lines iirc).
Sure. If you are using an nvidia optimus laptop, you should also add __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia at the start of the last line when running in hybrid mode to run mpv on the dgpu. You should have a file at ~/.wallpaperrc that contains wallpaper_playlist: /path/to/mpv/playlist. You may want to add this script to your startup sequence via your wm/de.
I used to use the command line, Bash, Awk, Sed, Cut, Grep, and Find (often piped to one another) quite often. I can recall that the few times I used Awk was usually for collating lines from logs or CSV files.
But then I switched to using Emacs as my editor, and it gathers together the functionality of all of those tools into one, nice, neat little bundle of APIs that you can easily program in the Emacs Lisp programming language, either as code or by recording keystrokes as a “macro.”
Now I don’t use shell pipelines hardly at all anymore. Mostly I run a process, buffer its output, and edit it interactively. I first edit by hand, then record a macro once I know what I want to do, then apply the macro to every line of the buffer. After that, I might save the buffer to a file, or maybe stream it to another process, recapturing its output. This technique is much more interactive, with the ability to undo mistakes, and so it is easier to manipulate data than with Awk and shell pipelines.
This is fascinating to me. Do you have any links or suggestions for this workflow to learn more?
I am glad you asked, because I actually wrote a series of blog posts on the topic of how Emacs replaced my old Tmux+Bash CLI-based workflow. The link there is to the introductory article, in the “contents” section there are links to each of the 4 articles in the series. The “Shell Basics” (titled “Emacs as a Shell”) might be of particular interest to you.
If you have any specific questions, or if you have recommendations for something you think you would like to learn from one of my blog posts, please let me know. I would like to write a few more entries in this blog series.
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.