On Fri, Mar 31, 2006 at 07:24:56AM +0200, Martin Michlmayr wrote:
> * Anthony DeRobertis <[EMAIL PROTECTED]> [2006-03-30 15:38]:
> > Nah, I expect C-c to "kill this action". Usually, that means "quit and
> > return to the shell." With Jack, I expected "this action" to be "rip
> > the cd", so I expected to get put back to the shell.
> >
> > (Examples of a program where I don't expect C-c to return me to the
> > shell: bc (kill the current calculation); irb (same, basically); mutt;
> > etc)
> >
> > However, a request to change the C-c mapping in Jack is a different
> > bug, so let's...
>
> I disagree and think that jack belongs in the class with eg. mutt.
> Anyway, can you please read #352755 and comment. Not that this bug
> contains much information but at least it shows that pressing C-c
> leading to the current ripper/encoding being killed rather than the
> whole program has always been the default behaviour (just that I fixed
> it so it actually works).
I can think of several reasons you'd want to quickly kill jack
completely:
- accidentally inserted wrong disc
- realized you picked the wrong entry in freecddb
- drive starts making weird sounds
- realize you don't have enough disk space, or need the space for
something else
- realize the rip is broken in some way (encoder not working,
options wrong, etc.)
I can not think of any reason why I'd want to kill the rip of the
current track and immediately proceed to the next track. (And why the
current ripper, not the current encoder[s]?)
That's why Control-C should kill jack, not just the current ripper.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
