241–250 of 276 posts
The python utils section missed the very cool json.tool that can pretty print JSON files (and exists on your OS if it includes Python): cat /tmp/foo.json | python -m json.tool https://docs.python.org/3/library/json.html#module-json.tool
Don't abuse cats, use `python3 -m json.tool < test.json` instead.
Earlier quoted context omitted.
This. After the KDE 4 debacle, I gave up on KDE because they cut all the functionality I relied on. However, I’ve been pleasantly surprised by how functional the newer KDE5/Plasma desktop is, especially once you change a handful of really ugly defaults (mouse cursors, window switcher and a couple other similar things)
That, imho, is the major boat anchor holding KDE down: the ugly defaults. If they would take a moment to apply tasteful default settings it would make a huge difference in the marketing value. In the end, though, KDE is "just like Linux" in the philosophy of "you don't like it? change it!"
Earlier quoted context omitted.
This feels off topic. I agree with these suggestions and appreciate the suggestion for Xournal, will look into that. But TFA focused on fundamental command line tools and shells, not office productivity apps.
There are thousands of articles on the classical command line tools grep, awk etc. With a subject "Linux Productivity Tools" I think this was both on topic and valuable.
Earlier quoted context omitted.
1. "Xournal" is amazing, small install footprint, simple interface and can do everything you need with pdf's. 5. You should try [1] "Kdenlive", it has it's quirks (as all linux tools do) but it's probably the best open-source Linux video editor out there. [1] https://kdenlive.org/en/
For video editing, Blender is the best FOSS tool I've tried. But you now get Davinci Resolve for free on Linux. It blows the FOSS competition out of the water, being a software with probably millions of dev hours funded by Hollywood studios behind it. Blackmagic decided to go the way of providing the basic tool for free in order to build user base amongst hobby video editors, and it's not a bad move IMO.
locate is not mentioned -- two orders of magnitude faster than find for searches from '/' on my laptop, e.g. find / -name \*bashrc\* locate bashrc Faster because reading from a single binary cache file, updated nightly, rather than opening every directory inode under /. To force an immediate synchronous update of the cache: sudo updatedb
Relying on a database which gets updated nightly is problematic for some usage though in at least 2 ways: I don't leave my computer on if I'm not using it so there's a good chance the db will simply never update (I guess?) plus it's only usable for locating files with confidence if you know they're system files or else they were on the system yesterday. Or, you run updatedb manually all the time and weep because that…
Earlier quoted context omitted.
+1 for ripgrep (it really is a lot faster). Also, I recommend using fd as a replacement for find. It’s API is a bit easier to grok imo, and it’s similarly blazing fast. fd/rg/fzf are the core tools I end up using most frequently, working in a big monorepo.
Does fd actually cover all the same ground as find? I used to be intimidated by find, but these days I find it’s extremely useful for all sorts of otherwise complicated file location operations. For example, to find files newer than a certain date, just use ‘touch’ to set the date of a temp file and then ‘find -newer temp’. Or, I have a script that deduplicates all the regular files in a tree by hard linking them to…
> cmd #tag to tag a hard to remember command Command tagging wasn't really explained in the deck. I had to read this archived web page for an explanation: https://web.archive.org/web/20191216131445/https://www.ostec...
Earlier quoted context omitted.
I never said python is bad. What I mean is that httpie is not a strict improvement because it's written in python. Ripgrep for example is a strict improvement because it's safer, more performant, and has equivalent and extended features, without missing anything. The only advantage of grep over ripgrep is that it's much older and prevalent. With the exception of this advantage of age, one can say that X is a strict i…
At what point you need computing performance on an I/O bound task? The only performance that matters in http requests is async support. You can have 1000 pararel curl processes and will still be dusted by a single async python process.
You can think of it as a spectrum ranging from incomparable to strictly better. So you can't say that one should use Python over grep for example; you can't even compare the two because that doesn't make sense. They aren't even in the same space. Ripgrep however is a strict improvement over grep, it is faster, more featureful, safer, and has no downsides (with the exception of age, as I've mentioned).
I think HTTPie is very close to the end of the spectrum of being a strict improvement, but it's held back by various little things that don't matter to many but still matter.
Earlier quoted context omitted.
I had not, just installed it though and it looks fantastic, thanks! The best I'd found previously was a no-annotation script that failed most of the time with a vague "something went wrong" error.
I hunted around for a while looking for something similar. I spent so much time in Slack working remote, that fast screenshots with arrows and notes are critical to communication. Coming from a Mac environment, I can't remember what the tool was that I used previously but I think it was purchased by Evernote. Flameshot has been excellent as a replacement.