Re: [ptp-dev] Uploading Scripts through PTP

["Alameda, Jay" <alameda@xxxxxxxxxxxx>]

Steve,

You may want to take a look at how Jeff implemented the module capability, a script gets uploaded to /tmp and then is prepended to anything that we do (build, run, etc) -

Jay


Participate in XSEDE14!
Full Call for Participation at www.xsede.org/xsede14
July 13-18, 2014
Atlanta, GA


-----Original Message-----
From: ptp-dev-bounces@xxxxxxxxxxx [mailto:ptp-dev-bounces@xxxxxxxxxxx] On Behalf Of Steven R. Brandt
Sent: Tuesday, April 29, 2014 9:25 AM
To: ptp-dev@xxxxxxxxxxx
Subject: Re: [ptp-dev] Uploading Scripts through PTP

On 04/28/2014 09:56 AM, Steven R. Brandt wrote:
> I'm working on the GUI enhancements for the terminal in PTP. One of 
> the things I want to provide is a graphical interface to the shell 
> history. For bash, I can easily get modifications to the history file 
> by using "tail -f" or "tailf". For tcsh/csh, however, I've come to 
> realize the problem is not so simple and no standard linux command 
> does the job. I've written a perl script which solves the problem, so 
> the obvious solution would be to upload it to the user's account and 
> execute it.
>
> My question: What's the standard way to go about doing this? (i.e. 
> classes to use for uploading, what to name the file, etc.)
What I'm  doing until I hear otherwise, is stripping all whitespace from the perl code, and executing the script with -e. It's somewhat cleaner in that it doesn't install anything. It's somewhat uglier, in that a perl script is stored in a moderately big Java string.

Cheers,
Steve
>
> Cheers,
> Steve
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev

_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev