That can be a struggle. There used to be a context menu option in maybe xterm or the kde terminal emulator that would copy the wd and maybe even the highlighted file but I might be gpt hallucinating that last one.
After fucking up bad copying from the internet into a terminal about fifteen years ago I have tried to review and understand what’s happening when copying from or to the terminal even in part. It would be bad for me if there weren’t the possibility of (at best) having shit not work when I use middle click with abandon.
I been thinking a lot about designing technology to discourage people from using it. For example it’s a serious mistake when wearable displays are made to look like wayfarers. The danger of people accepting them socially to the point of being manipulated into a state of flow, dissociating from their reality through a combination of sight and sound augmented reality, is too high. Good design of wearable displays should prioritize function over form 100% and make the user look like an insane freak that no one wants to be around, forcing people to remove them in order to maintain social interactions.
I think copying to and from the terminal is like that. When going between an interface which is a very high level mediator of interaction with the machine and one that’s a very low level mediator, we should be alert, on guard and proofreading everything twice. It’s good that we have to check ourselves before we wreck ourselves copying and pasting into the terminal.
I didn’t notice that part of your post. 🙏
The point I guess I was getting at was that even having “come up” with Slackware and a whole os that’s just 69 half baked scripts in a trenchcoat I adopted a more universal mindset and specific skill set when using scripts over ten years ago and find it hard to justify expecting sanitary inputs nowadays when it is harder and harder with Unicode and is a serious security threat to treat variables as passable strings.
I wasn’t trying to suggest that there isn’t a way to make a space in a filename cause an error, but that I can’t think of an example where allowing a space to affect things was a good or right way to do something.
In the specific example of the op, no spaces is a scene rule from the days of ftp and irc/usenet. The idea behind having only a subset of the ascii character set was to allow those services to work with the files and commands around them. There’s no reason to treat my own scripts and programs as if they’ll never encounter the galaxy of other characters that are flying around now and to be honest, theres no reason not to work in sane handling of non ascii characters in filenames even for code I only expect to touch scene stuff.
It used to be an unavoidable mistake when we dug up buried utilities. Now that there’s a number to call first it’s only the fault of the knucklehead with the shovel.
Please don’t read this as some kind of an argument. I think we basically agree and I’m not trying to get one over on you.
I’m not at a bash terminal, but I think “$f” fixes that. I’ll look tonight.
Escape characters and autocomplete exist.
It’s also really good practice to account for weird characters in programs and shell scripts you write because then you don’t have injection vulnerabilities or unicode problems.
Seriously, what’s an example of spaces in filenames causing a problem?
I’m with the person you’re replying to, what’s an example? I haven’t had a problem working with filenames with spaces in at least ten years on windows, Linux or Mac…
What I’m trying to push back on is your assertion that everyone can do it.
Security auditing is an extremely complex and specialized field within the already complex and specialized field of software development. Everyone cannot do it.
Even if it were as straightforward as you imply, just the prevalence of major security flaws in thousands of open source packages implies that everyone doesnt do it.
If I were to leave piles of aggregate and cement, barrels of water, hand tools and materials for forms, a grader and a compactor out and tell the neighborhood “now you can all pave your driveways” I’d be looked at like a crazy person because presented with the materials, tools and equipment to perform a job most people still lack the training and experience to perform it.
Idk what the person you’re arguing with is trying to say, but as a prolific user of open source software, there are thousands of serious vulnerabilities discovered every time some auditing company passes its eye over github.
Malicious commits are a whole nother thing and with the new spaghetti code nightmare that is python nowadays it’s extremely hard to figure out which commits are malicious.
Open source software is not more secure by default and the possibility of audit by anyone does not mean that it’s actually getting done. The idea that anyone who can write software can audit software is also absurd. Security auditing is a specialized subset of programming that requires significant training, skill and experience.
I think you’re gonna find out very soon because four battery plants are in the works for trucks.
i’m skeptical about electric trucks.
they’re gonna be a hit with the people who’ve been buying them instead of sedans lately, but the fleet and rural markets are gonna be less inclined to use em and needing a big battery service periodically is gonna change the long term value proposition of a full size truck for a lot of people.
They’re planning on building four, and they paused construction recently as a power play in negotiations when the uaw said battery workers should get the same pay as the machinists.
I saw that those plants will be making batteries for the new f150, not the much smaller evs that everyone else drives.
Battery manufacture is part of its own can of worms though, and one that doesn’t make evs look great either.
I wanna also say that I’m not against spinning down the ice auto industry, but no one who’s suggesting doing that or making fun of people who recognize that it’s the consequence of things that are already happening has a real plan for it.
Come on, is the best insult you got that I sound like it’s my job to defend workers?
Really and truly, where will the labor cost savings go? There’s going to be one, so who gets it? How will that be enforced?
What’s gonna be done for the people whose labor isn’t needed anymore? Bear in mind we’re not just talking about the protagonists of the now forty year old song “Allentown”, but entire industries that support ice car production like die making and machining. Surely we have some idea of what happens here aside from “theyre fucked, some people’s blood and bonemeal grease the rails of progress”.
You can’t just handwave away the real effects of changes in productivity in the name of abstractly defined technological progress.
If you can’t seriously engage with the effects of a transition to producing electric cars then it’s no wonder American conservatives are making so much hay over it.
No really, the parts/labor breakdown of an ev skews farther to parts than an ice car. Who gets that money in their pocket in exchange for all the jobs?
What happens to the families and communities that depend on the jobs that are going away?
Have we learned anything from the failed reskilling of Appalachian coal country?
I’m gonna go backwards here:
We don’t see lots of high drag coefficient evs that look like mustangs because all the features of the mustang that make it look boxy and aggressive are there to accommodate the reality of making air go places it’s needed, across the radiator and into the engine.
We don’t see ev jeeps because jeeps are (or used to be) relatively lightweight, high torque vehicles whose design choices favor ground clearance over aerodynamics. Evs are relatively heavyweight and benefit most from low ground clearance and good aerodynamics.
When automakers try to put those designs in an ev buyers react negatively to them, to the point that they have to have ersatz engine noise to be accepted.
Indeed the wrangler and mustang are so disconnected from normal buying trends that they kept stick shift long after the industry wide move to automatics!
Those are popular models, but they’re extreme outliers in terms of design.
Let me address the top part of your reply with a question: if evs are so great and such a slam dunk why has Toyota, famous for not making the wrong choices, stuck with hybrids up until very recently?
Goose chasing meme: more money in whose pocket, motherfucker?
Seriously. We’re talking about shitcanning a third of the us auto jobs. Who’s gonna get the money from that nightmare?
How can we expect those communities to take it lying down when they saw what happened and continues to happen to coal country?
This isn’t fake made up handwavey bullshit. These are the real effects of domestic ev production and we can’t just say “anyone who opposed evs is a conservative piece of garbage or a head-in-ass neoliberal economist.”
What will that money be doing?
how are the ostensible productivity gains from evs going to be used to help american workers?
it’s hard to believe that the reduced demand for skilled tooling, die and machining labor will translate into some kind of gain for the communities and people that rely on that work to survive.
and we’ve seen how anemic reskilling efforts are and how the usual boilerplate response, “learn to code”, is completely defunct with the combination of LLMs and the cheap overseas junior dev labor pool.
american conservatives are trotting out these arguments to appeal to people who feel like they’re being forced to give up their lifestyle (driving cars with cheap gas), and materially are actually being heavily pressured to get evs without fully understanding the economics of this new class of Second Most Expensive Thing Most Americans Will Ever Buy, but that doesn’t mean that the realities that appeal is built on aren’t there.
That’s the social engineering aspect of insecurity on pwas.
I’m genuinely baffled by this comment section.