This is my brew.env. cat ~/.homebrew/brew.env HOMEBREW_CASK_OPTS="--no-quarantine" HOMEBREW_CASK_OPTS="--appdir=~/Applications" HOMEBREW_CLEANUP_MAX_AGE_DAYS=2 HOMEBREW_NO_ANALYTICS=1 The second line HOMEBREW_CASK_OPTS="--appdir=~/Applications" is working, but first line HOMEBREW_CASK_OPTS="--no-quarantine" is ignored. How to specify both env variables? I tried also HOMEBREW_CASK_OPTS="--no-quarantine --appdir=~/Applications" on the same line, but both variables did not work.

I have a german keyboard. On this keyboard you can access the pipe ('|') by pressing Option-7. I recently updated to Sequoia 15.5 (I don't know the old version). After the update I can't enter the pipe symbol anymore. When I press Option-7 the next key afterwards is repeated 7 times. So Option-7 and then 'a' gives 'aaaaaaa'. This initially only happend in the Terminal app but now also in the shell of my IDE (IntelliJ). iTerm is working without problems. When I press other combinations like Control-3 the next key is also repeated this number of times (like 3 times). I wasn't able to find anything on the internet, or my search phrase was poor.

I recently had to reinstall the developer tools using

-select —install

, but noticed that the install was completed with my efficiency cores rather than my performance cores. I know this because iStatMenu showed me that my four efficiency cores were at 100% most of the time while the performance cores were inactive. Is there a way I can manually set the priority of a process? Can I tell a process to run on the performance cores if needed? Ideally, it would actually use as many cores as it had threads, and run on all 8 cores simultaneously. An answer here describes how to run a task with the efficiency cores, which is equally useful, but I couldn't figure out how to adapt that technique to use the performance cores instead.

I am on Catalina 10.15.7 and use Karabiner-Elements 13.3. When I use the rule shown below for opening Terminal nothing happens unless Terminal is in focus (you can see Terminal on the menu bar). Seems like something to do with security permissions. When I run the script itself from within iTerm (not Terminal) I got a pop up asking for allowing "access to control". Once accepted the shortcut worked when either Terminal or iTerm was in focus. Obviously I want the shortcut to work regardless of what is in focus. How to achieve that?

{
  "title": "Open Terminal",
  "rules": [
    {
      "description": "Open Terminal",
      "manipulators": [
        {
          "type": "basic",
          "from": {
            "modifiers": {
              "mandatory": [
                "left_control",
                "left_alt"
              ]
            },
            "key_code": "t"
          },
          "to": [
            {
              "shell_command": "osascript -e 'tell app \"Terminal\"' -e 'do script \"tmux\"' -e 'end tell'"
            }
          ]
        }
      ]
    }
  ]
}

I'm unable to change my Terminal app profile (color theme) even when I change it in the preferences. I selected Homebrew as my profile, closed Terminal and reopened it - but it won't actually change to Homebrew. It shows the basic (default) profile. Is it possible that I have an issue with my .bash_profile, .bashrc, or .profile? I'm trying to change it to the profile "Homebrew" seen below:

Is there a way to share a file over AirDrop via Terminal on Mountain Lion? How so?

I'm hoping to build on my embarrassingly-limited knowledge of the command line, and I know there are a ton of great resources out there. I'm wondering if there are any books or other resources that are tailored specifically to the OS X user running Terminal. Thanks.

Basically, I want to sync my repo on iPad with git, but I can't find the public key, so I can't clone the repo. I found three different guides, but none of them has worked out for me so far. I first tried following the instructions [here](https://www.warp.dev/terminus/git-clone-ssh) and [here](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) . I generated an SSH key with ssh-keygen -t ed25519 -C “user@example.com” After that, I got a randomart and a message, telling me where the public key could be found. The next step, according to the guides is to double check the public key is where it's at. The first guide said to run ls ~/.ssh and I'd see where the keys are. But I am presented with an error message. When I go ahead and run cat ~/.ssh/id_ed25519.pub, I'm told that no file or directory can be found. The same thing happens when I copy the entire path rather than enter the short one. The second guide said to add the key to SSH agent and to run $ eval "$(ssh-agent -s)" > Agent pid 59566 But a-Shell tells me that the command doesn't exist. This second guide also said > Depending on your environment, you may need to use a different command. For example, you may need to use root access by running sudo -s -H before starting the ssh-agent, or you may need to use exec ssh-agent bash or exec ssh-agent zsh to run the ssh-agent. But neither sudo nor exec exist as commands. I found a [third guide](https://bianshen00009.gitbook.io/a-guide-to-a-shell/basic-tutorials/configure-lg2-for-version-controlling) , but it also didn't tell me how to get the public key, only that I should link it with git. I tried ssh-agent, and I'm told that I can now run ssh-add, so I tried that, but it didn't work. In the list of commands I got from help -l, I saw ssh-copy-id So I tried that and ran ssh-copy-id ~/.ssh/id_ed25519, but that didn't work, tried it again ssh-copy-id ~/.ssh/id_ed25519.pub. That didn't work either. I got Error: ssh: Could not resolve hostname and nodename nor servnamer provided, or not known. I'm not sure what I'm missing here. I've done the same on Android and I got the repo to sync, but iOS has me stumped.

I am using a Danish keyboard language and Danish keyboard layout. When typing in my browser or other applications on my computer, I can make a backslash. In my case I use the combination shift + option + /. However, when I enter the terminal (either through VSC or directly from my computer), I can't make backslash through the key combination. Nothing happens. I am using bash. I have also tried the Z shell instead, but I can't make backslash there as well. For similar characters I can use their key combinations without any problems in the bash terminal. E.g. shift + option + ( makes an opening curly bracket '{'. Thus, the key combination for backslash works fine in browser and applications, but not in the terminal. Is there a way to add a new key combination for the terminal?

I've been tweaking the theme / color preferences in the Terminal.app a bit, after a while I found that when pressing a diacritical mark/accent/dead key there's a **highlighted yellow rectangle** showing a preview of the accent you're inputting. Here's an screenshot: It turns out is not editable from the terminal preferences. In fact it seems like a system wide setting. But it IS incredibly annoying to guess what it is displaying with a dark background + lighter text color in the terminal app: Is there anyway to change that yellow color to correctly read those symbols no matter what text/background color is?

Just moved off from windows into a Mac. I used to use Putty and it has a feature of logging sessions into a folder so everything that happens (stdin/out) goes also to a folder for historic record. I would like to have the same thing with Mac Terminal app.

I’ve been having problems with my MacBook Air (Early 2015). Since installing an update to 10.13.6 (From 10.13.3, I believe) the computer freezes once the progress bar fills up on the login screen. Rebooting has not resolved the issue. I have tried to enter safe mode and recovery mode (Command-R); the result is the same, and the computer will not transition to the recovery mode interface. Option-command-R and Shift-option-command-R generate error messages -5101 and -2003 respectively, which don’t seem to be often cited on these forums. Similarly, a PRAM/NVRAM reset has been unhelpful. Single user mode (Command-S) works fine, but I haven’t found any set of commands which has fixed my problem. Verbose mode is inconclusive, and the text stops updating after a minute or two, except for ‘busy timeout ‘IGPU’’ messages. I have also considered that this may be a hardware issue, but have never experienced problems with this laptop before. Has anyone experienced something like this before or does anyone have a possible solution? Cheers Edit: Attached are two images of the final screen before timeout messages start happening. The command line doesn’t seem entirely consistent each time I start it up: some additional messages appeared here. Unfortunately, it doesn’t let me post a video.   Note: the image at the bottom is of the latest state of the screen. Regarding Target Disk mode, I don’t have a second computer on hand right now, but I’d be able to set that up in the near future. I don’t have an external display.)  UPDATE 2:  ![enter image description here] (https://i.sstatic.net/04dfs.jpg)   These are logs after entering the command ‘exit’. I got IGPU messages after this; this time though, the syntax is ‘kextd stall, (240s): ‘IGPU’. Hopefully this is helpful, but from what I understand it could mean any number of things. Presumably the AppleKeyStore messages are also useful? 1. I now have access to another computer. Since this mode is mostly used to get files from a Mac, what specifically should I be looking out for? 2. As I mentioned initially, ‘Option-Command-R’ and ‘Shift-Option-Command-R’ don’t work either: I have since tried them again, and ‘Option-Command-R’ returns error message -5101 (after typing in correct internet password). ‘Shift-Option-Command-R’ boots into Internet Recovery (with the spinning globe), but then seems to go back to the login screen, which is always a dead end. So I guess I should be looking for any fix to this which doesn’t require the login screen to take effect. I haven’t been able to find a solution allowing me to reinstall macOS and bypass recovery mode - is that possible? EDIT: When the Mac is on, I also sporadically get the voiceover message ‘To choose English as your main language, press the ‘return’ key...’ I think this has something to do with recovery mode.

**Problem** On my new M3 Mac Pro (36 GB RAM) running macOS Sequoia 15.3.2, launching a new interactive shell in both the built‑in Terminal.app and the GPU‑accelerated Ghostty takes orders of magnitude longer than on my Linux/Windows boxes. I frequently use tmux, and spawning new panes can take > 1 second, whereas on Linux/Windows it’s real 0.15; user 0.04; sys 0.03
real 0.13; user 0.03; sys 0.03
real 0.14; user 0.03; sys 0.03
**With plugins enabled:** 3. compinit tweaks & zprof analysis - Precompiled cache, removed old dump files, no significant improvement. 4. Homebrew & some cli tools also feel sluggish, suggesting a deeper system issue. **Environment** - macOS: Sequoia 15.3.2 - Hardware: Apple M3 Pro, 36 GB RAM - Shells tested: - /bin/zsh (default) - /bin/bash - Measurement tool: /usr/bin/time and zprof **Questions** Has anyone observed 1-2 second cold startup on an M3 Mac for Zsh, even with minimal config?
Are there known system-wide factors (e.g. Rosetta layers, filesystem checks, notarization delays) that could slow down every new shell instance?
How can I diagnose what’s happening during that 1 second (e.g. tracing dynamic libraries, file-system stalls)?
Any tweaks or workarounds to get terminal/spawn times closer to < 0.1 s? Thanks in advance for any insights! EDIT: After using zcomet instead of zinit and p10k instead of starship. I think the issue is mostly connected to cold start vs. warm start of the terminal. If everything is cached, the startup time is in the ball park of 5ms which is fine. But the cold start of the terminal after the recent os update is 2-6 seconds and really annoying. I also thought about a stupid way of just opening a terminal in the background with a cron job, but the terminal isn't a tty and therefore not useful. Any ideas how I can reduce the cold start time or keep the terminal also "warm"?

How, from a Terminal, do I make a plain text file and a folder?

I am racking my head for an [old login password] (pass1) that is gone from my keychain but still in a Time Machine backup. The password I seek [encrypts an external drive] (pass2), which used to unlock automagically by virtue of being in the keychain so I did not memorise it. However losing (pass2) now would also mean losing a good deal of data. I still know some of the passwords in that keychain (pass3), but I have forgotten the master password (pass1). Unfortunately I have been using complex passwords for some time now and will not be able to brute force it with the likes of hashcat easily. Nevertheless, I hope to recover the old login password (pass1) by deducing what the hash and salt of the keychain is from the other known passwords (pass3). Does macOS store remnants or clear version of passwords in any locations? edit: I was quite lousy with my password and found some old passwords in Copyclip, an app that logs text copied to clipboard (security risk, yes); I also have Near Lock which I think might log some keystrokes but I am still investigating, and am wondering if there might be other somewhat common places that might have passwords stored due to poor security practices.

With my SSL certificate passwords stored using ssh-agent I just need to provide a master passphrase to unlock the keychain in the terminal. Generally this isn't an issue, but when the computer restarts I am left typing in the passphrase into each terminal tab. This can be up to 10 tabs, which is fairly annoying. Is there any way to have the ssh-agent keychain unlocked prior to the terminal tabs opening, so I only need to type it once?

I'm fairly new to MacOS, when i try to directly do

pip install

the terminal whether in VScode or the normal mac terminal gives the output as

zsh: command not found: pip

But if i execute the same command after activating my virtual environment, it works. can anyone help in explaining this.

When use the terminal in macOS, press

+shift+N

can turn on this "New Command" window, which doesn't store all the commands executed in the terminal. From ~/.zsh_history, I can see that the commands were executed in the form of xxxxx;exit By deleting those lines from ~/.zsh_history, the wrong commands still remain in the New Command Window. How can I delete those lines like

and

show cores

so that they won't show in New Command. Thanks PS: This

+Shift+N

New Window is quite useful, feels like a

... as ...

function in python and will completely quit when closing, unlike directly executing some commands which may leave frozen threads after

+c

.

I tried to use the accessibility/zoom feature on a terminal window which is running a ssh session to a remote FreeBSD host and where after login to the remote system a "screen" session has been launched. It appears that the "zoom" feature is only aware of the original text that was displayed in the terminal window before screen was launched, so is rendering a zoomed version of that original text instead of what is currently displayed. Can anyone suggest what option settings might enable the zoom feature to display the correct text?

Every time I open a new Terminal window or tab, it shows this error before the shell prompt:

/etc/zshrc_Apple_Terminal:14: INSIDE_EMACS: parameter not set

(I don't use emacs, and I've noticed no other ill effects.) As that indicates, my default shell is zsh.  The error also appears when starting a new zsh instance from within any existing shell. Line 14 of /etc/zshrc_Apple_Terminal is:

if [ -z "$INSIDE_EMACS" ]; then

So that file clearly expects $INSIDE_EMACS to be set, and gives the error when it's not.  But I've not been able to find out what should be setting it (that's clearly not working on my machine).  I have various user-level shell startup files, but none of those seem to be the cause, as that message appears before any of them have run. There's an obvious workaround: edit that file (as root) and e.g. replace $INSIDE_EMACS with ${INSIDE_EMACS-} (which silently expands to empty string if the variable's not set).  That works fine — but every time I upgrade macOS, that file gets replaced and the error is back!  (This has happened with every upgrade since around macOS 12 Monterey; I'm now on the current macOS 15.5.) I've not found this error online (other than my own mention in [this answer](https://apple.stackexchange.com/a/439072/291214)) , so I'm guessing it's not common, and probably triggered by some quirk of my own set-up.  But I haven't found any possible cause. What can I do to make this error go away for good?  What _should_ be setting $INSIDE_EMACS?