[GH-ISSUE #173] Multiple tag search

kerem commented

2026-03-01 17:17:21 +03:00

Owner

Originally created by @majkinetor on GitHub (Dec 16, 2021).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/173

Originally assigned to: @VShawn on GitHub.

Is your feature request related to a problem? Please describe.

Currently its not possible to show connections having multiple tags.

Describe the solution you'd like

Lets use #xyz phrase in search to create AND query. For example #personal #server would shows connections tagged both with personal AND server. Negative tags should also be supported - -#personal for example to find connections NOT containing that tag.

Describe alternatives you've considered

There are no alternatives

Additional context
There could be sugar behavior later when this is implmented:

Click on tag replaces current search (we basically have this now)
CTRL click on tag adds it in search
(CTRL) right click on tag adds negative search (i.e. #server -#personal would show connections having server tag but not having personal tag)
Middle click on tag to show popup via which you can rename it or delete it (there could be more options, such as tag color and tag description but those are not that important).

With this there is only one IMO mandatory option that we need to have for efficient tag based workflow - adding or removing tags from group of connections (not just replacing all the tags as we have today).

Originally created by @majkinetor on GitHub (Dec 16, 2021). Original GitHub issue: https://github.com/1Remote/1Remote/issues/173 Originally assigned to: @VShawn on GitHub. **Is your feature request related to a problem? Please describe.** Currently its not possible to show connections having multiple tags. **Describe the solution you'd like** Lets use `#xyz` phrase in search to create AND query. For example `#personal #server` would shows connections tagged both with personal AND server. Negative tags should also be supported - `-#personal` for example to find connections NOT containing that tag. **Describe alternatives you've considered** There are no alternatives **Additional context** There could be sugar behavior later when this is implmented: 0. Click on tag replaces current search (we basically have this now) 1. CTRL click on tag adds it in search 2. (CTRL) right click on tag adds negative search (i.e. `#server -#personal` would show connections having `server` tag but not having `personal` tag) 3. Middle click on tag to show popup via which you can rename it or delete it (there could be more options, such as tag color and tag description but those are not that important). With this there is only one IMO mandatory option that we need to have for efficient tag based workflow - adding or removing tags from group of connections (not just replacing all the tags as we have today).

kerem

2026-03-01 17:17:21 +03:00

closed this issue
added the
general-ux

meta-feature

area-launcher

area-list
labels

kerem commented

2026-03-01 17:17:22 +03:00

Author

Owner

@VShawn commented on GitHub (Dec 16, 2021):

how this work in the launcher?

@VShawn commented on GitHub (Dec 16, 2021): how this work in the launcher?

kerem commented

2026-03-01 17:17:22 +03:00

Author

Owner

@majkinetor commented on GitHub (Jan 15, 2022):

It could work exactly the same. Launcher search or list search, it shouldn't matter.

So:

#database #project1 - find all connections containing both tags
#database -#project1 - find all databases less those of project1
#project1 foo - find all connections containing project1 tag and among them, find those having foo somewhere (name, computer name, even tags with option to search within them enabled)

@majkinetor commented on GitHub (Jan 15, 2022): It could work exactly the same. Launcher search or list search, it shouldn't matter. So: 1. `#database #project1` - find all connections containing both tags 2. `#database -#project1` - find all databases less those of project1 3. `#project1 foo` - find all connections containing project1 tag and among them, find those having `foo` somewhere (name, computer name, even tags with option to search within them enabled)

kerem commented

2026-03-01 17:17:22 +03:00

Author

Owner

@VShawn commented on GitHub (Jan 21, 2022):

done the job.

@VShawn commented on GitHub (Jan 21, 2022): done the job. ![image](https://user-images.githubusercontent.com/10143738/150446459-e159c07d-1624-4d00-919c-44418e51f47a.png) ![image](https://user-images.githubusercontent.com/10143738/150446544-505f04cf-51f3-4862-b490-8517d0bf9340.png)

kerem commented

2026-03-01 17:17:22 +03:00

Author

Owner

@majkinetor commented on GitHub (Jan 21, 2022):

Awesome.

But, wait, why are you showing # in front of every tag on display? Its just marker for search type, it shouldn't propagate to tag name. It just adds noise IMO.

@majkinetor commented on GitHub (Jan 21, 2022): Awesome. But, wait, why are you showing # in front of every tag on display? Its just marker for search type, it shouldn't propagate to tag name. It just adds noise IMO.

kerem commented

2026-03-01 17:17:22 +03:00

Author

Owner

@VShawn commented on GitHub (Jan 23, 2022):

in the launcher, PRM enter the TAG matching logic through the # prefix. In order to keep all TAG display formats, all the tags were added a # prefix.

@VShawn commented on GitHub (Jan 23, 2022): in the launcher, PRM enter the TAG matching logic through the `#` prefix. In order to keep all TAG display formats, all the tags were added a `#` prefix.

kerem commented

2026-03-01 17:17:22 +03:00

Author

Owner

@majkinetor commented on GitHub (Jan 23, 2022):

Well ok, I think it just adds noise here since there are dedicated tag locations in PRM. When there is no dedicated location then it makes sense (e.g Twitter allows tags among narrative so it must have #).

@majkinetor commented on GitHub (Jan 23, 2022): Well ok, I think it just adds noise here since there are dedicated tag locations in PRM. When there is no dedicated location then it makes sense (e.g Twitter allows tags among narrative so it must have #).

kerem commented

2026-03-01 17:17:22 +03:00

Author

Owner

@majkinetor commented on GitHub (Jan 26, 2022):

We don't have multiple tag search in list view:

@majkinetor commented on GitHub (Jan 26, 2022): We don't have multiple tag search in list view: ![image](https://user-images.githubusercontent.com/85767/151159379-76f5680a-0be4-40a0-ac07-57d0f65368d3.png) ![image](https://user-images.githubusercontent.com/85767/151159389-024bb4d0-d894-4c2d-bb1e-9f73a859b83a.png)

kerem commented

2026-03-01 17:17:22 +03:00

Author

Owner

@majkinetor commented on GitHub (Feb 23, 2022):

I will reopen this due to it not working in the list view.

@majkinetor commented on GitHub (Feb 23, 2022): I will reopen this due to it not working in the list view.

kerem commented

2026-03-01 17:17:22 +03:00

Author

Owner

@VShawn commented on GitHub (Feb 26, 2022):

I have done this tick.

Since huge code changed for the ticket, there must some bugs in it.

I will test it for a week before I publish it.

feel free to reopen this ticket if anyone find a bug (please do remember backup your database)

0.6.2.beta2.zip

@VShawn commented on GitHub (Feb 26, 2022): I have done this tick. Since huge code changed for the ticket, there must some bugs in it. I will test it for a week before I publish it. feel free to reopen this ticket if anyone find a bug (please do remember backup your database) [0.6.2.beta2.zip](https://github.com/VShawn/PRemoteM/files/8146292/0.6.2.beta2.zip)

kerem commented

2026-03-01 17:17:22 +03:00

Author

Owner

@majkinetor commented on GitHub (Feb 26, 2022):

Great. I will start using it and report anything I find here.

@majkinetor commented on GitHub (Feb 26, 2022): Great. I will start using it and report anything I find here.

kerem commented

2026-03-01 17:17:22 +03:00

Author

Owner

@majkinetor commented on GitHub (Feb 26, 2022):

FYI, existing database is deleted with this 0.6.2.beta2.zip

@majkinetor commented on GitHub (Feb 26, 2022): FYI, existing database is deleted with this 0.6.2.beta2.zip

kerem commented

2026-03-01 17:17:22 +03:00

Author

Owner

@majkinetor commented on GitHub (Feb 26, 2022):

Sorry, its not deleted, it is set to C:\FastToolsShared\PRemoteM\PRemoteM.db :)

@majkinetor commented on GitHub (Feb 26, 2022): Sorry, its not deleted, it is set to `C:\FastToolsShared\PRemoteM\PRemoteM.db` :)

Rows
Columns

[GH-ISSUE #173] Multiple tag search #2065