691: A Menlo Phase
https://atp.fm/691
Apple's chip-fab options, branding the 20th-anniversary iPhone, Terminal and Xcode preferences, and some very special filenames.
Post
691: A Menlo Phase
https://atp.fm/691
Apple's chip-fab options, branding the 20th-anniversary iPhone, Terminal and Xcode preferences, and some very special filenames.
@atpfm I can't believe no one mentioned how *terrible* text entry and manipulation is in Apple's Terminal app!
You can't click to move the cursor (option-click is ridiculous)
You can't cut or replace selected text
Holding shift and using arrow keys to try to select text just inserts key codes like ;2D
Command left/right doesn't go to the start/end of the line
It's so bad! These are basic computer text entry features from 30+ years ago.
@allanjackson I didn’t have those things in my first experiences with Unix, so I don’t crave them now! I don’t even want them! (I’ve had them in fancier terminal apps, and I have not preferred it.) Finally, being old pays off!
@siracusa But you're always complaining about apps that don't follow the system standards. This is NOT how Mac apps behave!
All these things are just QoL features that you don't have to use if you don't want to... surely you aren't arguing that Apple should leave it broken just for historical unix reasons?
@allanjackson Terminal is where the Mac and Unix worlds meet, and there will always be a mix of conventions at that point. Anyway, I don’t oppose the addition of these features. But I’d pick different ones for that 0.15 Apple employee to work on first.
@anirudhc It’s one of the many apps I’ve already got installed and have tried (but I always end up back in Apple Terminal).
@siracusa The default config is a bit off with the padding compared to Terminal but it's just a few tweaks to get it just right. It supports way more features and if you spend a lot of time in CLIs like Claude Code which take advantage of it, its worth it IMO. I know you don't like text based configs, but point Claude to the documentation and can it configure it exactly how you like it.
@anirudhc What enhancements does Claude Code have in Ghostty that it doesn’t have in Terminal?
@atpfm @siracusa Hi ATP/John- massive fan, subscriber for years, you were worried about terminal and other apps - #Ghostty as you know is a major one; their config file easily editable; suggest you use Gemini to re-write it for you to make it look like your fav. MacOS terminal - including font. Its much better than terminal for window management/splits on your stellar 6K
@neuroccm That’s one of the many I have installed, but I always end up back in Apple’s Terminal.
@v600 I don’t use either of those shells, but I swear I’ve seen it work with my shell. Maybe my config got messed up at some point. Anyway, earlier, a zsh user reported what works for them, so I’m on the trail…
@atpfm was the homework bit @marcoarment referred to the rec diffs #286? I think it must be but it wasn’t as long as I expected from the reference. (I had to try to find it because I’m having big feelings about homework right now).
@atpfm the Time Machine discourse in the past couple of weeks has been bizarre. Stating it corrupts itself regularly is a very strange thing to conclude, even with anecdata. Even more so given the often praised cloning alternatives use the same mechanisms.
@jimmyjamesuk Cloning apps like SuperDuper and CarbonCopyCloner do not use the same mechanisms as Time Machine to track, perform, and store their copies.
@siracusa The claim was that TM gets corrupted over time.These are just snapshots on an apfs volume. SD and CCC must be using these same mechanisms. In any case what on earth do you think these apps use to copy? Magic? It’s either asr or the file copy apis. The claim that TM corrupts itself is unsubstantiated. Feel free to ask Howard Oakley.
@jimmyjamesuk As for Time Machine corrupting itself, I’ve seen it with my own eyes many, many, many times. Feel free to search the Internet until you are satisfied that this is a thing that actually happens frequently enough to be a legitimate factor in backup strategy decisions.
@jimmyjamesuk The thing that gets corrupted is not the snapshot on the source volume (although snapshots can become corrupted), it’s the structures that store the multiple backups on the destination volume and the databases that track the state of those backups. SuperDuper just makes a single copy, so there’s none of that structure or database stuff, and CCC uses its own, different system to store and track multiple versions of files.
@atpfm I think @siracusa is over-complicating the node_modules backup problem. You don't exclude individual node_modules folders; you exclude your entire ~/Developer directory. Everything in there is either clonable from a public repo, a scratch project you don't care if you lose, or an important project pushed to a remote.
@kmcmahon Nah, I want my stuff backed up even between pushes.
@Daytonlowell I don’t think so.