reveal-option when opening a document

[alefragnani]

When you call showTextDocument you can pass in which column a TextDocument should be opened. It works perfectly if it being opened for the first time, but if that TextDocument was already opened before, on a different column, you may end up with two views of the same TextDocument.

I didn't find any API to check if the TextDocument is/was already opened, or any API to access the Stacks/Columns, so I could search for that TextDocument and detect the correct column to be used. I only found onDidChangeTextEditorViewColumn event, that appears to be a way to follow the changes.

Thanks for your help.

[jrieken]

There is TextEditor.viewColumn and the list of visibileTextEditors with that you should be able to find what you need. Does that help?

[alefragnani]

Hi @jrieken ,

Thanks for your advice, but unfortunately it does not work, because it only returns the currently visible document in that column, not the list of documents.

I mean, let´s suppose I have two columns with 2 opened documents in each one, like the picture below. In this case the visible document in each column is the first one (LEFT - extension.test.ts / RIGHT - launch.json).

In my scenario, I'm currently focused in the LEFT column. If I need to reopen/navigate to the second one (package.json), which is in the RIGHT column, vscode.window.visibleTextEditors[X] gives me launch.json, with no information about package.json (at least no API), so I can't know that package.json is also stacked in that column. If I had access to the stacks, I could look for that file and open/focus it in the correct column.

The intention is to avoid reopen the same document twice, but instead navigate to the already opened instance.

Thanks for your help

[jrieken]

Yes - we have not exposed the stacks/tab model but an editor in the API land is an editor widget that is bound to a model. I will think about some options for the show-call, like revealIfAlreadyOpenInColumn

[alefragnani]

@jrieken thanks 👍

By the way, I guess you forgot to reopen the issue 😁

[jrieken]

I did ;-)

[jrieken]

closing this as dupe of #15178 which came later but is a little easier to understand