In default configuration, bookmarks show up without prefix ... can i make the prefix-only?

[gestaltungssache]

Sorry if i'm using this issues section to ask a question, but i can't find a solution myself, nor a forum to ask questions. Please direct me the right way if such a thing exists ... I'm new to keypirinha, and while i'm excited about all the possibilities, i'm having difficulties to configure it the way i want it.

Currently i want to configure the bookmarks package. When typing in the main window, all the bookmarks (from firefox) that match show up by default. I'd like them to show up only if i use the bookmarks: prefix. Easy example: i have a bookmarks to nytimes.com in firefox. when i type "ny", this shows up immediately in the results ... i'd like it to show up only if i type "bookmarks: ny"

Thought was to set the bookmarks.ini this way: [main] [provider/Firefox] Default: no enable = yes

but after saving the ini, re-initialize the configuration and refreishing the catalog, the bookmarks still show up while typing. So either i'm not understanding what "Default: no" means, or i'm doing it wrong.

Thanks for your help!

[ueffel]

Sadly you can't set up the package so only shows the bookmarks if you type the prefix. They're just all in the catalog and can show up when the search terms match. The Default: no shouldn't be in there. Its just a comment in the default INI file. The only thing you can set up per provider is, if the bookmarks from the particular browser are added to the catalog, with the enable setting. (or possibly a path to the bookmark file of the browser)

[gestaltungssache]

thanks for input. so i'll have to get used to this somehow ... either disabling bookmarks (there are thousands, polluting the results and pushing down more relevant results from other modules) or just adjust to it and train the catalog right.

got it about "Default: no" ... long time no see for ini files :-) I've also found the chat now ... i guess it's better to ask general questions there.

Maybe it could be a future feature to make it configurable globally which packages need a prefix and which don't?

[ueffel]

As a feature I would image a behaviour similar to the Taskswitcher Package, where you can configure if you want the catalog items always be there or if you want them only to show up after you entered the prefix. Let's see what @polyvertex has to say :)

[polyvertex]

@gestaltungssache are the items you wish to find in the crowded list, meant to be executed frequently? Perhaps some specific examples would help to narrow things down a bit and find the appropriate solution?

[gestaltungssache]

well maybe it's best to explain what its currently "doing" and what i'd "like it to do":

i personally use keypirinha

• primarily for launching programs (from start menu items), opening folders or files directly (everything) and calculations (calc).
• secondarily, i'm using the filezilla package, translate package, and i try to train myself to do web searches with it too. finding the (thousands) bookmarks from my firefox setup would be nice to have too. those all are less important aspects to me but nice to have.

now if i just call the program and start typing, let's say "indesign", i'd like see as a result the program itself, and maybe as further hits, show folders or files with that name as well. I'd rather not see anything else than programs, folders and files. but currently keyperinha also presents me about 300 firefox bookmarks with that keyword as well, and (as long as it is still completely untrained) it's even presenting them to me with higher priority than the program or folder i'm looking for. So my results are flooded with matches from the bookmarks package, hiding away the things i was actually looking for. Of course sometimes i'd like to search for "indesign" in my bookmarks, so disabling the package is a bit harsh ...

My thought was to somewhat configure the packages into two categories:

• those who may show results when just typing the keyword itself ("indesign" --> only programs, folders and files with that name)
• and the others who should only show their results when having prefixed the keyword with something ("bookmarks: indesign" --> specifically only show firefox bookmarks with that keyword).

A variation of this would be to give them some priority instead: when typing a keyword, first results should be programs, then files and folders, then bookmarks, and then maybe websearch suggestions, ...

Now this of course would have to be configurable to ones own preferences - everyone has other priorities, so everyone would need other "primary" and "prefix-only" packages. I'm also well aware that when training the program, the "problem" gets smaller rather fast, as things preferred in first search show up in first places in the next search. Still i was irritated when i switched over from launchy, trying to find my programs and folders, but instead was presented hundrets of bookmarks and no way to get them out of the way fast ...

[ningo247]

Maybe a simple solution would be to allow another setting for custom flags to trigger specific results from specific package e.g.: when searching "indesign -bookmarks" would mask all the catalog results which are not coming from the bookmark package. I looked at the api a little bit and saw that all package items are merged into a single catalog..does it know which package its from ?

[polyvertex]

@gestaltungssache you definitely sound like you want to get more acquainted with KP's Associate a Keyword to an Item feature. This is the one you need for items you will execute more than once. Yes it requires you to "train" KP but it's just a one or two steps process and you actually do not need to do it consciously (that's pretty much the beauty of it). That is the short-term answer.

Now I appreciate there are some non-frequent cases where one need to dig for an item that hasn't been executed yet and is not meant to be used frequently. This kind of cases leads us to search syntax indeed.

Having a search syntax for the initial search step only has been in my to-do list for a while and has actually replaced the weight/priority system like the one in FARR you described, which I find unnatural to use and cumbersome to configure.

Search syntax might be implemented in KP in the future, but be warned it's a long shot.

[polyvertex]

Please also note that you may experience abnormal difficulties to find some items due to a recent regression in KP's search algorithm. See #215 for more info. Sorry for that.

[polyvertex]

v2.15.3 should at least partly address this. I'm closing this but feel free to comment if the issue persists.

PS: the aforementioned search syntax feature is not gone to oblivion and kept in KP's to-do list!

[rasivasu]

v2.15.3 should at least partly address this. I'm closing this but feel free to comment if the issue persists.

PS: the aforementioned search syntax feature is not gone to oblivion and kept in KP's to-do list!

Is there a way to up-vote this feature?