Re: [External] RE: using macros in Action, Execute Command

[Paul Sichta via Tech-talk <tech-talk at aps.anl.gov>]

Hello Tong,

You are correct and Kay also indicated this was fixed February 2, 2023.  I was using an old tagged version 4.6.6.

The current master works as-expected!

Thanks, all.

-ps

On Mon, Mar 20, 2023 at 10:12 AM Zhang, Tong <ZhangT at frib.msu.edu> wrote:

I also came across the similar issue but I was trying to access the widget property, e.g. $(name) through an argument of a command. And I believe this PR resolved it https://github.com/ControlSystemStudio/phoebus/pull/2532

 

If it does not support env, either report a new issue, or try to use a dummy property of a widget to host the env, and use it in a command, for multiple envs, you can also parse the string in your command into multiple variables.

 

Thanks,

Tong

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Paul Sichta via Tech-talk
Sent: Friday, March 17, 2023 17:19
To: tech-talk at aps.anl.gov
Subject: using macros in Action, Execute Command

 

[EXTERNAL] This email originated from outside of FRIB

Using phoebus, I used an action button and added an Execute Command.  My macro will not work when used in the Command line.  The macro will work in action type WritePV,  or as a PVname for an object on the display.

 

Example: I add to my environment before starting phoebus,  export myLS=ls

In the action command line I use       $(myLS)  

 

When I run the action I get an error

Cannot run program "$myLS" (in directory  blah...); error=2, No such file or directory

 

If I simply use    ls    in the command it works fine.

The help, about,  inspect environmental variables it shows:  myLS = ls

 

Is there a way to use macros from the user's environment on these Execute Commands?

In particular, I want to use a macro to be a directory path on my system

 

Regards,

-ps