3 ms·

I am so thankful to members of the HN community for stepping and and lending a helping hand with info. Re line start and line end, those key combos rarely work

I am so thankful to members of the HN community for stepping and and lending a helping hand with info. Re line start and line end, those key combos rarely work (ctrl-a and ctrl-e are more common, but guess what? ctrl-a and ctrl-e behave like Win Ctrl-Home and Ctrl-End while composing this reply in Chrome, while fn-left moves to the start of the line and fn-right does nothing at all. Go figure.) It was document start and document end (or, even a standard PgUp/PgDn) that seemed missing. Open doesn't handle file paths, only directories, and doesn't work if I've got the File Open dialog going. These (and the need to research and review commands, instead of any GUI support) was what I meant by secret handshakes. The original UI concepts included the idea of making settings and functions discoverable via UI as well. No love for cmd32 here, mind you. A real shell would help that world out quite a bit. Wonder if the preferences would go the opposite way if I'd started differently.

pfranz 5y ago
> Open doesn't handle file paths, only directories, and doesn't work if I've got the File Open dialog going. It opens as if you had clicked it in Finder. Are you wanting something like `open $(dirname ${file})`? File Open dialogs are oddballs on macOS, Linux, and Windows. I remember some Linux apps tried unifying them, but it was immediately obvious why they're different. FWIW drag d&d and Cmd-Shift-G work. > These (and the need to research and review commands, instead of any GUI support) was what I meant by secret handshakes. I don't think that dream applies to much outside of the core WIMP on any platform. Especially, when interacting with a command line. I feel like macOS does a better job by showing shortcut keys in more places, highlighting when they're triggered, and having Help > Search. It's unfortunate that gesture-based interfaces are way worse. > while composing this reply in Chrome Non-native apps are particularly annoying. Firefox notoriously had a bug open for 20+ years for adding native macOS context menus. Text shortcuts still don't work.

pfranz 5y ago

> Open doesn't handle file paths, only directories, and doesn't work if I've got the File Open dialog going. It opens as if you had clicked it in Finder. Are you wanting something like `open $(dirname ${file})`? File Open dialogs are oddballs on macOS, Linux, and Windows. I remember some Linux apps tried unifying them, but it was immediately obvious why they're different. FWIW drag d&d and Cmd-Shift-G work. > These (and the need to research and review commands, instead of any GUI support) was what I meant by secret handshakes. I don't think that dream applies to much outside of the core WIMP on any platform. Especially, when interacting with a command line. I feel like macOS does a better job by showing shortcut keys in more places, highlighting when they're triggered, and having Help > Search. It's unfortunate that gesture-based interfaces are way worse. > while composing this reply in Chrome Non-native apps are particularly annoying. Firefox notoriously had a bug open for 20+ years for adding native macOS context menus. Text shortcuts still don't work.