Professional Documents
Culture Documents
ID: 108512924
Class: CSE-300-03
Homework #2 - Propose Topics for Assignments
developers when the project is still small and thus they usually look at very bad user guide which
promotes bad source version control practices. Then when the project gets larger or hits some hard-tobeat errors that need a rollback, the team faces a mess of branches and commits that they have no way
to escape from. Sometimes, incompetency in using Git & Bitbucket can slow down the development
process and introducing bugs to the software through merging up conflicting source-code branches.
Vim, Emacs, etc. especially when coding in lightly-library-dependent languages such as HTML, CSS,
JavaScript, C, C++, etc. However, learning how to use and configure these editors to suite ones needs
still proposes big challenges that prevent users from switching from the user-friendly IDE to the fastand-furious Vim or Emacs.
a. Literature Review: Why switching to Vim or Emacs instead of using an IDE or Vim/Emacs IDE
keybindings? What are the command-line alternatives to these 2 editors?
b. Press Release: Announce the release of my personal dotfiles, particularly vimrc which vastly
extends the features provided by default by the Vim editor.
c. User Manual: My tricks for using Vim more effectively, including key-remapping and cheat sheet
for source code navigation using Vim keys.
I chose this topic because I love using Vim and I admit myself addicted to customizing and writing
extensions for Vim. Also, with the increasing popularity of Linux and Mac OSX, more and more
people nowadays have access to UNIX terminal tools such as cat, grep, vi, etc., making UNIX no
longer administrators and geeks-exclusive. Therefore, I believe having a hand-on comprehensive guide
to Vim customization is very necessary for even novice computer users.