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…
Pynchon wrote it better.
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.
In addition to all that @MystikIncarnate@lemmy.ca said, implementing an am or fm receiver on an existing device is as easy as plopping down one of the existing bga chips that has an antenna input and an audio output. here’s one of the bigger ones that needs a killer 3mm x 3mm land pattern. It’s also only $1.79 or so, which is expensive for an ic, but in the context of a phone wouldn’t contribute significantly to the cost of the device.
The need for an 1/8” out would be the worst part because ironically, phone jacks suck for uhh… phones.
Ladies and gentlemen, the CIA!
give it up for our brave intelligence assets risking their time to implement all of the ideas presented in the Simple Field Sabotage Manual!
They’ll be here all week, so make sure to come on back for the floor show tonight, i hear they have a real ripper planned ba-dum-tiss!
Seriously folks, enjoy your meals, tip your servers and stick around for the rest of the night.
Take it away boys!
What’s the problem here?
All the stuff is listed as rule 1 and rule 2 and they seem to fit the description even without the helpful context.
There’s one ban evasion in there too.
Sounds like the Marxist mod is doing a good job.
Hey I got a temp ban for my post and username (typical lemmy homophobia) but I wanted to come back and seriously recommend with nothing but civility that you engage with some of the ideas of people who’ve pushed back against you in this comment thread.
When everyone from conservatives to communists are frothing at the mouth it doesn’t mean you’re doing something right, it doesn’t mean the answer is somewhere in the middle and you found it, it means you overlooked a lot of ideas.
For my part, your claim that tech workers aren’t proletarian is absurd on the face of it because that claim denies the nature of tech work and proletarianization. An alarmingly small number of tech workers hail from the places they’re working in, almost all have moved there for the work. Unless everyone moved away from their families and homes because they just love the idea, they were pushed to move by the lack of work. And while you’re happy to put senior engineers in the tech worker category, call center tech support is notably absent in your analysis. Heck, entry level programmers are absent!
Your claims can only be put together as some form of gatekeeping based on aesthetics: they don’t look poor to you so they can’t be proletarian.
If I’m off base I look forward to your response!
Hey, why don’t you engage with all the people who are explaining to you in good faith and great detail how your understanding and comments are deeply flawed instead of just having a snit with the one who didn’t?
Lemmy has limited space for unique comments on posts, so make sure it’s a good one before you click “reply”!
If you feel the need to post but don’t wanna blow up the spot, just copy another users comment verbatim and post that. Copies of comments don’t take up space.
All that doesn’t apply to posts, make all the posts you want just don’t comment on em!
It’s a serious problem, but users like you can help!
When you delete your posts the space is freed up because the backend just serves up the same “deleted by user” content.
So when you think one’s been up long enough, go ahead and delete that post!
Along with posting less, deleting your posts can save lemmy!
Remember: limit your comments, lemmy is running out of comment space!
If you’re thinking about commenting, make a new post instead. There’s plenty of room for posts!
Removed by mod
Steam dick