Retrieve recent command form different shells

[GoogleCodeExporter]

I realise this might be difficult to implement considering the shells are 
actually different processes, but I'd still like to 'put on the table' this 
idea: Allow fetching of commands typed in a different shell in the current 
shell.

Example usage:
Running a certain code in a Python 3.3 shell, than running the same code in a 
python 2.7 shell: One could copy-paste, and one could also run the code from a 
file; one convenient option would be to have a shortcut set to retrieve the 
most recent commands typed in any shell as if they were typed in the current 
shell: Instead of pressing Up (as you'd do for recent commands in the current 
shell) you'd press something like Ctrl+Up and scroll commands irrespective of 
the shell they were typed in.

Original issue reported on code.google.com by zaha...@gmail.com on 9 Mar 2013 at 3:02

[GoogleCodeExporter]

Sharing command history between shells by default would be confusing, but as 
you point out, using something like Ctrl-Up or Alt-Up I can see being useful.

How useful is sharing commands between shells? Are there other use-cases beyond 
testing things on different Python versions?

The implementations does not have to be that hard, because command history is 
stored on the IDE side. There will have to be some changes to ensure that the 
commands from different shells are in the correct order.

This is a bit related to another idea: store command history between sessions 
(since in that case it was also a different process). If we're going to discuss 
this, we should look at the big picture. E.g. also taking a future command 
history tool into account.

Original comment by almar.klein@gmail.com on 9 Mar 2013 at 11:18

• Changed state: Accepted
• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

I think the question is "why does anyone needs to use more than one shell at a 
time", and beyond my answer to that - as part of the team, what's yours? What 
cases do you know that make use of multiple, concurrently-running shells?

Between sessions? I find IEP so resource-efficient that I just don't bother 
exiting :-P .

I think it's related to another issue: Workspaces and projects - I'll elaborate 
in the relevant issue.

Original comment by zaha...@gmail.com on 10 Mar 2013 at 12:41

[GoogleCodeExporter]

> What cases do you know that make use of multiple, concurrently-running shells?

  * Sometimes to temporarily work on something and not disrupt my long-running shell.
  * Comparing things between different Python versions (rare)
  * Running/testing a system where different processes communicate with each-other.

Original comment by almar.klein@gmail.com on 11 Mar 2013 at 1:09

[GoogleCodeExporter]

In all three example it would be beneficial to have this ability: In the first 
you could divert work from your running shell to a new one by retrieving at 
least the last few commands; the second is the case I'm dealing with; the third 
could allow you to send the same command from different processes without 
re-typing.

Original comment by zaha...@gmail.com on 11 Mar 2013 at 1:30

[GoogleCodeExporter]

As part of migrating our code repositories from Googlecode
to Bitbucket, all IEP issues are now tracked at 
https://bitbucket.org/iep-project/iep/issues

To view this issue, use this link (with X replaced by the issue number):
https://bitbucket.org/iep-project/iep/issue/X

Issues on Bitbucket can be created by anyone. Commenting on issues requires 
login via Bitbucket, Google, Twitter or Github.

Original comment by almar.klein@gmail.com on 11 Jun 2013 at 2:40

• Changed state: Moved