chore(iterm2): profile working directory as ~, not an absolute home path - #6
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.agefiles 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.