Steven Carpenter stevencarpenter

## delete_git_submodule.md

      
              1 file
            
          
              362 forks
            
          
              195 comments
            
          
              2383 stars
            
          
                myusuf3
                / delete_git_submodule.md
            
            
              Created
              November 3, 2014 17:36
            
              
                How effectively delete a git submodule.
              
          
    To remove a submodule you need to:

Delete the relevant section from the .gitmodules file.
Stage the .gitmodules changes git add .gitmodules
Delete the relevant section from .git/config.
Run git rm --cached path_to_submodule (no trailing slash).
Run rm -rf .git/modules/path_to_submodule (no trailing slash).
Commit git commit -m "Removed submodule "
Delete the now untracked submodule files rm -rf path_to_submodule


## python_environment_setup.md

      
              1 file
            
          
              17 forks
            
          
              1 comment
            
          
              37 stars
            
          
                Geoyi
                / python_environment_setup.md
            
            
              Created
              January 20, 2018 19:01
                — forked from wronk/python_environment_setup.md
            
              
                Setting up your python development environment (with pyenv, virtualenv, and virtualenvwrapper)
              
          
    Overview

When you're working on multiple coding projects, you might want a couple different version of Python and/or modules installed. That way you can keep each project in its own sandbox instead of trying to juggle multiple projects (each with different dependencies) on your system's version of Python. This intermediate guide covers one way to handle multiple Python versions and Python environments on your own (i.e., without a package manager like conda). See the Using the workflow section to view the end result.
Use cases


Working on 2+ projects that each have their own dependencies; e.g., a Python 2.7 project and a Python 3.6 project, or developing a module that needs to work across multiple versions of Python. It's not reasonable to uninstall/reinstall modules every time you want to switch environments.
If you want to execute code on the cloud, you can set up a Python environment that mirrors the relevant


## zsh-cheatsheet.md

      
              1 file
            
          
              41 forks
            
          
              16 comments
            
          
              376 stars
            
          
                ClementNerma
                / zsh-cheatsheet.md
            
            
              Last active
              June 6, 2024 20:07
            
          
    ZSH CheatSheet

This is a cheat sheet for how to perform various actions to ZSH, which can be tricky to find on the web as the syntax is not intuitive and it is generally not very well-documented.
Strings


Description
Syntax


Get the length of a string
${#VARNAME}


Get a single character
${VARNAME[index]}


## migrate-zsh-dotfiles.zsh
# This command moves your zsh dotfiles (.zshrc, .zsh_history, etc.)
# from the home directory to ~/.config/zsh. It's been verified to
# work correctly if you are using zsh4humans. With other zsh configs
# your mileage may vary.
#
# How to:
#
#   1. Close all terminals except one.
#   2. Copy-paste this command into the only remaining terminal.
() {
Description	Syntax
Get the length of a string	`${#VARNAME}`
Get a single character	`${VARNAME[index]}`
	# This command moves your zsh dotfiles (.zshrc, .zsh_history, etc.)
	# from the home directory to ~/.config/zsh. It's been verified to
	# work correctly if you are using zsh4humans. With other zsh configs
	# your mileage may vary.
	#
	# How to:
	#
	# 1. Close all terminals except one.
	# 2. Copy-paste this command into the only remaining terminal.
	() {