Currently, every time an oracle command is launched it will look at the current cursor position. This means that if you've drilled down into the code using links a mode has provided, switching to a new mode will launch oracle from the current position.
This may be the workflow desired.
It might be worth investigating a workflow where go-oracle tracks where it was when it was opened and runs all oracle commands with the stored position. If this were the case, we'd then need a way to explicitly tell the oracle to run a command from the current position, e.g. after drilling down.
This may be an unexpected and undesirable workflow.
Currently, every time an oracle command is launched it will look at the current cursor position. This means that if you've drilled down into the code using links a mode has provided, switching to a new mode will launch oracle from the current position.
This may be the workflow desired.
It might be worth investigating a workflow where go-oracle tracks where it was when it was opened and runs all oracle commands with the stored position. If this were the case, we'd then need a way to explicitly tell the oracle to run a command from the current position, e.g. after drilling down.
This may be an unexpected and undesirable workflow.