gonsole weeks: multiple console sessions

Home  >>  Eclipse  >>  gonsole weeks: multiple console sessions

gonsole weeks: multiple console sessions

On July 2, 2014, Posted by , In Eclipse,Gonsole, By ,,, , With 4 Comments

While Eclipse ships with a comprehensive Git tool, it seems that for certain tasks many developers switch to the command line. This gave Frank and me the idea, to start an open source project to provide a git console integration for the IDE. What happened so far during the gonsole weeks can be read in git init gonsole, eclipse egit integration, content assist for git commands and oops – it’s a framework.

As we were busy with other things the recent days there are not that many new features to talk about. Nevertheless, we managed to teach gonsole how to cope with multiple console sessions and refresh your workspace when necessary. Furthermore, we fixed some bugs – most notably quoted text (like in commit -m “foo bar”) is now recognized correctly.

Multiple Sessions

A console session can be created with the ‘Open Git Console’ action as before.

open-console-dropdown

However, you can now create multiple sessions through this action and switch between them with the ‘Display Selected Console’ drop-down.

To distinguish different sessions, the console view is labeled with the name of the repository that is currently in use. This allows you to operate on multiple repositories and keep their work log separate.

Workspace Refresh

An annoyance when working with an external console is that the workspace may become stale through commands which change the work directory. Though ‘Refresh on access’ solves many of the synchronization problems, newly created or deleted files aren’t recognized by this feature.

This is where gonsole helps out and refreshes all affected workspace resources after you e.g. checked out a branch, reset to a certain commit or merged commits.

See also  EclipseCon Europe — RAP Talk On-Line

Even though there is a ‘Refresh using native hooks or polling’ option we thought it is worth to actively refresh changed resources because the hook isn’t enabled by default and comes with a (admittedly short) delay.

If you want to try the new features by yourself, you can install the tool from this update site: https://rherrmann.github.io/gonsole/repository/

And we will go back to work on the long-promised content assist enhancements – this time for real ;-)

Rüdiger Herrmann
Follow me
Latest posts by Rüdiger Herrmann (see all)

4 Comments so far:

  1. Jake Toronto says:

    Hi, how does one tell gonsole which repository is active?

  2. Jake Toronto says:

    Thanks, Frank! Nicely done — this is the perfect complement to EGit.

    Have you considered using the currently active project to determine which repository to open with a new gonsole window? This is what I was originally expecting when I began using gonsole. It would be a nice convenience for the user.

    Thanks again!

    • Rüdiger Herrmann says:

      Jake, this is a nice enhancement, would you mind to open an issue?
      https://github.com/rherrmann/gonsole/issues

      In the meanwhile, you can use Open Console from the Team menu to open a console for the repository to which the selected resource belongs. Alternatively, there is an Open Git Console command that can be reached via Ctrl+3 which also uses the current selection to determine the initially used repository