nikita-rudenko / back-n-forth Goto Github PK

I work at a company that recently switched to using VS Code remoting. Unfortunately the extensions we can install on the remote host are limited. This means we can't install this extension by default because it tries to install to the remote host.

For now I've overridden the extension type but it'd be awesome if the package.json could be updated to add "extensionKind": ["ui"] since I don't think it needs access to files on the remote host.

This is more of a question than an issue really but:

Wouldn't it be simpler to just bind the buttons directly to workbench.action.navigateBack and workbench.action.navigateForward rather than creating new commands that just call the original ones?

I have a logitech mouse with back and forward buttons on the side, can I make it work with this plugin?

On the Mac, the back and forward icons on the Touch Bar are carets, not arrows. It would be less jarring if your toolbar icons matched. Thanks!

Configuring the editor so that the same file is opened in both panes of the editor in horizontal split view mode (so the editor shows two panes, and both display a different section of the same file). When doing a "ctrl+click" on a function in the top pane of the editor, it then opens the file defining this function in the top pane and shows that function one navigated to. Then when using the "back" arrow of this extension to go back to the initial place, instead of moving back to the initial place in the file in the top pane, it moves back to it in the file in the bottom pane, which is not the expected behavior.
Note: the issue also occurs when trying it from the bottom pane or in any other split view mode.

See video:

.

Back-n-forth VSCode extension looks really interesting.

But, some of us not using VSCode directly. Instead we use https://vscodium.com/ or https://github.com/eclipse-theia/theia.
These uses a different marketplace, open-vsx.org.
Can you please publish your extension on open-vsx.org also.

Here is a guide to publish into open-vsx marketplace.
https://github.com/eclipse/openvsx/wiki/Publishing-Extensions

atm going back/forth will open closed files, so can we exclude the closed files from the navigation loop ?

Hi! I'm from the VS Code team, and we'd like to ensure Back & Forth can run in the different extension host setups VS Code currently supports. I've found that the current definition of extensionKind for your extension is too restrictive.

The extension has the extensionKind set to ["ui"]: https://github.com/nikita-rudenko/back-n-forth/blob/master/package.json#L24. This defines that the extension can only run in the VS Code desktop extension host.

However, this extension can also run on the workspace extension host (which is used for remote scenarios) since it doesn't have any dependencies on the desktop extension host. It'd also be great to enable it for Codespaces web.

Thus, to ensure your extension can run properly across setups, we'd recommend to change the extensionKind to "extensionKind": ["ui", "workspace"]. More information about extensionKind can be found here.

Please let me know if you have questions - I'm happy to help clarify anything. Thank you!

Title says it all! Wondering if there's a way to move it so the back-n-forth buttons are to the left of the open tabs :)

Thank you for being part of the Open VSX community by adding your extensions to the Open VSX Registry. Please note that the service was recently transferred to the Eclipse Foundation and urgent action on your part is needed so we can continue to list your extensions. To ensure uninterrupted service, please sign the Eclipse Publisher Agreement on or before January 8, 2021. If not signed by that date, your extensions will be delisted and will no longer appear on the site nor be available via the API. If you sign at a later date, your extensions will then be re-activated. The signing process is explained in the Wiki (steps 1 and 2).

Please also note that all extensions MUST have a license in order to be listed.

More details are in these recent blog posts:
https://blogs.eclipse.org/post/brian-king/open-vsx-registry-under-new-management
https://blogs.eclipse.org/post/brian-king/new-era-open-vsx-registry

Today, there’s growing momentum around open source tools and technologies that support Visual Studio (VS) Code extensions. Leading global organizations are adopting these tools and technologies. This momentum has spurred demand for a marketplace without restrictions and limitations. Thanks for joining us on this journey as we continue to build the Open VSX community. We look forward to continued innovation from you in 2021!

Enhancement suggestion: Might it be possible to add a Last Edit Location button as well? The icon should be a left arrow with an asterisk (as in Eclipse).