xpachanges(7)

✨ xpachanges(7) ✨

okay bestie, this is the SAORD Documentation glow-up page for xpachanges — it's literally the tea on what changed for users moving from XPA 1.0 to XPA 2.0 💖

🌸 NAME 🌸

XPAChanges — the changes that hit users coming from XPA 1.0 and 2.0 🦋

🎀 SYNOPSIS 🎀

This doc spills the whole story of the changes that affect users who migrate from XPA 1.0 to XPA 2.0. periodt. 💅

💜 DESCRIPTION 💜

So here's the situation: there have been a few changes that affect users who upgrade XPA from version 1.0 to version 2.0. And we're detailing all of them below, no gatekeeping here 🫶

• XPA commands no longer have a resolver routine — and lowkey, this one is open to negotiations, but the team decided the idea was dumb. 😭 For the SAOtng program, this means you must explicitly specify the access point, i.e.:

cat foo.fits | xpaset SAOtng fits

instead of:

cat foo.fits | xpaset SAOtng

• By default, xpaset, xpaget, etc. now wait for the server callback to complete — i.e., the old -W is implied (and the switch is ignored, bestie, it's giving obsolete 👑). This is the whole reason we get support for better error handling. ✨ If you want xpaset, etc. to return before the callback is complete, use the -n switch:

echo "file foo.fits" | xpaset -n SAOtng

• The old -w switch in xpaset and xpaget is no longer necessary (and is ignored 🙈), since you can have more than one process communicating with an xpa access point at one time. the way that's just no longer a problem for us 💅
• The new -p switch on xpaset means you need not read from stdout:

xpaset -p SAOtng colormap I8

will send the paramlist to the SAOtng callback without reading from stdin. iconic behavior, honestly 🌈

🦋 SEE ALSO 🦋

See xpa(n) for a list of XPA help pages 💖

k bye bestie, that's the whole page — version 2.1.15, dated July 23, 2013, and yes it ate ✨💅👑