Changes between Initial Version and Version 1 of Ticket #22452, comment 29


Ignore:
Timestamp:
03/08/17 13:12:17 (4 years ago)
Author:
SimonKing
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #22452, comment 29

    initial v1  
    66I tried, and it seems it won't work. At least it won't work better than the current approach. So, I'll keep it.
    77
    8 Andreas Paffenholz has just pointed out to me how to parse the output of `apropos "";` in order to not only get the functions of the current application, but also to get member and member function names, which is important for tab completion respectively for knowing what a Sage user means when she type `X.name_of_something`: An property of X? A polymake function that, when called, is applied to X '''and''' further given arguments? A member function of X that, when called, is evaluated '''only''' on the further given arguments?
     8Andreas Paffenholz has just pointed out to me how to parse the output of `apropos "";` in order to not only get the functions of the current application, but also to get member and member function names, which is important for tab completion respectively for knowing what a Sage user means when she types `X.name_of_something`: An property of X? A polymake function that, when called, is applied to X '''and''' further given arguments? A member function of X that, when called, is evaluated '''only''' on the further given arguments?
    99
    1010Also I made some experiments with !KeyboardInterrupt. Sometimes I found that it crashed the interface (i.e., `polymake._expect` became None), and so far I don't understand why this can happen, and why it doesn't ''always'' happen.