Page MenuHomePhabricator

When highlighting source, catch "python" for the PHP parser
ClosedPublic

Authored by epriestley on Feb 28 2019, 8:57 PM.
Tags
None
Referenced Files
F15445953: D20231.id48291.diff
Thu, Mar 27, 4:43 PM
F15439347: D20231.id48301.diff
Wed, Mar 26, 7:06 AM
F15436130: D20231.id.diff
Tue, Mar 25, 12:07 PM
F15432025: D20231.diff
Mon, Mar 24, 3:54 PM
F15430450: D20231.id.diff
Mon, Mar 24, 7:44 AM
F15426191: D20231.id48291.diff
Sun, Mar 23, 7:38 AM
F15413500: D20231.id48291.diff
Wed, Mar 19, 7:12 PM
F15401407: D20231.diff
Mon, Mar 17, 5:30 PM
Subscribers
None

Details

Summary

See PHI1065. Normally, Python files are called ".py" and we end up with the lexer coded as "py" by the time we get here, but if you "Highlight As..." and select "Python" we can end up here with "python". (Probably also if you name a file "something.python", although this is very unusual.)

Catch both "py" and "python" for our highlighter.

T3626 should eventually standardize and moot this, but since this patch is only a quarter of a line long it seems reasonable until then.

Test Plan

Added a phlog(), verified we now hit the first-party highlighter with "Highlight As... > Python".

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable