Closed Bug 950957 Opened 11 years ago Closed 11 years ago

mach completion on relative paths busted

Categories

(Firefox Build System :: General, defect)

defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED FIXED
mozilla29

People

(Reporter: mt, Assigned: mt)

Details

Attachments

(1 file)

The default completion for mach doesn't need to try to work out what the name of the command is.  It currently gets confused if you don't have mach on the path and the command is not run from $srcdir.

The fix is easy, run "${COMP_WORDS[0]}".  The only risk (which already existed) is that this rule fires on something that is not mach, but bash thinks it is.
Attachment #8348391 - Flags: review?(gps)
Comment on attachment 8348391 [details] [diff] [review]
Completion based on COMP_WORDS[0]

Review of attachment 8348391 [details] [diff] [review]:
-----------------------------------------------------------------

This looks good to me. Thanks for the patch!
Attachment #8348391 - Flags: review?(gps) → review+
Comment on attachment 8348391 [details] [diff] [review]
Completion based on COMP_WORDS[0]

Can I leave the checkin to you then?
Attachment #8348391 - Flags: checkin?(gps)
I just set checkin-needed and let the tree sheriffs land when they think it's a good time. Typically less than 24h.
Keywords: checkin-needed
Attachment #8348391 - Flags: checkin?(gps) → checkin+
https://hg.mozilla.org/mozilla-central/rev/27cf4fe3975b
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: