id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	blockedby	blocking	branch_state	votes
3532	Find File's line numbers are meaningless for parsed files	egmont		"Have an uncompressed manual page in its raw *roff format, e.g. bash.1 residing in a directory.

Perform a Find File for some content that occurs in the manual, e.g. ""tilde expansion"". You'll see a couple of results appearing, along with line numbers.

Press F3 to view the file at one of these matching numbers. The expected string won't be there.

This is because line numbers are according to the raw file, whereas before displaying they are formatted by the *roff pipeline.

For similar reasons, there can be false positives (e.g. on manpage formatting keywords) or missed matches (e.g. gzipped files) as well.
"	defect	closed	minor		mc-core	master	duplicate					no branch