Bug#342693: yafc: Ctrl-C behaviour is annoying

2005-12-10 Thread Andrew Ferrier
On 2005-12-09 at 12:28 -0500, Decklin Foster wrote:

 Andrew Ferrier writes:
 
  In bash, and most shells, Ctrl-C seems to kill the current line and open
  a new prompt. However, in yafc, pressing Ctrl-C also disconnects from
  the server one is connected to.
 
 My thought is that if something is open (running) in a shell, ctrl-C
 kills it, so I hadn't personally found this behavior surprising.
 
 Would ctrl-U work for you? That's what I always use for erase the
 current line and start over. But I'm not sure if you're looking for
 something more here.

I have to admit I didn't know about that. Having just tested it in bash
and yafc, it does seem to do what I usually use Ctrl-C for, so I should
probably get used to doing that.

 ctrl-D should only be exit on a blank line, methinks, as it is
 equivalent to end-of-file.

Fair enough.

 Yafc uses readline, so is it also possible that you can setup the
 bindings you want by using .inputrc? If so maybe you can close this bug.
 Thanks.

Fair point - didn't know that. Sounds like my 'wrong' behaviour would
be configurable anyway if I wanted, although I'll try and get used to
the right keybindings!

Thanks for your help. I think you can close this bug.

Cheers,
Andrew.

-- 
Andrew Ferrier

web: http://www.new-destiny.co.uk/andrew/
email: [EMAIL PROTECTED]


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



Bug#342693: yafc: Ctrl-C behaviour is annoying

2005-12-09 Thread Andrew Ferrier
Package: yafc
Version: 1.1-4
Severity: normal

In bash, and most shells, Ctrl-C seems to kill the current line and open
a new prompt. However, in yafc, pressing Ctrl-C also disconnects from
the server one is connected to. I'm not sure if this is intentional, but
personally I find this very irritating and I am frequently disconnecting
accidentally. I would have thought Ctrl-D is a more appropriate keymap,
since this normally exits a shell.

However, I appreciate that this may be design, so perhaps this bug is
arguably wishlist.

Thanks for your work on yafc.

Regards,
Andrew Ferrier

-- System Information:
Debian Release: testing/unstable
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages yafc depends on:
ii  libc6 2.3.5-6GNU C Library: Shared libraries an
ii  libncurses5   5.4-9  Shared libraries for terminal hand
ii  libreadline5  5.0-11 GNU readline and history libraries

yafc recommends no packages.

-- no debconf information


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



Bug#342693: yafc: Ctrl-C behaviour is annoying

2005-12-09 Thread Decklin Foster
Andrew Ferrier writes:

 In bash, and most shells, Ctrl-C seems to kill the current line and open
 a new prompt. However, in yafc, pressing Ctrl-C also disconnects from
 the server one is connected to.

My thought is that if something is open (running) in a shell, ctrl-C
kills it, so I hadn't personally found this behavior surprising.

Would ctrl-U work for you? That's what I always use for erase the
current line and start over. But I'm not sure if you're looking for
something more here.

ctrl-D should only be exit on a blank line, methinks, as it is
equivalent to end-of-file.

Yafc uses readline, so is it also possible that you can setup the
bindings you want by using .inputrc? If so maybe you can close this bug.
Thanks.

-- 
things change.
[EMAIL PROTECTED]


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