Closed Bug 16598 Opened 25 years ago Closed 25 years ago

Lame 29-character string search limit

Categories

(Webtools Graveyard :: MXR, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: shaver, Assigned: endico)

References

()

Details

We have long variable names, and I need to search for them. Waaah.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
lxr uses glimpse and glimpse uses agrep. agrep limits the length of patterns. Work around this by finding the 29 most unique characters in your string and search for that. This is likely the end of the string. Or try using a regex. The real problem here is that lxr doesn't index idl files and macros very well. The new version should fix that. A bug is already filed.
Well, the glimpse/LXR documentation, to which we link from the LXR page, indicates otherwise. From http://lxr.mozilla.org/seamonkey/search-help.html: There is no size limit for simple patterns and simple patterns within Boolean expressions. More complicated patterns, such as regular expressions, are currently limited to approximately 30 characters. Lines are limited to 1024 characters. Is the documentation incorrect? Note that I'm searching for a string, not a regular expression.
Yes the documentation is incorrect. It seems that glimpse's -n option forces regex searches because typing in the glimpse search by hand and removing the -n option lets you search for long strings (but is useless for using in lxr). BTW, searching for "ntProcessComponentDirectory" gives the same results as searching for the entire string.
vrfy wontfix - sorry
Status: RESOLVED → VERIFIED
QA Contact: timeless
QA Contact: timeless → lxr
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.