##// END OF EJS Templates
refactor to improve cell switching in edit mode...
refactor to improve cell switching in edit mode This code was repeated in both CodeCell and TextCell, both of which are extensions of Cell, so this just unifies the logic in Cell. TextCell had logic here to check if the cell was rendered or not, but I don't believe it is possible to end up triggering such a code path. (Should that be required, I can always just add back these methods to TextCell, performing the .rendered==True check, and calling the Cell prior to this, code mirror at_top would only return true on if the cursor was at the first character of the top line. Now, pressing up arrow on any character on the top line will take you to the cell above. The same applies for the bottom line. Pressing down arrow would only go to the next cell if the cursor was at a location *after* the last character (something that is only possible to achieve in vim mode if the last line is empty, for example). Now, down arrow on any character of the last line will go to the next cell.

File last commit:

r11729:5cc34183
r15754:d60e793e
Show More
set_up_fork.rst
68 lines | 2.0 KiB | text/x-rst | RstLexer

Set up your fork

First you follow the instructions for :ref:`forking`.

Overview

git clone git@github.com:your-user-name/ipython.git
cd ipython
git remote add upstream git://github.com/ipython/ipython.git

In detail

Clone your fork

  1. Clone your fork to the local computer with git clone git@github.com:your-user-name/ipython.git

  2. Investigate. Change directory to your new repo: cd ipython. Then git branch -a to show you all branches. You'll get something like:

    * master
    remotes/origin/master
    

    This tells you that you are currently on the master branch, and that you also have a remote connection to origin/master. What remote repository is remote/origin? Try git remote -v to see the URLs for the remote. They will point to your github_ fork.

    Now you want to connect to the upstream `ipython github`_ repository, so you can merge in changes from trunk.

Linking your repository to the upstream repo

cd ipython
git remote add upstream git://github.com/ipython/ipython.git

upstream here is just the arbitrary name we're using to refer to the main ipython_ repository at `ipython github`_.

Note that we've used git:// for the URL rather than git@. The git:// URL is read only. This means we that we can't accidentally (or deliberately) write to the upstream repo, and we are only going to use it to merge into our own code.

Just for your own satisfaction, show yourself that you now have a new 'remote', with git remote -v show, giving you something like:

upstream     git://github.com/ipython/ipython.git (fetch)
upstream     git://github.com/ipython/ipython.git (push)
origin       git@github.com:your-user-name/ipython.git (fetch)
origin       git@github.com:your-user-name/ipython.git (push)