linuxmint / linuxmint/nemo

Search with special character "?" breaks search logic

Open
#3,462 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
1.6k
Forks
368
Avg merge
4d 4h
Merged PRs (30d)
2

Description

Distribution

Tested in Mint 22 Cinnamon

Package version

6.2.8

Frequency

Always

Bug description

I hope I'm not completely off base here. Nemo seems to treat the question mark as a special character when it's used in a file name search. I believe that it is supposed to match any single character, though I haven't found any documentation of that behavior. But there are many times where it does other odd things as well.

Assume that I have files named A, B, C, AB, BA, BCA, AAA, AAAA, D, AA, BB, and CC.

  • Searching for "A B" only returns AB, BA, and BCA, good
  • Searching for "A?" should return AA, AB, AAA, and AAAA, but only returns AA and AB. Apparently "A?" is treated as a 2 character search of A followed by any other character. As a RegEx that'd be ^A.$
  • Searching for "A B?" should match A and B followed by any single character. It should only match BCA and BA, but it matches A, AAA, AAAA, AB, BA, BCA, AA, and BB.
  • Searching for "A B ?" (with a space) matches everything except CC.
Steps to reproduce

Perform a search with "?" as one of the terms or as part of one of the terms

Expected behavior

Make "?" act as expected or clarify the expected behavior.

Thank you!

Additional information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in Nemo using the listed filenames and search terms, starting with the search entry point. Trace how question marks and space-separated terms are interpreted, then verify behavior against the examples in the report; done means the expected matches are returned or the behavior is clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop-dev, search
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.