After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 708792 - Jumping from terminal to source and back
Jumping from terminal to source and back
Status: RESOLVED OBSOLETE
Product: anjuta
Classification: Applications
Component: core application
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: Naba Kumar
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2013-09-25 23:46 UTC by Guus
Modified: 2020-11-06 20:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Guus 2013-09-25 23:46:17 UTC
From my email to the anjuta user list. I am using Fedora 19 with current software.

Le 24/09/2013 11:01, A.J. Bonnema a écrit :
> I just started using anjuta: a very good development environment indeed.

Thank you.


> I am writing because while learning c++ I do a lot of compile-run
> cycles. Each time I run some code, the terminal starts, but my cursor
> stays in the editor. In order to end the program that is running or to
> do input, I have to use the mouse to get to the terminal, press enter,
> and then use the mouse to get back. Then I can resume coding.
>
> Is there a shortcut (I could not find one) that takes the cursor from
> the code window to the terminal and back?

No, I don't think so. Could you write a bug report here
https://bugzilla.gnome.org/buglist.cgi?query=product%3Aanjuta+
It will allow us to remember this request.


Regards,

Sébastien
Comment 1 André Klapper 2020-11-06 20:21:52 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/anjuta/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.