Search for comment in gtgrep broken

Bug #910593 reported by Byrial Jensen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PyG3T
Fix Committed
Undecided
Ask Hjorth Larsen

Bug Description

Search for comments in gtgrep seems broken:

Case 1)

$ gtgrep --comment vilje da.po

--> The program hangs reading from stdin

Case 2)

$ cat da.po | gtgrep --comment=vilje
No pattern, no files
$

No pattern?

Case 3)

$ cat da.po | gtgrep --comment=vilje da.po
$

But da.po contains the word "vilje" in a comment.

Revision history for this message
Byrial Jensen (byrial-t) wrote :

Forget the equal sign in case 1) It should read:

$ gtgrep --comment=vilje da.po

But the result is same both with and without =.

Revision history for this message
Ask Hjorth Larsen (askhl) wrote :

--comments is very broken; will fix.

Changed in pyg3t:
status: New → In Progress
assignee: nobody → Ask Hjorth Larsen (askhl)
Revision history for this message
Ask Hjorth Larsen (askhl) wrote :

gtgrepping for comments and msgctxt now works. Excuse the delay.

Changed in pyg3t:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.