Apple wins the Pepsi Challenge for the same reasons, sweet and fizzy in your first taste. Some like the full drink, many don’t.
Apple wins the Pepsi Challenge for the same reasons, sweet and fizzy in your first taste. Some like the full drink, many don’t.
Command-Shift-Period
>As a default?*
defaults write com.apple.Finder AppleShowAllFiles true; killall Finder
>How do you copy-paste file or folder paths between terminal and Finder?
Drag and drop the icon into a Terminal window.
And regarding gestures or shortcuts, if you put in the same effort that you did for Windows, you can find everything you need on the Mac.
Home/End on macOS typically jump to the start and end of a document - which annoys me as I prefer Home/End to jump to the beginning and end of the current line - I just don’t like Ctrl+ArrowKeys, and the Cmd-key tires my pinky. At least macOS let’s you remap Cmd/Ctrl/Alt - I wish Windows would do the same.
I believe that they can be customized and extended as well.
Terminal is a bit different for me since they keyboard can be customized; with my configuration, fn-left/fn-right are sent to the terminal session while cmd-up/cmd-down affect the scroll bars for the window.
Drag the file or folder from Finder to your terminal to copy the path.
To open a file or folder in Finder from your terminal simply run `open <path>`.
The open command also works with any url whose protocol has a registered handler, like slack:// or https://. With a path the file:// protocol is assumed, and Finder is its handler. Moreover since this is a unix system with good documentation, `man open` will help you with more advanced usage.
Thank you for the open command mention. Suppose it's a path I'm trying to bring to a File Open or File Close dialog?
Cmd-C the file in Finder and Cmd-V in Terminal pastes the escaped path. You can also drag and drop the file. To go the other way I used the `open` command (which acts like clicking something in Finder). For example, `open .` or Cmd-Shift-G (Go -> Go to Folder...)
On laptops, Fn-Left Arrow (Home) scrolls to the top and Fn-Right Arrow scrolls to the bottom (End). I agree it's not obvious, but it's more ergonomic than moving your hand to where the Home/End traditionally are on a keyboard. It's also exactly the same as on a 'LG 17" gram Laptop'--the second image result when I searched for "laptop."
I don't slight people who prefer Windows and won't argue macOS gets things right, either, but I find the Windows UI frustrating especially in tandem with a terminal. I used Windows exclusively from 1 or 3-whatever until XP, dropped it, then took a job when 10 was first being released and tried to give it an honest try. I'm sure it's just my familiarity and preference, but I greatly prefer macOS and almost any Linux GUI to Windows.
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.
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.