##// 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:

r4895:329e2362
r15754:d60e793e
Show More
test_autocall.py
45 lines | 971 B | text/x-python | PythonLexer
"""These kinds of tests are less than ideal, but at least they run.
This was an old test that was being run interactively in the top-level tests/
directory, which we are removing. For now putting this here ensures at least
we do run the test, though ultimately this functionality should all be tested
with better-isolated tests that don't rely on the global instance in iptest.
"""
from IPython.utils import py3compat
@py3compat.doctest_refactor_print
def doctest_autocall():
"""
In [1]: def f1(a,b,c):
...: return a+b+c
...:
In [2]: def f2(a):
...: return a + a
...:
In [3]: ;f2 a b c
Out[3]: 'a b ca b c'
In [4]: assert _ == "a b ca b c"
In [5]: ,f1 a b c
Out[5]: 'abc'
In [6]: assert _ == 'abc'
In [7]: print _
abc
In [8]: /f1 1,2,3
Out[8]: 6
In [9]: assert _ == 6
In [10]: /f2 4
Out[10]: 8
In [11]: assert _ == 8
In [11]: del f1, f2
"""