Add standard text search and replace

[guanglinn]

This PR makes Markor support standard text search and replace that are widely adopted by most text editors.

Related Issues:

#2164 - Show search as find in page, not in a popup

#2341 - Highlight in-search results

#2582 - Markor search jumps not to exact finding position

Supported features are as follows:

1. Standard UI for text find & replace

2. Highlight all matches/occurrences

3. Highlight current active match

4. Jump to previous/next match

5. Match case

6. Match whole word

7. Use regular expression

8. Find in selection

9. Replace once

10. Replace all

11. Preserve case when replacing

12. Toggle to line based text search

[guanglinn]

Screenshot

[gsantner]

Thanks for working on this and the screenshot! To me at least it looks quite complicated at first, user will next ask where can I replace only this highlighted one? Where can I replace all? Thats the two most important buttons to be easy recognizable

[guanglinn]

User will next ask where can I replace only this highlighted one?
Where can I replace all?

These two features have already been implemented in this PR, and these two buttons can popup tool tips, users can easily recognize it.

[guanglinn]

I will check it, but it works well on my phone.

SVID_20260206_080628_1.mp4

[gsantner]

Guess it's also due multiline field there:

Is it intentionally multiline? I'm rather unfimilar with search/replace not being normal single text search+replace or regex search+replace

[gsantner]

A crash I could get, but thats not whats currently on the branch, I just tried with

                      android:inputType="text"
                        android:maxLines="1"

FATAL EXCEPTION: main
Process: net.gsantner.markor_test, PID: 10864
java.lang.NullPointerException: Attempt to invoke virtual method 'int android.view.KeyEvent.getKeyCode()' on a null object reference
	at net.gsantner.markor.frontend.textsearch.TextSearchFragment.lambda$onViewCreated$3$net-gsantner-markor-frontend-textsearch-TextSearchFragment(TextSearchFragment.java:138)
	at net.gsantner.markor.frontend.textsearch.TextSearchFragment$$ExternalSyntheticLambda15.onEditorAction(D8$$SyntheticClass:0)
	at android.widget.TextView.onEditorAction(TextView.java:8333)
	at com.android.internal.inputmethod.EditableInputConnection.performEditorAction(EditableInputConnection.java:175)
	at android.view.inputmethod.InputConnectionWrapper.performEditorAction(InputConnectionWrapper.java:253)
	at android.view.inputmethod.RemoteInputConnectionImpl.lambda$performEditorAction$22(RemoteInputConnectionImpl.java:732)
	at android.view.inputmethod.RemoteInputConnectionImpl.$r8$lambda$Jl5UsxtFJ64KyE-rGTA_d_NwhC4(Unknown Source:0)
	at android.view.inputmethod.RemoteInputConnectionImpl$$ExternalSyntheticLambda33.run(D8$$SyntheticClass:0)
	at android.os.Handler.handleCallback(Handler.java:995)
	at android.os.Handler.dispatchMessage(Handler.java:103)
	at android.os.Looper.loopOnce(Looper.java:248)
	at android.os.Looper.loop(Looper.java:338)
	at android.app.ActivityThread.main(ActivityThread.java:9079)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:596)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:932)

[guanglinn]

Hello, @gsantner
I have fixed all known issues. You can test it on your phone.

[gsantner]

Thanks for creating this and working on it for quite some time. I merged it!

[harshad1]

@guanglinn

Why was this disabled?!

Long pressing was extremely useful and I had it set up for many actions.

For example:

• Long press snippet to directly jump to and edit the snippet
• Long press todo in the search field to directly jump to it
• Long press context / project in the filtering dialogs to see them directly

All of these are now not working

[guanglinn]

Hi, @harshad1

I find it easy to trigger incorrect action by long pressing. For example, it may cause incorrect jumps due to unintentionally long pressing an item when you slide the TOC list, so I disabled it at that time.

I will revert it soon.

[harshad1]

We have dopt.state.searchText

That is what should be set here. I am making the change in #2736

[guanglinn]

The reason why I added searchEditText.setText(dopt.searchText) at that time is as follows:
Assuming you input a search text in search dialog, then you switch to replace dialog. dopt.searchText can keep search text from search dialog to replace dialog. This can avoid typing the same search text again.

Here is an example, see search text 'hello':

petal_20260408_233837.mp4

[harshad1]

Yes. Setting state.searchText does that :)