Skip to content

chore(iterm2): profile working directory as ~, not an absolute home path - #6

Merged
froppa merged 1 commit into
masterfrom
chore/no-home-path-in-iterm-profile
Sep 5, 2026
Merged

chore(iterm2): profile working directory as ~, not an absolute home path#6
froppa merged 1 commit into
masterfrom
chore/no-home-path-in-iterm-profile

Conversation

@froppa

@froppa froppa commented Sep 5, 2026

Copy link
Copy Markdown
Owner

The saved iTerm2 profile pinned Working Directory to one machine's absolute home path — wrong on any other machine, and a developer path in a public repository. iTerm2 expands ~ in that field.

Not touched here, for you to decide: the repository's history also holds an initial-commit LAN SSH target (user@192.168.x.x) and two encrypted .age files that were later removed. Purging those means rewriting public history (force-push, breaks clones/forks); the encrypted files remain unreadable without a key that only you hold.

The saved profile pinned Working Directory to one machine's absolute home
path, which is both wrong on any other machine and a developer path in a
public repository. iTerm2 expands ~ in that field.
@froppa
froppa merged commit cd6eb2a into master Sep 5, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant