Bug 181402 - [usability] Specify commands to be run on shell startup
Summary: [usability] Specify commands to be run on shell startup
Status: ASSIGNED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: dsdp.tm.rse-inbox CLA
QA Contact: Martin Oberhuber CLA
URL: http://www.eclipse.org/newsportal/art...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-06 08:50 EDT by Sander Klous CLA
Modified: 2012-11-19 04:57 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sander Klous CLA 2007-04-06 08:50:08 EDT 
I would like to be able to specify a number of commands to be executed on RSE shell startup (SSH). 

A thread with a detailed discussion on this topic is on the target management mailing list and starts here:

http://www.eclipse.org/newsportal/article.php?id=116&group=eclipse.dsdp.tm#116

Thanks,
Sander
Comment 1 Martin Oberhuber CLA 2007-05-09 11:17:21 EDT 
I'm not sure we'll get to this for 2.0
Comment 2 Martin Oberhuber CLA 2007-05-30 17:22:27 EDT 
Dave - this request seems to make sense since it's asking for a generic way of running commands when connecting an RSE shell. Such commands can be used to set up a remote environment -- which can be extremely helpful.

Implementing this would be really easy since the commands could be sent to the remote on shell startup just like the "cd" command is currently sent.

Only problem is that we'd need an editbox with an NLS label in the UI. What do you think about this? - There is a similar request for running commands on remotecdt application launch, are you also translating the remotecdt NLS strings?
Comment 3 David Dykstal CLA 2007-05-30 18:39:35 EDT 
Are we considering this for 2.0?
Comment 4 Martin Oberhuber CLA 2007-05-30 18:56:53 EDT 
Maybe, depending on what you think. I consider this a very strong improvement at little cost - and a viable workaround for SSH not being able to set user-defined environment variables, like dstore does.

If you're concerned about the NLS change and/or the general impact, I could also target 2.0.1.
Comment 5 David Dykstal CLA 2007-05-30 23:55:37 EDT 
What sort of NL numbers would we be talking about here? I'm afraid there is not time for it to be translated if it is anything significant. I'd prefer 2.0.1, but I'm not sure we are doing translations for that either. Can it be added as "experimental" and turned on by preference?
Comment 6 Martin Oberhuber CLA 2007-05-31 12:08:29 EDT 
This would only be 1 or 2 NL Strings, i.e. the Label and Tooltip for

"Commands to be executed when shell starts:"
Comment 7 Martin Oberhuber CLA 2007-05-31 12:08:48 EDT 
BTW, do you translate the remotecdt integration after all?
Comment 8 David Dykstal CLA 2007-05-31 12:40:26 EDT 
(In reply to comment #7)
> BTW, do you translate the remotecdt integration after all?
> 
It doesn't look like we do. Remote CDT is not packaged in the SDK is it?

Is this a change to the Remote CDT integration or is it more general?
Comment 9 Martin Oberhuber CLA 2007-05-31 13:02:56 EDT 
There are two options -- adding a "Commands to Execute" to the REmoteCDT Launch only, and adding a "Commands to Execute" to the Shell Subsystem.

I'd like to do both but I'm also ok with doing one only for now.
Comment 10 David Dykstal CLA 2007-05-31 14:37:52 EDT 
If we do the CDT only version for now it is less risky. Let's do that. We can generalize it to all shells in a future release.
Comment 11 Martin Oberhuber CLA 2007-06-01 06:30:32 EDT 
Ok. Shooting for the remotecdt enhancement through bug #181517.