File tree Expand file tree Collapse file tree 1 file changed +16
-3
lines changed Expand file tree Collapse file tree 1 file changed +16
-3
lines changed Original file line number Diff line number Diff line change @@ -623,11 +623,12 @@ Message type: ``history_request``::
623
623
# So far, this can be 'range', 'tail' or 'search'.
624
624
'hist_access_type' : str,
625
625
626
- # If hist_access_type is 'range', get a range of input cells. session can
627
- # be a positive session number, or a negative number to count back from
626
+ # If hist_access_type is 'range', get a range of input cells. session
627
+ # is a number counting up each time the kernel starts; you can give
628
+ # a positive session number, or a negative number to count back from
628
629
# the current session.
629
630
'session' : int,
630
- # start and stop are line numbers within that session.
631
+ # start and stop are line (cell) numbers within that session.
631
632
'start' : int,
632
633
'stop' : int,
633
634
@@ -657,6 +658,18 @@ Message type: ``history_reply``::
657
658
'history' : list,
658
659
}
659
660
661
+ .. note ::
662
+
663
+ Most of the history messaging options are not used by Jupyter frontends, and
664
+ many kernels do not implement them. If you're implementing these messages in
665
+ a kernel, the 'tail' request is the most useful; this is used by the Qt
666
+ console, for example. The notebook interface does not use history messages
667
+ at all.
668
+
669
+ This interface was designed by exposing all the main options of IPython's
670
+ history interface. We may remove some options in a future version of the
671
+ message spec.
672
+
660
673
.. _msging_is_complete :
661
674
662
675
Code completeness
You can’t perform that action at this time.
0 commit comments