How to find the function to which a line belongs with git?












0















I understand that git grep -n <line>
will give the function name to which that line belongs.

Also git log -L 539,540:webpack/webpack.config.js gives the commit history of lines 539-540 & git log -L functionName:webpack/webpack.config.js gives the commit history of the procedure functionName()



Is there a way to combine both of this and get the commit history of the function to which 539,549:webpack/webpack.config.js belongs.

Essentially, a way to find to which function the lines belong would be enough.



Also this is not for manual viewing. I will be using this commands in a program to find the commit history of the function. So, checking the context and finding the function name and then using it is not an option.










share|improve this question

























  • Have you tried using the --context (or -C, for short) flag? If you tune the number of leading and trailing lines to your needs, you should be able to see the name of the function containing the match.

    – jubobs
    Nov 20 '18 at 10:41











  • Hi, -C in grep or log?

    – Arshak Anj
    Nov 20 '18 at 10:58











  • Also, check the edit on the question. This is not for manual use.

    – Arshak Anj
    Nov 20 '18 at 11:04






  • 1





    If you want this to be programmatic, your approach will need to know about JS syntax. That's going to be more complicated...

    – jubobs
    Nov 20 '18 at 11:19
















0















I understand that git grep -n <line>
will give the function name to which that line belongs.

Also git log -L 539,540:webpack/webpack.config.js gives the commit history of lines 539-540 & git log -L functionName:webpack/webpack.config.js gives the commit history of the procedure functionName()



Is there a way to combine both of this and get the commit history of the function to which 539,549:webpack/webpack.config.js belongs.

Essentially, a way to find to which function the lines belong would be enough.



Also this is not for manual viewing. I will be using this commands in a program to find the commit history of the function. So, checking the context and finding the function name and then using it is not an option.










share|improve this question

























  • Have you tried using the --context (or -C, for short) flag? If you tune the number of leading and trailing lines to your needs, you should be able to see the name of the function containing the match.

    – jubobs
    Nov 20 '18 at 10:41











  • Hi, -C in grep or log?

    – Arshak Anj
    Nov 20 '18 at 10:58











  • Also, check the edit on the question. This is not for manual use.

    – Arshak Anj
    Nov 20 '18 at 11:04






  • 1





    If you want this to be programmatic, your approach will need to know about JS syntax. That's going to be more complicated...

    – jubobs
    Nov 20 '18 at 11:19














0












0








0








I understand that git grep -n <line>
will give the function name to which that line belongs.

Also git log -L 539,540:webpack/webpack.config.js gives the commit history of lines 539-540 & git log -L functionName:webpack/webpack.config.js gives the commit history of the procedure functionName()



Is there a way to combine both of this and get the commit history of the function to which 539,549:webpack/webpack.config.js belongs.

Essentially, a way to find to which function the lines belong would be enough.



Also this is not for manual viewing. I will be using this commands in a program to find the commit history of the function. So, checking the context and finding the function name and then using it is not an option.










share|improve this question
















I understand that git grep -n <line>
will give the function name to which that line belongs.

Also git log -L 539,540:webpack/webpack.config.js gives the commit history of lines 539-540 & git log -L functionName:webpack/webpack.config.js gives the commit history of the procedure functionName()



Is there a way to combine both of this and get the commit history of the function to which 539,549:webpack/webpack.config.js belongs.

Essentially, a way to find to which function the lines belong would be enough.



Also this is not for manual viewing. I will be using this commands in a program to find the commit history of the function. So, checking the context and finding the function name and then using it is not an option.







git grep command-line-interface






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 '18 at 11:35









Liam

16.1k1676129




16.1k1676129










asked Nov 20 '18 at 10:35









Arshak AnjArshak Anj

103




103













  • Have you tried using the --context (or -C, for short) flag? If you tune the number of leading and trailing lines to your needs, you should be able to see the name of the function containing the match.

    – jubobs
    Nov 20 '18 at 10:41











  • Hi, -C in grep or log?

    – Arshak Anj
    Nov 20 '18 at 10:58











  • Also, check the edit on the question. This is not for manual use.

    – Arshak Anj
    Nov 20 '18 at 11:04






  • 1





    If you want this to be programmatic, your approach will need to know about JS syntax. That's going to be more complicated...

    – jubobs
    Nov 20 '18 at 11:19



















  • Have you tried using the --context (or -C, for short) flag? If you tune the number of leading and trailing lines to your needs, you should be able to see the name of the function containing the match.

    – jubobs
    Nov 20 '18 at 10:41











  • Hi, -C in grep or log?

    – Arshak Anj
    Nov 20 '18 at 10:58











  • Also, check the edit on the question. This is not for manual use.

    – Arshak Anj
    Nov 20 '18 at 11:04






  • 1





    If you want this to be programmatic, your approach will need to know about JS syntax. That's going to be more complicated...

    – jubobs
    Nov 20 '18 at 11:19

















Have you tried using the --context (or -C, for short) flag? If you tune the number of leading and trailing lines to your needs, you should be able to see the name of the function containing the match.

– jubobs
Nov 20 '18 at 10:41





Have you tried using the --context (or -C, for short) flag? If you tune the number of leading and trailing lines to your needs, you should be able to see the name of the function containing the match.

– jubobs
Nov 20 '18 at 10:41













Hi, -C in grep or log?

– Arshak Anj
Nov 20 '18 at 10:58





Hi, -C in grep or log?

– Arshak Anj
Nov 20 '18 at 10:58













Also, check the edit on the question. This is not for manual use.

– Arshak Anj
Nov 20 '18 at 11:04





Also, check the edit on the question. This is not for manual use.

– Arshak Anj
Nov 20 '18 at 11:04




1




1





If you want this to be programmatic, your approach will need to know about JS syntax. That's going to be more complicated...

– jubobs
Nov 20 '18 at 11:19





If you want this to be programmatic, your approach will need to know about JS syntax. That's going to be more complicated...

– jubobs
Nov 20 '18 at 11:19












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fstackoverflow.com%2fquestions%2f53391093%2fhow-to-find-the-function-to-which-a-line-belongs-with-git%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • 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%2fstackoverflow.com%2fquestions%2f53391093%2fhow-to-find-the-function-to-which-a-line-belongs-with-git%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







Popular posts from this blog

MongoDB - Not Authorized To Execute Command

in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith

How to fix TextFormField cause rebuild widget in Flutter