bzr shell becomes very slow after qdiff

Bug #478733 reported by Aliaksei Vasileuski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
BzrTools
Fix Released
Undecided
Unassigned
QBzr
Invalid
Undecided
Unassigned

Bug Description

I use bazaar as "bzr shell" on MS Windows. This saves me 4 chars ("bzr "), nice command completion.
After executing 'qdiff some/file.cpp', the typing speed in the bzr shell becomes very slow (0.5 char/sec).

summary: - bzr shell becomes very slow (0.5 char/sec) after qdiff
+ bzr shell becomes very slow after qdiff
Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 478733] [NEW] bzr shell becomes very slow after qdiff

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nishi wrote:
> Public bug reported:
>
> I use bazaar as "bzr shell" on MS Windows. This saves me 4 chars ("bzr "), nice command completion.
> After executing 'qdiff some/file.cpp', the typing speed in the bzr shell becomes very slow (0.5 char/sec).
>
> ** Affects: qbzr
> Importance: Undecided
> Status: New
>
> ** Summary changed:
>
> - bzr shell becomes very slow (0.5 char/sec) after qdiff
> + bzr shell becomes very slow after qdiff
>

I believe that qt application starts its own command line hooks. (You'll
notice if you try to drop down into pdb from a running app.)

I don't really know any way to work around it. But can you confirm that
it happens after running *any* 'q' action? (qlog, qbrowse, qdiff, etc)

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkr7NCsACgkQJdeBCYSNAANrSACfdzVSLl1g+IxWYCjm6DnVz21l
VckAn3gq8S9wtGb7SSEdw2tXchNoO/+B
=p2jH
-----END PGP SIGNATURE-----

Revision history for this message
Aliaksei Vasileuski (sagara1337) wrote :

Yes, I confirm it, bzr shell becomes slow after any q* action.

On Thu, Nov 12, 2009 at 00:01, John A Meinel <email address hidden> wrote:

> But can you confirm that it happens after running *any* 'q' action? (qlog,
> qbrowse, qdiff, etc)
>

Revision history for this message
Aliaksei Vasileuski (sagara1337) wrote :

As a walkaround, bzr can create another console window when executing any q* actions, and run the action from it.

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 478733] Re: bzr shell becomes very slow after qdiff

Nishi пишет:
> As a walkaround, bzr can create another console window when executing
> any q* actions, and run the action from it.

It never happens, IMO.
You just should not mix console commands and GUI commands.
If you like, you can file another bug against QBzr project and asking for providing special GUI shell.

Revision history for this message
Alexander Belchenko (bialix) wrote :

Actually this bug cannot be fixed in QBzr. And shell command coming from bzrtools.

Changed in qbzr:
status: New → Invalid
Revision history for this message
Aliaksei Vasileuski (sagara1337) wrote :

Currently I run two consoles, one in "bzr shell", another one is usual console to run "bzr qdiff" when necessary. But it make the "too many open windows" problem even worse for me.

Revision history for this message
Aaron Bentley (abentley) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexander Belchenko wrote:
> Actually this bug cannot be fixed in QBzr. And shell command coming from
> bzrtools.

I believe it could be fixed in qbzr. Qbzr is starting up an event loop
that is capturing keystrokes, and should be able to shut that event loop
down, such that it stops capturing keystrokes.

However, I agree that it is possible to fix it in bzrtools, and I have
done that.

 status fix-released

Aaron

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkr704UACgkQ0F+nu1YWqI2ctgCeJ1EjNICE/kJ33hX/k4SOHSSL
SP4An2PvJplxDeHx9/0apRoARHk/1YGn
=jIoU
-----END PGP SIGNATURE-----

Aaron Bentley (abentley)
Changed in bzrtools:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.