Autocomplete in make based on possible targetszsh autocomplete directoryCustom bash autocomplete for git breaks other git autocomplete featuresUnable to autocomplete ONLY when typing a make commandBash autocomplete with vim commandpmount hangs on BASH autocompleteCan I change how zsh autocomplete works?How do certain commands change the tabbed autocomplete criteria?bash custom tab completion with wildcardsDefine paths zsh autocomplete usesMake Bash autocomplete guess the closest approximation

How can I use the arrow sign in my bash prompt?

Best way to store options for panels

Bash method for viewing beginning and end of file

How do I define a right arrow with bar in LaTeX?

Is exact Kanji stroke length important?

Can criminal fraud exist without damages?

How to verify if g is a generator for p?

Implement the Thanos sorting algorithm

What's the purpose of "true" in bash "if sudo true; then"

What is difference between behavior and behaviour

If a character can use a +X magic weapon as a spellcasting focus, does it add the bonus to spell attacks or spell save DCs?

Can I convert a rim brake wheel to a disc brake wheel?

What would happen if the UK refused to take part in EU Parliamentary elections?

Minimal reference content

How to be diplomatic in refusing to write code that breaches the privacy of our users

quarter to five p.m

Have I saved too much for retirement so far?

Why does John Bercow say “unlock” after reading out the results of a vote?

Where in the Bible does the greeting ("Dominus Vobiscum") used at Mass come from?

What is the intuitive meaning of having a linear relationship between the logs of two variables?

Is there any reason not to eat food that's been dropped on the surface of the moon?

Cynical novel that describes an America ruled by the media, arms manufacturers, and ethnic figureheads

Opposite of a diet

Should my PhD thesis be submitted under my legal name?



Autocomplete in make based on possible targets


zsh autocomplete directoryCustom bash autocomplete for git breaks other git autocomplete featuresUnable to autocomplete ONLY when typing a make commandBash autocomplete with vim commandpmount hangs on BASH autocompleteCan I change how zsh autocomplete works?How do certain commands change the tabbed autocomplete criteria?bash custom tab completion with wildcardsDefine paths zsh autocomplete usesMake Bash autocomplete guess the closest approximation













6















The Makefile is:



%.pdf: %.tex
rubber -d $<


If there is a doc.tex in the directory, then make doc.pdf builds doc.pdf. The problem is that when I type make, the autocompletion gives nothing: it doesn't even allow to autocomplete to make doc.tex. What can be done about it?










share|improve this question














bumped to the homepage by Community yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Completion is handled by bash-completion, not by bash, nor by make. bash-completion needs a list of valid targets to show you. I don't think it's possible to convince make to produce such a list when you're using wildcard rules.

    – Satō Katsura
    Oct 26 '16 at 7:01






  • 1





    Even zsh's completion isn't that smart.

    – Gilles
    Oct 27 '16 at 22:49











  • Possible duplicate: stackoverflow.com/q/516305/21348

    – asalamon74
    Aug 11 '17 at 13:55















6















The Makefile is:



%.pdf: %.tex
rubber -d $<


If there is a doc.tex in the directory, then make doc.pdf builds doc.pdf. The problem is that when I type make, the autocompletion gives nothing: it doesn't even allow to autocomplete to make doc.tex. What can be done about it?










share|improve this question














bumped to the homepage by Community yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Completion is handled by bash-completion, not by bash, nor by make. bash-completion needs a list of valid targets to show you. I don't think it's possible to convince make to produce such a list when you're using wildcard rules.

    – Satō Katsura
    Oct 26 '16 at 7:01






  • 1





    Even zsh's completion isn't that smart.

    – Gilles
    Oct 27 '16 at 22:49











  • Possible duplicate: stackoverflow.com/q/516305/21348

    – asalamon74
    Aug 11 '17 at 13:55













6












6








6


1






The Makefile is:



%.pdf: %.tex
rubber -d $<


If there is a doc.tex in the directory, then make doc.pdf builds doc.pdf. The problem is that when I type make, the autocompletion gives nothing: it doesn't even allow to autocomplete to make doc.tex. What can be done about it?










share|improve this question














The Makefile is:



%.pdf: %.tex
rubber -d $<


If there is a doc.tex in the directory, then make doc.pdf builds doc.pdf. The problem is that when I type make, the autocompletion gives nothing: it doesn't even allow to autocomplete to make doc.tex. What can be done about it?







bash make autocomplete






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 26 '16 at 6:43









VelkanVelkan

236210




236210





bumped to the homepage by Community yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.














  • Completion is handled by bash-completion, not by bash, nor by make. bash-completion needs a list of valid targets to show you. I don't think it's possible to convince make to produce such a list when you're using wildcard rules.

    – Satō Katsura
    Oct 26 '16 at 7:01






  • 1





    Even zsh's completion isn't that smart.

    – Gilles
    Oct 27 '16 at 22:49











  • Possible duplicate: stackoverflow.com/q/516305/21348

    – asalamon74
    Aug 11 '17 at 13:55

















  • Completion is handled by bash-completion, not by bash, nor by make. bash-completion needs a list of valid targets to show you. I don't think it's possible to convince make to produce such a list when you're using wildcard rules.

    – Satō Katsura
    Oct 26 '16 at 7:01






  • 1





    Even zsh's completion isn't that smart.

    – Gilles
    Oct 27 '16 at 22:49











  • Possible duplicate: stackoverflow.com/q/516305/21348

    – asalamon74
    Aug 11 '17 at 13:55
















Completion is handled by bash-completion, not by bash, nor by make. bash-completion needs a list of valid targets to show you. I don't think it's possible to convince make to produce such a list when you're using wildcard rules.

– Satō Katsura
Oct 26 '16 at 7:01





Completion is handled by bash-completion, not by bash, nor by make. bash-completion needs a list of valid targets to show you. I don't think it's possible to convince make to produce such a list when you're using wildcard rules.

– Satō Katsura
Oct 26 '16 at 7:01




1




1





Even zsh's completion isn't that smart.

– Gilles
Oct 27 '16 at 22:49





Even zsh's completion isn't that smart.

– Gilles
Oct 27 '16 at 22:49













Possible duplicate: stackoverflow.com/q/516305/21348

– asalamon74
Aug 11 '17 at 13:55





Possible duplicate: stackoverflow.com/q/516305/21348

– asalamon74
Aug 11 '17 at 13:55










1 Answer
1






active

oldest

votes


















0














The bash-completion package doesn't do this, it does some acrobatics to handle both command line options and extract a list of Makefile targets, but it does not try to generate matches by applying wildcards or otherwise handling any pattern rules.



It can be done however, here's a simple version with a few caveats.



function _mkcache() 
gawk '/^# *Make data base/,/^# *Finished Make data base/
if (/^# Not a target/) getline; next
## handle "target: ..."
if (match($0,/^([^.#% ][^:%=]+) *:($' > ".$_file:-Makefile.targets"


function _bc_make()
local ctok=$COMP_WORDS[COMP_CWORD] # curr token
local ptok=$COMP_WORDS[COMP_CWORD-1] # prev token
local -a mkrule maybe
local try rr lhs rhs rdir pat makefile=Makefile

## check we're not doing any make options
[[ $ctok:0:1 != "-" && ! $ptok =~ ^-[fCIjloW] ]] && try="$rdir$rhs/%/$ctok*"

maybe=( $(compgen -G "$try") ) # try must be quoted

## maybe[] is an array of filenames from expanded prereq globs
(( $#maybe[*] )) &&

[[ "$rhs" =~ % ]] &&
## promote rhs glob to a regex: % -> (.*)
rhs="$rhs/./\."
pat="$rdir$rhs/%/(.*)"

## use regex to extract stem from RHS, sub "%" on LHS
for nn in "$maybe[@]"; do
[[ $nn =~ $pat ]] &&
COMPREPLY+=( "$lhs/%/$BASH_REMATCH[1]" )

done

done
return

COMPREPLY=() #default

complete -F _bc_make $MAKE:-make


There are two parts, a function _mkcache extracts all the rules and targets from a Makefile and caches these. It also does a bit of processing so the rules are simplified to a single "target : pre-req" form in that cache.



Then, a completion function _bc_make takes the token you attempt completion on and tries to match against targets, and uses the pattern rules to expand a glob based on the pre-requisites and the word for completion. If one or more matches are found, it builds a list of targets based on the pattern rules.



GNU make is assumed. It should correctly handle:



  • targets and pattern rules (though not all of them, see below)

  • new and old form .c.o%.o : %.c

  • paths in prereqs (e.g RCS/)

  • with or without all default rules (add -r to make if preferred)

Caveats, and not supported:



  • intermediate or chained dependencies, it's not as smart as make


  • VPATH or vpath

  • .SUFFIXES

  • make -C dir

  • "archive(member)" targets, explicit or implicit


  • make options expansion

  • pathological junk in the environment that can cause Makefile parsing problems (TERMCAP for example)

  • Makefiles named other than Makefile

Somme of the above can be added relatively simply, others like the archive handling are not so simple.






share|improve this answer
























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f318992%2fautocomplete-in-make-based-on-possible-targets%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    The bash-completion package doesn't do this, it does some acrobatics to handle both command line options and extract a list of Makefile targets, but it does not try to generate matches by applying wildcards or otherwise handling any pattern rules.



    It can be done however, here's a simple version with a few caveats.



    function _mkcache() 
    gawk '/^# *Make data base/,/^# *Finished Make data base/
    if (/^# Not a target/) getline; next
    ## handle "target: ..."
    if (match($0,/^([^.#% ][^:%=]+) *:($' > ".$_file:-Makefile.targets"


    function _bc_make()
    local ctok=$COMP_WORDS[COMP_CWORD] # curr token
    local ptok=$COMP_WORDS[COMP_CWORD-1] # prev token
    local -a mkrule maybe
    local try rr lhs rhs rdir pat makefile=Makefile

    ## check we're not doing any make options
    [[ $ctok:0:1 != "-" && ! $ptok =~ ^-[fCIjloW] ]] && try="$rdir$rhs/%/$ctok*"

    maybe=( $(compgen -G "$try") ) # try must be quoted

    ## maybe[] is an array of filenames from expanded prereq globs
    (( $#maybe[*] )) &&

    [[ "$rhs" =~ % ]] &&
    ## promote rhs glob to a regex: % -> (.*)
    rhs="$rhs/./\."
    pat="$rdir$rhs/%/(.*)"

    ## use regex to extract stem from RHS, sub "%" on LHS
    for nn in "$maybe[@]"; do
    [[ $nn =~ $pat ]] &&
    COMPREPLY+=( "$lhs/%/$BASH_REMATCH[1]" )

    done

    done
    return

    COMPREPLY=() #default

    complete -F _bc_make $MAKE:-make


    There are two parts, a function _mkcache extracts all the rules and targets from a Makefile and caches these. It also does a bit of processing so the rules are simplified to a single "target : pre-req" form in that cache.



    Then, a completion function _bc_make takes the token you attempt completion on and tries to match against targets, and uses the pattern rules to expand a glob based on the pre-requisites and the word for completion. If one or more matches are found, it builds a list of targets based on the pattern rules.



    GNU make is assumed. It should correctly handle:



    • targets and pattern rules (though not all of them, see below)

    • new and old form .c.o%.o : %.c

    • paths in prereqs (e.g RCS/)

    • with or without all default rules (add -r to make if preferred)

    Caveats, and not supported:



    • intermediate or chained dependencies, it's not as smart as make


    • VPATH or vpath

    • .SUFFIXES

    • make -C dir

    • "archive(member)" targets, explicit or implicit


    • make options expansion

    • pathological junk in the environment that can cause Makefile parsing problems (TERMCAP for example)

    • Makefiles named other than Makefile

    Somme of the above can be added relatively simply, others like the archive handling are not so simple.






    share|improve this answer





























      0














      The bash-completion package doesn't do this, it does some acrobatics to handle both command line options and extract a list of Makefile targets, but it does not try to generate matches by applying wildcards or otherwise handling any pattern rules.



      It can be done however, here's a simple version with a few caveats.



      function _mkcache() 
      gawk '/^# *Make data base/,/^# *Finished Make data base/
      if (/^# Not a target/) getline; next
      ## handle "target: ..."
      if (match($0,/^([^.#% ][^:%=]+) *:($' > ".$_file:-Makefile.targets"


      function _bc_make()
      local ctok=$COMP_WORDS[COMP_CWORD] # curr token
      local ptok=$COMP_WORDS[COMP_CWORD-1] # prev token
      local -a mkrule maybe
      local try rr lhs rhs rdir pat makefile=Makefile

      ## check we're not doing any make options
      [[ $ctok:0:1 != "-" && ! $ptok =~ ^-[fCIjloW] ]] && try="$rdir$rhs/%/$ctok*"

      maybe=( $(compgen -G "$try") ) # try must be quoted

      ## maybe[] is an array of filenames from expanded prereq globs
      (( $#maybe[*] )) &&

      [[ "$rhs" =~ % ]] &&
      ## promote rhs glob to a regex: % -> (.*)
      rhs="$rhs/./\."
      pat="$rdir$rhs/%/(.*)"

      ## use regex to extract stem from RHS, sub "%" on LHS
      for nn in "$maybe[@]"; do
      [[ $nn =~ $pat ]] &&
      COMPREPLY+=( "$lhs/%/$BASH_REMATCH[1]" )

      done

      done
      return

      COMPREPLY=() #default

      complete -F _bc_make $MAKE:-make


      There are two parts, a function _mkcache extracts all the rules and targets from a Makefile and caches these. It also does a bit of processing so the rules are simplified to a single "target : pre-req" form in that cache.



      Then, a completion function _bc_make takes the token you attempt completion on and tries to match against targets, and uses the pattern rules to expand a glob based on the pre-requisites and the word for completion. If one or more matches are found, it builds a list of targets based on the pattern rules.



      GNU make is assumed. It should correctly handle:



      • targets and pattern rules (though not all of them, see below)

      • new and old form .c.o%.o : %.c

      • paths in prereqs (e.g RCS/)

      • with or without all default rules (add -r to make if preferred)

      Caveats, and not supported:



      • intermediate or chained dependencies, it's not as smart as make


      • VPATH or vpath

      • .SUFFIXES

      • make -C dir

      • "archive(member)" targets, explicit or implicit


      • make options expansion

      • pathological junk in the environment that can cause Makefile parsing problems (TERMCAP for example)

      • Makefiles named other than Makefile

      Somme of the above can be added relatively simply, others like the archive handling are not so simple.






      share|improve this answer



























        0












        0








        0







        The bash-completion package doesn't do this, it does some acrobatics to handle both command line options and extract a list of Makefile targets, but it does not try to generate matches by applying wildcards or otherwise handling any pattern rules.



        It can be done however, here's a simple version with a few caveats.



        function _mkcache() 
        gawk '/^# *Make data base/,/^# *Finished Make data base/
        if (/^# Not a target/) getline; next
        ## handle "target: ..."
        if (match($0,/^([^.#% ][^:%=]+) *:($' > ".$_file:-Makefile.targets"


        function _bc_make()
        local ctok=$COMP_WORDS[COMP_CWORD] # curr token
        local ptok=$COMP_WORDS[COMP_CWORD-1] # prev token
        local -a mkrule maybe
        local try rr lhs rhs rdir pat makefile=Makefile

        ## check we're not doing any make options
        [[ $ctok:0:1 != "-" && ! $ptok =~ ^-[fCIjloW] ]] && try="$rdir$rhs/%/$ctok*"

        maybe=( $(compgen -G "$try") ) # try must be quoted

        ## maybe[] is an array of filenames from expanded prereq globs
        (( $#maybe[*] )) &&

        [[ "$rhs" =~ % ]] &&
        ## promote rhs glob to a regex: % -> (.*)
        rhs="$rhs/./\."
        pat="$rdir$rhs/%/(.*)"

        ## use regex to extract stem from RHS, sub "%" on LHS
        for nn in "$maybe[@]"; do
        [[ $nn =~ $pat ]] &&
        COMPREPLY+=( "$lhs/%/$BASH_REMATCH[1]" )

        done

        done
        return

        COMPREPLY=() #default

        complete -F _bc_make $MAKE:-make


        There are two parts, a function _mkcache extracts all the rules and targets from a Makefile and caches these. It also does a bit of processing so the rules are simplified to a single "target : pre-req" form in that cache.



        Then, a completion function _bc_make takes the token you attempt completion on and tries to match against targets, and uses the pattern rules to expand a glob based on the pre-requisites and the word for completion. If one or more matches are found, it builds a list of targets based on the pattern rules.



        GNU make is assumed. It should correctly handle:



        • targets and pattern rules (though not all of them, see below)

        • new and old form .c.o%.o : %.c

        • paths in prereqs (e.g RCS/)

        • with or without all default rules (add -r to make if preferred)

        Caveats, and not supported:



        • intermediate or chained dependencies, it's not as smart as make


        • VPATH or vpath

        • .SUFFIXES

        • make -C dir

        • "archive(member)" targets, explicit or implicit


        • make options expansion

        • pathological junk in the environment that can cause Makefile parsing problems (TERMCAP for example)

        • Makefiles named other than Makefile

        Somme of the above can be added relatively simply, others like the archive handling are not so simple.






        share|improve this answer















        The bash-completion package doesn't do this, it does some acrobatics to handle both command line options and extract a list of Makefile targets, but it does not try to generate matches by applying wildcards or otherwise handling any pattern rules.



        It can be done however, here's a simple version with a few caveats.



        function _mkcache() 
        gawk '/^# *Make data base/,/^# *Finished Make data base/
        if (/^# Not a target/) getline; next
        ## handle "target: ..."
        if (match($0,/^([^.#% ][^:%=]+) *:($' > ".$_file:-Makefile.targets"


        function _bc_make()
        local ctok=$COMP_WORDS[COMP_CWORD] # curr token
        local ptok=$COMP_WORDS[COMP_CWORD-1] # prev token
        local -a mkrule maybe
        local try rr lhs rhs rdir pat makefile=Makefile

        ## check we're not doing any make options
        [[ $ctok:0:1 != "-" && ! $ptok =~ ^-[fCIjloW] ]] && try="$rdir$rhs/%/$ctok*"

        maybe=( $(compgen -G "$try") ) # try must be quoted

        ## maybe[] is an array of filenames from expanded prereq globs
        (( $#maybe[*] )) &&

        [[ "$rhs" =~ % ]] &&
        ## promote rhs glob to a regex: % -> (.*)
        rhs="$rhs/./\."
        pat="$rdir$rhs/%/(.*)"

        ## use regex to extract stem from RHS, sub "%" on LHS
        for nn in "$maybe[@]"; do
        [[ $nn =~ $pat ]] &&
        COMPREPLY+=( "$lhs/%/$BASH_REMATCH[1]" )

        done

        done
        return

        COMPREPLY=() #default

        complete -F _bc_make $MAKE:-make


        There are two parts, a function _mkcache extracts all the rules and targets from a Makefile and caches these. It also does a bit of processing so the rules are simplified to a single "target : pre-req" form in that cache.



        Then, a completion function _bc_make takes the token you attempt completion on and tries to match against targets, and uses the pattern rules to expand a glob based on the pre-requisites and the word for completion. If one or more matches are found, it builds a list of targets based on the pattern rules.



        GNU make is assumed. It should correctly handle:



        • targets and pattern rules (though not all of them, see below)

        • new and old form .c.o%.o : %.c

        • paths in prereqs (e.g RCS/)

        • with or without all default rules (add -r to make if preferred)

        Caveats, and not supported:



        • intermediate or chained dependencies, it's not as smart as make


        • VPATH or vpath

        • .SUFFIXES

        • make -C dir

        • "archive(member)" targets, explicit or implicit


        • make options expansion

        • pathological junk in the environment that can cause Makefile parsing problems (TERMCAP for example)

        • Makefiles named other than Makefile

        Somme of the above can be added relatively simply, others like the archive handling are not so simple.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Aug 9 '18 at 12:35

























        answered Mar 9 '18 at 18:09









        mr.spuraticmr.spuratic

        7,0411128




        7,0411128



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f318992%2fautocomplete-in-make-based-on-possible-targets%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            -autocomplete, bash, make

            Popular posts from this blog

            Word for a person who has no opinion about whether god existsWord for having a definite opinion while simultaneously withholding judgment?What's the opposite of “newcomer? Is ”veteran" OK?What do you call an “atheist” who might believe in an afterlife?What's a word for someone who wants to voice opinions but not have them challenged?Word for someone who dismisses contrary opinions as irrational?Somone who thinks they are overly special/out of the ordinaryIs there a word, phrase or idiom for “a person who is incapable of thinking about the future”?The belief that a god is human-likeA word for a non-famous person/thing you have heard a lot aboutAdjective for a person who enjoys taking care of their appearance

            What was this official D&D 3.5e Lovecraft-flavored rulebook?What was this set of RPG tools called?As a first-time DM should I let my players play complex character classes and roles?Nymph's Kiss and the RelationshipWhat was the name of this Cleric Prestige Class that shapes metal with its bare hands?Are the 3.5e Dragonlance books third party or official works?What's up with the domain Vile Darkness?What was this 80s book about RPGs?What was the name of this Werewolf band?What book had Rituals to “upgrade” animal companions to keep them viable at higher levels?What was this RPG that had rules for player-owned businesses?

            2017 IndyCar Series Contents Series news Teams and drivers Schedule Season summary Footnotes References External links Navigation menu"INDYCAR: Initial 2018 bodywork concepts unveiled"the original"IndyCar confirms switch to Performance Friction brakes in 2017""AJ Foyt Racing will switch to Chevy"the original"Carlos Munoz, Conor Daly will drive for AJ Foyt Racing""Zach Veach's Indy 500 Debut Confirmed with Foyt""No mass exodus from Honda after Ganassi switch""Ex-F1 driver Sato joins Andretti Autosport for 2017 IndyCar season""IndyCar's Ryan Hunter-Reay, sponsor DHL paired through 2020""hhgregg and Andretti Autosport announce partnership for key races in 2016""INDYCAR: Rossi re-signs with Andretti"the original"McLaren Formula 1 - Fernando Alonso to race at Indy 500 with McLaren, Honda and Andretti Autosport""Shank will finally take part in Indy 500 with Harvey, Andretti | MotorSportsTalk""Andretti adds Jack Harvey to Indy 500 field""Ganassi switches to Honda power for 2017""INDYCAR: Chilton returns to Ganassi"the original"IndyCar silly season: Who's going where in 2017?""INDYCAR: Kanaan, NTT Data return to Ganassi"the original"Kimball to remain at Ganassi for 2017""Coyne confirms Bourdais for 2017 IndyCar season""Davison to sub for Bourdais in Indy 500"the original"Gutierrez confirmed for Detroit IndyCar debut""Gutierrez returns with Coyne for rest of 2017 season""Vautier to drive for Coyne at Texas"the original"INDYCAR: Coyne confirms Jones for 2017"the original"Pippa Mann returns to Coyne for Indy 500""Karam, Dreyer & Reinbold teaming up again for Indianapolis 500""Pigot to return to Ed Carpenter Racing""Hildebrand confirmed as full-time Ed Carpenter driver""Veach to replace injured Hildebrand at Barber"the originalNew Team Harding Racing Enters Chaves for 101st Indianapolis 500"Juncos Racing Announces Entry in 101st Running of the Indianapolis 500 :: Juncos Racing""Juncos confirms Pigot for Indy 500""Saavedra confirmed in Juncos' second 500 entry"the original"Lazier confirms Indy 500 run after son's USF2000 debut"the original"Claman DeMelo to race for RLLR at Sonoma"the original"Rahal signs Servia and ace engineer for 2017""IndyCar: Aleshin returns with Schmidt"the original"Aleshin replaced by Saavedra for Toronto""Jack Harvey will pilot SPM No. 7 car at Watkins Glen, Sonoma""Jay Howard confirmed in Tony Stewart's supported SPM Indy entry""INDYCAR: Newgarden to wave the flag at Penske"the original"Pagenaud opts for No. 1 in 2017"the original"Penske confirms Newgarden for 2017""Montoya to stay with Team Penske in 2017""Target leaving IndyCar after 27 seasons with Chip Ganassi""Cavin: IndyCar could see complete driver/team shakeup in 2017""End of the road for KV Racing?""KV Racing confirms closure, equipment sold to Juncos""Juncos confirms IndyCar Series entry"the original"Juncos readies IndyCar program, aims for '17 500"the original"Harding Racing to add Texas, Pocono to schedule"the original"Sato signs with Andretti Autosport for 2017""INDYCAR: Aleshin in Doubt at SPM"the original"Long Beach notebook: JR Hildebrand breaks hand""Hildebrand cleared to return at Phoenix"the original"Bourdais to undergo surgery on multiple fractures""Aleshin loses Schmidt Peterson IndyCar ride""Saavedra in at SPM for Pocono, Gateway"the original"Bourdais to make return at Gateway"the original"The IndyCar Grand Prix no longer is sponsored by Angie's List""2017 IndyCar Series rulebook""2017 Verizon IndyCar Series Official Rulebook"Official websiteeeeee