4 ms·

That's only if you're launching from an interactive Bash? We're talking about subprocess launches in general.

• johnisgood 1y ago
  If you add a whitespace before the command, it will not even get appended to history!
  • amelius 1y ago
    This is quite annoying behavior, actually.
    • nosrepa 1y ago
      Good thing you can turn it off!
      • amelius 1y ago
        Yeah, took me a while to figure that out though. Plus I lost my history. Typing an extra space should not invoke advanced functionality. Bad design, etc.
  • zamadatix 1y ago
    I 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 ago
      I'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 ago
        Proxmox (debian 12.x based) and Arch both didn't for me (both w/ bash). An Ubuntu 24.04 container in Proxmox did though.