completion buffer not closed when done

Bug #1065468 reported by Andreas Roehler
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-mode.el
Fix Released
Medium
Andreas Roehler

Bug Description

Am 08.10.2012 17:54, schrieb Yaroslav Halchenko:> Thanks Andreas -- tried it -- I guess it is better now...
>
> so, now if I have pre-split window with an original source code in one
> (#1), and the interactive ipython in another (#2), completing in ipython
> shell uses the #1. Then whenever I am done completing I have following
> options to "close" it to get back to the code view: switch to it and
> press 'q' or actually complete completion by clicking mouse on a desired
> choice -- then completion buffer gets removed going back to #1 with the
> source code. And then if I just triple-Esc -- it closes ALL other
> buffers and I end up with the mighty shell. And I guess that is how
> other shells completions behave (tested with a regular shell). I just
> wondered what is your usage pattern? do you just keep completions
> buffer pre-opened all the time? or use mouse/switch+q to close it?
> Ideally, I wished there was a way to close completions buffer without
> leaving the prompt buffer and without hurting any previously opened
> (e.g. code view in #1) as if I pressed 'q' in it... e.g. if Triple-Esc
> (keyboard-escape-quit) could be overriden to invoke that action in the
> "*Python Completions". Or may be there is already some shortcut which
> would accomplish this?
>

Changed in python-mode:
assignee: nobody → Andreas Roehler (a-roehler)
milestone: none → 6.1.1
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Andreas Roehler (a-roehler) wrote :

C-x 1

Nonetheless Emacs should be smart enough to make completions vanish when done or abandoned.

Changed in python-mode:
status: In Progress → Triaged
milestone: 6.1.1 → 6.2
Changed in python-mode:
status: Triaged → Fix Committed
Changed in python-mode:
status: Fix Committed → 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.