Ouch. When I wrote “contextually undesired outcome” I was trying to be polite and non-confrontational. Things work in Tinderbox the way they do. I don’t see this as a bug but simply something that doesn’t work according to someone’s assumptions. We don’t all have the same intuition as to how things work; this doesn’t make anyone ‘wrong’, but some assumptions will match the app design and others won’t. Thus, if I use an export code in a way it’s not designed to work (despite my expectation) in that context the outcome is unexpected - due to my mis-assumptions.
We had discussion of this what-an-alias-is moons ago (c. v4.x?), which led to current function. An alias allows the same note content to be ‘physically’ exported in more than one place. The suggestion above would break that, and lots of current users’ export and, more significantly, make export less flexible. Thus the status quo.
Within Tinderbox, an alias allows one note to be used/seen in multiple contexts. Clicking on an alias doesn’t move context to the original. Rather it shows the original’s data in the current context. Export reflects this. The suggestion above might suit.
I’ve explained (previous post) how to fix the original question. Do please give it a try it before discounting it, given that your suggestion would break current functionality. In addition, I think @eastgate’s suggestion is a reasonable and pragmatic one.