You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the history is mixed for all open consoles it would make the most sense if the history was separated for each console.
From a use case prospective I think this isn't a good idea to have the history mixed and it would be better and simpler to have IPython take care of the history entirely as per the changes in #7141. We can just take what the console gives for it's history and not worry about it...it works great. This would require us to have one history tab per console, but luckily the history widget already has tabs implemented.
Currently, If you change between tabs and run commands in each the history gives you a mess of code that is most likely unassociated and you can tell what commands were executed in each console. The up arrow history at the ipython prompt keeps the history separate and when both sessions are closed the two histories are appended into the main history one console after the other so the code is still in blocks that are still associated.
The hardest part would be to synchronize the tab switching between the consoles and the history.
@ccordoba12 suggest to use a QStackedWidget like the variable explorer does instead of tabs
The text was updated successfully, but these errors were encountered:
CAM-Gerlach
changed the title
Have the History widget dislpay a separate history for each console
Have the History widget display a separate history for each console
May 20, 2018
It would be quite easy to do, If you replace "iPython history" in register_client by the name of the console, you have a new tab with the correct name.
The tab are not automatically switched but this should not be a big problem.
The only issue I would see is that the log loaded from the file would be the same for all log tabs.
@impact27 I think the idea is a redesigned history widget without tabs but using QStackedWidgets. In this way the history widget only shows the history of the currently displayed console. This would be similar to the way the variable explorer works currently.
Yes, that's the idea. The fact that after a restart the history of all consoles will be mixed up and exactly the same makes me prefer this alternative over the one of one history tab per console.
Currently the history is mixed for all open consoles it would make the most sense if the history was separated for each console.
From a use case prospective I think this isn't a good idea to have the history mixed and it would be better and simpler to have IPython take care of the history entirely as per the changes in #7141. We can just take what the console gives for it's history and not worry about it...it works great. This would require us to have one history tab per console, but luckily the history widget already has tabs implemented.
Currently, If you change between tabs and run commands in each the history gives you a mess of code that is most likely unassociated and you can tell what commands were executed in each console. The up arrow history at the ipython prompt keeps the history separate and when both sessions are closed the two histories are appended into the main history one console after the other so the code is still in blocks that are still associated.
The hardest part would be to synchronize the tab switching between the consoles and the history.
@ccordoba12 suggest to use a QStackedWidget like the variable explorer does instead of tabs
The text was updated successfully, but these errors were encountered: