Showing posts from February, 2020

GIT COMMANDS Easy to Learn -

GIT COMMANDS  We divide Git into high level ("porcelain") commands and low level ("plumbing") commands. High-level commands (porcelain) We separate the porcelain commands into the main commands and some ancillary user utilities. Main porcelain commands git-add[1] Add file contents to the index git-am[1] Apply a series of patches from a mailbox git-archive[1] Create an archive of files from a named tree git-bisect[1] Use binary search to find the commit that introduced a bug git-branch[1] List, create, or delete branches git-bundle[1] Move objects and refs by archive git-checkout[1] Switch branches or restore working tree files git-cherry-pick[1] Apply the changes introduced by some existing commits git-citool[1] Graphical alternative to git-commit git-clean[1] Remove untracked files from the working tree git-clone[1] Clone a repository into a new directory git-commit[1] Record changes to the repository git-describe[1] Give an object a human readable name based on an

Don't like IDEs? Try

Like most developers, I search and read source code all day long. Personally, I've never gotten used to integrated development environments (IDEs), and for years, I mainly used  grep  and copy/pasted file names to open Vi(m). Eventually, I came up with this script, slowly refining it as needed. Its dependencies are  Vim  and  rlwrap , and it is open source under the Apache 2.0 license. To use the script,  put it in your PATH , and run it inside a directory of text files with: grepgitvi <grep options> <grep/vim search pattern> It will return a numbered list of search results, prompt you for the number of the result you want to use, and open Vim with that result. After you exit Vim, it will show the list again in a loop until you enter anything other than a result number. You can also use the Up and Down arrow keys to select a file; this makes it easier (for me) to find which results I've already looked at. It's simple and primitive compared to modern IDEs, or eve