not work correct search ip-address in <code> #2767

Closed
opened 2025-11-02 04:47:43 -06:00 by GiteaMirror · 6 comments
Owner

Originally created by @vorlon001 on GitHub (Jan 17, 2019).

Description

on https://try.gitea.io not work search code....

for string not work search and indexer
example 1)
...
interface gi1/0
{space}{space}{space}ip address 10.0.0.1 255.255.255.0
!

interface gi1/0
ip address 10.0.0.1 255.255.255.0
!

...
example 2)
...
10.0.0.2
{space}{space}10.0.0.3

...

example 1): not search 10.0.0.1 or gi1/0 in document repo
example 1): not search 10.0.0.3. search only 10.0.0.2 in document repo

Screenshots

Originally created by @vorlon001 on GitHub (Jan 17, 2019). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 176a604 - Git version: - Operating system: Docker https://hub.docker.com/r/gitea/gitea/ - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description on https://try.gitea.io not work search code.... for string not work search and indexer example 1) ... interface gi1/0 {space}{space}{space}ip address 10.0.0.1 255.255.255.0 ! interface gi1/0 ip address 10.0.0.1 255.255.255.0 ! ... example 2) ... 10.0.0.2 {space}{space}10.0.0.3 ... example 1): not search 10.0.0.1 or gi1/0 in document repo example 1): not search 10.0.0.3. search only 10.0.0.2 in document repo ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/confirmedtype/enhancement labels 2025-11-02 04:47:43 -06:00
Author
Owner

@vorlon001 commented on GitHub (Jan 18, 2019):

update

@vorlon001 commented on GitHub (Jan 18, 2019): update
Author
Owner

@stale[bot] commented on GitHub (Mar 22, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 22, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@vorlon001 commented on GitHub (Mar 22, 2019):

problem not fix.
search ip in gitea no work.

@vorlon001 commented on GitHub (Mar 22, 2019): problem not fix. search ip in gitea no work.
Author
Owner

@vorlon001 commented on GitHub (Mar 22, 2019):

this is a bug

@vorlon001 commented on GitHub (Mar 22, 2019): this is a bug
Author
Owner

@vorlon001 commented on GitHub (Mar 22, 2019):

"This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions." - problem not fix.
solutions developed not given.
no reason to close.
search does not work is a mistake.

@vorlon001 commented on GitHub (Mar 22, 2019): "This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions." - problem not fix. solutions developed not given. no reason to close. search does not work is a mistake.
Author
Owner

@vorlon001 commented on GitHub (Apr 11, 2019):

found another solution

@vorlon001 commented on GitHub (Apr 11, 2019): found another solution
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2767