Mac OS plist problems with keyboard and screen capture?

Open
#230 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
macos

Research direction

Start with the linked blog reports and the described keyboard configuration and screen-capture symptoms. Inspect the user-level and system-level Library locations mentioned for the relevant plist files, then verify the keyboard remapping and Cmd-Shift-4 clipboard behavior; done means both reported problems are resolved.

Written by the indexing model from the issue text.

Description

From the blog: I reported a problem with my Mac keyboard configuration, now I can't do screen captures. As I do more searching on each of these problems what's implicated in both cases is a problem of corrupt plists. I don't know very much about these files, but I do understand what they're for. It's possible I did something that blew out some of these files. I've started a thread to ask for help getting to the bottom of this.

The keyboard problem is this -- I want to map Ctrl to Cmd and vice versa, but the change won't stick. I switched the keyboard, rebooted the machine, problem persists. The problem appears to be with the setup of the Mac.

The screen capture problem -- I do a screen capture with Cmd-Shift-4, switch into the Preview app, and the New From Clipboard command is disabled. It's still there after a machine reboot, and the problem isn't only in Preview, I can't paste into the browser either.

I've read lots of support queries but I don't have either of the plist files people keep pointing to.

I've looked in my user-level Library and the system-level one.

Dominant language
HTML
Stars
134
Forks
10
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Operating Systems issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.