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 dialog in viewer doesn't correctly process input field in hexadecimal mode #2433

Closed
mc-butler opened this issue Dec 1, 2010 · 3 comments
Labels
area: search Search subsystem prio: medium Has the potential to affect progress ver: 4.7.0.10 Reproducible in version 4.7.0.10

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/2433
Reporter yury_t
Mentions gotar@….pl

1) Char \000 isn't regarded correctly. Search for sequence containing 0x00 or 0 or 0h or $0 fails, even if sequence in question is present.

2) Hex modificators are processed differently -- search for 0x11 finds 0x11, but search for either 11h or $11 finds 0x0b.

3) Generally, the hex modificators (h, $, 0x) should be optional, if the hexadecimal mode is already selected.

@mc-butler
Copy link
Author

Changed by gotar (gotar@….pl) on Dec 3, 2010 at 19:18 UTC (comment 1)

  • Cc set to gotar@….pl

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Dec 5, 2010 at 13:55 UTC (comment 2)

  • Component changed from mc-core to mc-search

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Jun 17, 2012 at 7:28 UTC (comment 3)

  • Resolution set to fixed
  • Branch state set to no branch
  • Status changed from new to closed
  • Milestone 4.8 deleted

Fixed in #2795 and #2705.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: search Search subsystem prio: medium Has the potential to affect progress ver: 4.7.0.10 Reproducible in version 4.7.0.10
Development

No branches or pull requests

1 participant