All my old devices become un-chargeable due to USB-C plug wearout. Even with wireless charging I cannot avoid sometimes needing a wired full charge.
jdnewmil
joined 2 years ago
Just a note: Windows software for controlling hardware is highly likely to assume a)direct access to the hardware (sometimes mediated thorough ancient APIs and assuming the existence of defunct expansion slots) and b) assume meatspace time can be counted using OS timing ticks (which get stretched out as modern VMs timeshare with other processes underneath the virtulized hardware). It is awfully tough to replace them sometimes.
Bash scripts tend to use transformation programs that accept input through standard input and use the output from standard output. For replacing one character with another, the "tr" program is typically used.
To operate on the command-line arguments to a program like "mv", bash allows you to use back-tick quotes.
set FNAME="path/bad:file\\name"
mv "$FNAME" `echo "$FNAME" | tr ":\\" "_-"`
Note the use of escaped backslashes... the pair represents a single charcter. Be sure to study the manual for each command (e.g. man tr) before using it at first.
Te experiment building this kind of complicated command, replace the "mv" with "echo" to see what the two constucted arguments will be, and switch back to "mv" when they look right.
One approach to looping is to turn the above into a script that fixes one filename specified as an argument to the script ($1 inside the script) and then interactively pipe all the filenames through xargs to give them one at a time to your script.
find topdir -type f | xargs -d "\n" yourscriptname
You must try this on sample data and also backup your current data before turning your script loose on it... so often there are little things that don't behave the way you expect when some unexpected input interacts with your script.
Finally, there are scripting languages like Python that have a lot of these capabilities built in... and with more consistent syntax than the many-tools bash approach, but they can have the headache of a lot more specialized setup requirements than just bash to go along with those advantages.
Bro stair climbing wheelchair. Segway put a lot of design effort into this about 30 years ago before trying to go big with the normal Segway. https://www.scewo.com/en/
I copied so many short pieces as a child. OC is possible I suppose but there is a simpler explanation.
You didn't change anything?
No.
Where do you use it?
On my lap in the den.
When was the last time you vacuumed?
???
(Time to disassemble and apply compressed air...)
Failing to provide the name of the person in the body of the email is incomptetence.
Fox included the disclaimer about contact email... but IMO the person who built the mail merge was incompetent and that will not prevent ICE from coming after Aldo.
Not if cheeto is hiring.
Stick with Windows. Microft will deliver paradigm shifts and you will have no say in the matter. They are already removing options for disabling Copilot, and for all the promised backward compatibility they are letting go of features that lots of old Windows software depended on, as they introduce features similar to ones in Linux. I cannot really fault them for all of these changes, but the difference is actually one of choice and privacy, and not really the one you seem to think it is.
It is not recursive though. A directory is a special kind of inode that enumerates file inode numbers and when that list changes then the contents of that "directory inode" change. But if /home/user/.bashrc is deleted then the timestamp for /home will not be affected because the timestamps are associated with inodes rather than directory entries (assuming no symbolic links are involved).
https://www.redhat.com/en/blog/inodes-linux-filesystem https://en.wikipedia.org/wiki/inode
Hugh Jass isn't owned by any one person.