Installation of package Work with git.el Customization The git-emacs package Installation and customisation Work with existing repository Creation of new repositories Work with changes History of changes Work with tags & branches The magit package Installation and customisation Basics of work with package Work with changes Work with history of changes Tags, branches, and remote repositories The egg package Auxiliary packages git-blame gitsum egit We can work with Git using several packages — either use modules for VC и DVC packages, or use packages git.el, emacs-git, magit & egg packages. In first case we work with Git through standard interfaces of VC & DVC.
Welcome to ELPA, the Emacs Lisp Package Archive. Our goal is to make it simple to install, use, and upgrade Emacs Lisp packages. We supply package.el, a simple package manager for Emacs, and a repository of pre-packed Emacs Lisp code. If this is your first time here, you will want to install package.el. This is most easily done using our auto-installer.
Emacs Starter Kit This should provide a saner set of defaults than you get normally with Emacs. It’s intended for beginners, but it should provide a reasonable working environment for anyone using Emacs for dynamic languages. The main advantage of the Starter Kit is that it provides better default settings and bundles many useful libraries. The latest version is at http://github.com/technomancy/emacs-starter-kit/
let's do something about the ridiculous proliferation of the function keyword. Let's damp the syntactic noise required to use closures: (defun js-lambda () (interactive) (insert "function () {\n};") (backward-char 6)) (defun js-pretty-lambdas () (font-...
One of the most fundamental features that Emacs is missing among all the goodness available for programmers is the support for handling software projects. Not having a quick way to navigate between files, classes, methods and other symbols starts to significantly.I rolled two screen pages of Elisp or so, to make the basic operations I want to have available project-wide available. It served me very well ever since than. Recently, seeing some other attempts at solving this problem, I decided to cleanup and extend my solution a little bit and make it available for the general public. So the proel package was born. Proel makes one fundamental assumption - you have a set of dedicated directories for your software projects (ie. ~/code/work or ~/code/own), and each project has a single root directory in one of the projects directory, which name is also the name of the project (ie. ~/code/work/boring-app or ~/code/own/fun-app).