From ArchWiki
Revision as of 13:16, 30 December 2016 by Nl6720 (talk | contribs) (Shell frameworks: re)
Jump to: navigation, search

Shell frameworks

Currently there is no easy way to know if a shell configuration in dotfiles#Repositories uses a framework without checking each repository. I think it would be better if used frameworks were listed in brackets next to shell name. -- nl6720 (talk) 13:37, 22 November 2016 (UTC)

Since no one objected, I changed "Shell" to "Shell (shell framework)". Let's see if people start listing them. -- nl6720 (talk) 13:16, 30 December 2016 (UTC)

Bare repository and alias method

Hi all, I'd love to expand this out to include the method coved in this HN discussion. The simplicity of it is rather beautiful and it keeps the tracking isolated from the rest of $HOME. Before I do that, I'm new here so don't want to just start making sizeable edits with some form of discussion. Can anyone see any advantages of the currently listed gitignore method that this does not provide? -- Kimburgess (talk)

So basically all it does is hide the untracked files in the commit window? IOW, a half-baked variant of Dotfiles#Using_gitignore which actually ignores the files instead of hiding them. One example where this is better if you end up running git clean. If the files are not ignored, they'd end up deleted. -- Alad (talk) 12:51, 26 December 2016 (UTC)
Almost. Although it's hiding rather than excluding, there's one important difference — the actual repo is in a sub directory, not the base of $HOME. This means when you're sitting in the $HOME tree, attempting to run any vanilla git commands will fail (as it's not a repo). This protects you a little, but also stops any git cruft from showing for users running with git aware prompt strings (i.e. showing current branch / state). You could add a wildcard exclusion to this method as well, but it would come with the tradeoff of losing visibility of what you don't have tracked in your dotfiles.--Kimburgess (talk) 23:52, 26 December 2016 (UTC)