[prev in list] [next in list] [prev in thread] [next in thread]
List: kwrite-devel
Subject: Re: fuzzy-matching in quickopen...
From: Alexander Neundorf <neundorf () kde ! org>
Date: 2022-09-23 21:13:57
Message-ID: 2611304.q0ZmV6gNhb () unknownc4d9870202f1
[Download RAW message or body]
On Freitag, 16. September 2022 18:21:52 CEST Christoph Cullmann (cullmann.io) wrote:
> On 2022-09-16 16:25, Waqar Ahmed wrote:
> > 1. After filtering, why should open files always end up at top? This
> > is not an "already open files quickopen". If the filter matches
> > something else better that will end up at top. There might be cases
> > where an openfile is a better match, perhaps there is a way to improve
> > that without biasing 100% in favour of open files.
> >
> > 2. Match in sequence will take precedence once you have typed 4 or
> > more letters. With 3 or less letters, we can't be sure if that is a
> > sequence or an abbreviation. e.g., ftv will prefer "FilesTreeView"
> > over "abcftv.js"
> >
> > 3. That is correct and working as expected.
> >
> > Quickopen is not meant to filter already open files. For that, you
> > have other plugins that can do the job.
> >
> > If you have a concrete case where X is a better match, discussing that
> > would be better.
>
> The question is, if some people liked the very old behavior of
> preferences for
> open files, if somebody provides a patch to make this configurable via
> the
> context menu (as we have already for the project scope), I think that
> would be
> acceptable.
>
> A config option in the context menu is non-intrusive and will IMHO
> annoy nobody.
I created a merge request, it let's the user select "Fuzzy search" or "Wildcard matching":
https://invent.kde.org/utilities/kate/-/merge_requests/897[1]
Alex
--------
[1] https://invent.kde.org/utilities/kate/-/merge_requests/897
[Attachment #3 (unknown)]
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">On \
Freitag, 16. September 2022 18:21:52 CEST Christoph Cullmann (cullmann.io) wrote:</p> \
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> On \
2022-09-16 16:25, Waqar Ahmed wrote:</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > 1. After \
filtering, why should open files always end up at top? This</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > is not \
an "already open files quickopen". If the filter matches</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > \
something else better that will end up at top. There might be cases</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > where an \
openfile is a better match, perhaps there is a way to improve</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > that \
without biasing 100% in favour of open files.</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > </p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > 2. Match \
in sequence will take precedence once you have typed 4 or</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > more \
letters. With 3 or less letters, we can't be sure if that is a</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > sequence \
or an abbreviation. e.g., ftv will prefer "FilesTreeView"</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > over \
"abcftv.js"</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > </p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > 3. That \
is correct and working as expected.</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > </p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > \
Quickopen is not meant to filter already open files. For that, you</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > have \
other plugins that can do the job.</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > </p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > If you \
have a concrete case where X is a better match, discussing that</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > would be \
better.</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> \
</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> The \
question is, if some people liked the very old behavior of</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> preferences \
for</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> \
open files, if somebody provides a patch to make this configurable via</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> the</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> context menu \
(as we have already for the project scope), I think that</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> would be</p> \
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> \
acceptable.</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> \
</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> A \
config option in the context menu is non-intrusive and will IMHO</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> annoy \
nobody.</p> <br /><p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">I created a merge \
request, it let's the user select "Fuzzy search" or "Wildcard \
matching":</p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><a \
href="https://invent.kde.org/utilities/kate/-/merge_requests/897">https://invent.kde.org/utilities/kate/-/merge_requests/897</a></p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Alex</p>
<br /></body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic