-
Notifications
You must be signed in to change notification settings - Fork 29.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reveal-option when opening a document #13639
Comments
There is |
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 - In my scenario, I'm currently focused in the LEFT column. If I need to reopen/navigate to the second one ( The intention is to avoid reopen the same document twice, but instead navigate to the already opened instance. Thanks for your help |
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 |
@jrieken thanks 👍 By the way, I guess you forgot to reopen the issue 😁 |
I did ;-) |
closing this as dupe of #15178 which came later but is a little easier to understand |
When you call
showTextDocument
you can pass in which column aTextDocument
should be opened. It works perfectly if it being opened for the first time, but if thatTextDocument
was already opened before, on a different column, you may end up with two views of the sameTextDocument
.I didn't find any API to check if the
TextDocument
is/was already opened, or any API to access theStacks/Columns
, so I could search for thatTextDocument
and detect the correct column to be used. I only foundonDidChangeTextEditorViewColumn
event, that appears to be a way to follow the changes.Thanks for your help.
The text was updated successfully, but these errors were encountered: