Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Search Function Skips the First Matching Word After a Codebox #2631

Open
Qehremanov opened this issue Jan 11, 2025 · 3 comments
Open

Search Function Skips the First Matching Word After a Codebox #2631

Qehremanov opened this issue Jan 11, 2025 · 3 comments

Comments

@Qehremanov
Copy link

Qehremanov commented Jan 11, 2025

Version, Operating system
CherryTree version: 1.2.0
OS: Ubuntu 20.04.1
Desktop: Gnome

Describe the bug
When searching within a node, the application fails to find the first matching word that appears immediately after a codebox.
The bug seems specific to the first word after a codebox. Words in other parts of the note, both in rich text and codeboxes, are correctly found during a search.

To Reproduce
Steps to reproduce the behavior:

  1. Create a node containing both rich text and a codebox.
  2. Add a word or phrase (e.g., "example") within the rich text before the codebox.
  3. dd a codebox and include the same word or phrase (e.g., "example") inside it.
  4. Add the same word or phrase (e.g., "example") immediately after the codebox in the rich text.
  5. Use the search function to search for the word or phrase (e.g., "example").
  6. The search finds all instances of the word or phrase except for the first one located immediately after the codebox.

Screenshots
1
2
3

@xidiot
Copy link

xidiot commented Jan 17, 2025

I can confirm that this issue happens also on macOS v14.7.2 (23H311) and CherryTree v1.2.0 (73).

@giuspen
Copy link
Owner

giuspen commented Jan 26, 2025

I see it, thanks for reporting, I'll try to fix and get back

@giuspen
Copy link
Owner

giuspen commented Jan 29, 2025

This has been now fixed. The next release v1.3.0 should be in about a week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants