Run two Claude Code accounts simultaneously on macOS without re-authenticating by using separate configuration directories.
- Create Separate Config Directories
mkdir ~/.claude-account1 mkdir ~/.claude-account2
| const str1 = 'This is an example to test cosine similarity between two strings'; | |
| const str2 = 'This example is testing cosine similatiry for given two strings'; | |
| // | |
| // Preprocess strings and combine words to a unique collection | |
| // | |
| const str1Words = str1.trim().split(' ').map(omitPunctuations).map(toLowercase); | |
| const str2Words = str2.trim().split(' ').map(omitPunctuations).map(toLowercase); | |
| const allWordsUnique = Array.from(new Set(str1Words.concat(str2Words))); |
| # Adjust the following variables as necessary | |
| REMOTE=origin | |
| BRANCH=$(git rev-parse --abbrev-ref HEAD) | |
| BATCH_SIZE=500 | |
| # check if the branch exists on the remote | |
| if git show-ref --quiet --verify refs/remotes/$REMOTE/$BRANCH; then | |
| # if so, only push the commits that are not on the remote already | |
| range=$REMOTE/$BRANCH..HEAD | |
| else |
Problem: You want to maintain multiple different versions of python and keep packages separated based on projects that you're working on.
Solution: Use the pyenv, virtualenv tools along with the pyenv-virutalenv plugin to manage multiple versions of python and seamlessly integrate them with your projects' virtual environments.
How to make an application icon for macOS using
iconset&iconutil
The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.
The correct way of creating a private frok by duplicating the repo is documented here.
For this assignment the commands are:
git clone --bare git@github.com:usi-systems/easytrace.git
Last Updated: March 2023
IMPORTANT: Ignore the out-of-date steps below for getting Chromium keys.
Instead, read this up-to-date guide (Jan 2023) written by @LearningToPi.
P.S. Thank you to every contributor below who provided tips over the years on what should be a straightforward process: setting up Chromium for local development.
Long live the web!