[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: find
From:       Christoph Cullmann <cullmann () babylon2k ! de>
Date:       2007-10-03 11:39:54
Message-ID: 200710031339.54773.cullmann () babylon2k ! de
[Download RAW message or body]

Am Mittwoch, 3. Oktober 2007 07:37:20 schrieb Sebastian Pipping:
> ------------------------------------------------------
> Good and bad news in this mail. Please don't beat me
> for it but I thought about it some more, had a look
> at Firefox again and changed my view on this a bit:
>
> Pressing <return> should _not_ be the closer.
> Firefox' search bar is jumping to the next match on
> <return> as well. We were cloning Firefox all the
> time - for good reason in my eyes. In Firefox
> <shift> + <return> jumps to the previous match which -
> good news here - kate supports now as well.
>
> So what I did about that close thing is to map it
> on <ctrl> + <return>. That way you have a way of closing
> it right after the search. In case you like
> <alt> + <return> better, that would be an alternative.
> Please check out the current state live and see if you
> can get used to that.
>
>
> To sum it up again in a modifier/action map:
>
>    <ctrl> <shift> | action
>    ---------------|----------------------
>                   | search next
>              X    | search prev
>      X            | search next, hide bar
>      X       X    | search prev, hide bar
>
>
> Please let me know what you think of the current solution.
I think CTRL-return for closing is perfect, as other apps have similar stuff 
around, like kmail with sending on ctrl-return :)

cu
Christoph

-- 
Christoph Cullmann
KDE Developer, Kate Maintainer
http://babylon2k.de, cullmann@kde.org
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel

[prev in list] [next in list] [prev in thread] [next in thread]