this post was submitted on 06 Jan 2024
253 points (93.5% liked)

Asklemmy

43950 readers
596 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] morriscox@lemmy.world 1 points 10 months ago (1 children)
[โ€“] noughtnaut@lemmy.world 3 points 10 months ago

So using find was obviously a simplistic example. I know ctrl F is near-universal for a regular find operation, but let's imagine some other specialised feature of, say, a CAD application. "Find vertex in selected model" perhaps?

Oddly enough, I just discarded MacOS for a similar reason: yes, ctrl f is for "find" but, unlike on any other platform where ctrl shift f is "find in all files in project", on MacOS that is cmd shift f. WTAF, there goes my muscle memory out the window. In fact, the "when is it ctrl and when is it cmd" threw me for such a loop that it impacted my performance. Now that I'm back on Linux, the tool disappears and I can just do my job. Ahh.