253
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Jan 2024
253 points (93.5% liked)
Asklemmy
44173 readers
2283 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!
- Open-ended question
- 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.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
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 wherectrl shift f
is "find in all files in project", on MacOS that iscmd 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.