Tsugikazu Shibata <tshibata@xxxxxxxxxxxxx> writes: > So, question is why we should think of this field in case of non > programming language files ? > In case of text file using any coding, Should we need to add something > after "@@"? See gitattributes(5), "Defining a custom hunk-header". The associated configuration variable for this feature is somewhat misnamed [*1*], but if you do not want to see anything, I think you should be able to define a custom pattern that match emptyness. For .txt files, I always hoped that someday, somebody clever would come up with a custom pattern to grok AsciiDoc mark-up to pick a label-looking line so that the hunks in patches to our documentation would be easier to find. A simpler and more generally applicable possibility is to find the previous line that starts a paragraph (e.g. you would pick "For .txt files..." for this part because it is the non-blank line that immediately follows the first blank line before this part). But I think the code to find an appropriate string for hunk header is not capable of looking at more than one line, so neither of these would be easy to implement without changing the underlying logic and semantics of "diff.*.funcname" configuration. [Footnote] *1* It may be misnamed but it is in line with GNU diff, though. They call -p "show-c-function" and -F "show-function-line" -- both assume function names are what people are interested in having on hunk headers. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
