4 ms·
> I don't really know what a 4k JPEG worth of command line arguments is even supposed to be used for. I didn't either, until I learned about compiler command l
by dataflow 1y ago
> I don't really know what a 4k JPEG worth of command line arguments is even supposed to be used for.
I didn't either, until I learned about compiler command line flags.
But also: the nice thing about conmand line flags is they aren't persisted anywhere (normally). That's good for security.
- eightys3v3n 1y agoThere were ways for other users on the system to see running process command line flags I thought. This isn't so good for security.
- dataflow 1y agoThat depends on your threat model.
- Ghoelian 1y agoPretty sure `.bash_history` includes arguments as well.
- dataflow 1y agoThat's only if you're launching from an interactive Bash? We're talking about subprocess launches in general.
- johnisgood 1y agoIf you add a whitespace before the command, it will not even get appended to history!
- amelius 1y agoThis is quite annoying behavior, actually.
- zamadatix 1y agoI had never run across this and it didn't work for me when I tried it. After some reading it looks like the HISTCONTROL variable needs to be set to include "ignorespace" or "ignoreboth" (the other option included in this is "ignoredups"). This would be really killer if it was always enabled and the same across shells but "some shells support something akin and you have to check if it is actually enabled on the ones that do" is just annoying enough that I probably won't bother adopting this on my local machine even though it sounds convenient as a concept.
- wongarsu 1y agoI'm mostly using debian and ubuntu flavors (both on desktop and the cloud images provided and customized by various cloud and hosting providers) and they have all had this as the default behavior for bash YMMV with other shells and base distros
- zamadatix 1y agoProxmox (debian 12.x based) and Arch both didn't for me (both w/ bash). An Ubuntu 24.04 container in Proxmox did though.