Closed ericmandel closed 4 years ago
I think the tricky thing here is how general do you want to be: e.g.
ps -A
between different UNIX-like systemsAlthough we can put together something that improves upon the current situation without addressing either of these.
This check is probably overkill ... I would skip Windows happily, leave -A as is (it works on Linux and Mac) and just filter out instances related to pyds9. These instances almost certainly are the result of the newer install code beyond the primitive stuff I wrote a decade ago.
Oh. That's why I'm not seeing it. I'm using an out-of-tree version of xpans
(so it's not triggering the problem).
@ericmandel - if you have the Aqua version of DS9 running, what does ps -A
report for that line? Is it ...SAOImageDS9.app
(maybe with a space) or something different?
It does the right thing:
eric% ps -A | egrep ds9 | egrep -v egrep
49510 ?? 0:01.37 /Applications/SAOImageDS9.app/Contents/MacOS/ds9
Closed by #97
@DougBurke Whenever I start up pyds9, I can a long message beginning:
regardless of whether DS9 is running or not. This is because there is a too-general check on whether DS9 is running. In the ds9_xpans routine around line 61, we see:
Using ps is fine but the simple check for 'ds9' in plist is not. On my Mac, as soon as I start up xpans, I see this:
and the fact that xpans is installed in the pyds9 directory guarantees that 'ds9' will be in pslist.
I think we need to filter out lines from the ps output that contain "xpans" ... which I don't know how to do offhand. Can you please help?