ttj - Tom Jones

I just went to save a picture from a chromium browser. Rigbt-clicked, save. I was going to call the file after some things from the image.  It's a picture of a letter, so the date, and title, and amount of money it relates to. The "save" dialog came up, and the picture was gone.  Instead of doing the save dialog simply as a new window, chromium is instead "clever", and messes things up.  So I had to close the save dialog, write down the attributes "2024-03-04", "order_imposing_a_penalty", and "200.gbp", then save it again, and write in those things in the save dialog.  The whole point of a windowing system is to be able to have things side by side, but this is being deliberately disabled by imbecile geektards. This anti-pattern has been happening repeatedly in the previous weeks.  I haven't been taking exact notes on it (there is only so much instrumentation one can do on faults without grinding to a halt), but, from memory, a r...

 Often in a shell, one wants to do something with the newest file in the current working directory. Tab already completes on partial names in many interactive shells including bash. The idea here is to have a shortcut to autocomplete on the file with the highest ctime in the directory.  The action of "doing something to that file you just created" then becomes more convenient. As for user interface, is shift-tab available in bash et al?