Bug#458537: yakuake: Default close terminal shortcut conflicts with vim's redo change

2008-01-01 Thread Vincent Pelletier
Package: yakuake
Version: 2.8-1
Severity: normal

Subject says it all.
I would suggest to disable close terminal shortcut by default.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.23-1-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages yakuake depends on:
ii  kdelibs4c2a 4:3.5.8.dfsg.1-4 core libraries and binaries for al
ii  konsole 4:3.5.8.dfsg.1-2 X terminal emulator for KDE
ii  libc6   2.7-5GNU C Library: Shared libraries
ii  libgcc1 1:4.2.2-4GCC support library
ii  libqt3-mt   3:3.3.7-9Qt GUI Library (Threaded runtime v
ii  libstdc++6  4.2.2-4  The GNU Standard C++ Library v3

yakuake recommends no packages.

-- no debconf information




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#458537: yakuake: Default close terminal shortcut conflicts with vim's redo change

2008-01-01 Thread Ana Guerrero
Hi Vicent,

On Tue, Jan 01, 2008 at 03:19:16PM +0100, Vincent Pelletier wrote:
 Package: yakuake
 Version: 2.8-1
 Severity: normal
 
 Subject says it all.
 I would suggest to disable close terminal shortcut by default.


vim's redo change shortcut is control-R and yakuake's close terminal
shortcut is control-shift-R, so check your settings :)


Ana



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#458537: yakuake: Default close terminal shortcut conflicts with vim's redo change

2008-01-01 Thread Vincent Pelletier
On Jan 1, 2008 6:56 PM, Ana Guerrero [EMAIL PROTECTED] wrote:
 vim's redo change shortcut is control-R and yakuake's close terminal
 shortcut is control-shift-R, so check your settings :)

My mistake then... Although it does work with shift - if not caught by
yakuake, that is.

Anyway, I don't think it's so good to have an uncatchable key command
which causes terminal closure, no matter what's runing.

Let's take OSX console as an example: option+q closes any application
in OSX, and terminal checks runing processes in its shell: if anything
beside login and the shell is runing it displays a confirmation
window, listing runing processes.

Maybe this should be implemented (I bet this bug should then be moved
to a kde/konsole wishlist) and/or this shortcut should be disabled by
default. Closing an opened terminal when nothing else is runing is
anyway reachable by something like ^d or the close terminal button.

Vincent Pelletier



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]