]>
Commit | Line | Data |
---|---|---|
fd5c74e7 | 1 | '<start>' and '<end>' can take one of these forms: |
0ddd4719 | 2 | |
25ed3412 BY |
3 | - number |
4 | + | |
fd5c74e7 | 5 | If '<start>' or '<end>' is a number, it specifies an |
25ed3412 BY |
6 | absolute line number (lines count from 1). |
7 | + | |
8 | ||
fd5c74e7 | 9 | - `/regex/` |
25ed3412 BY |
10 | + |
11 | This form will use the first line matching the given | |
fd5c74e7 | 12 | POSIX regex. If '<start>' is a regex, it will search from the end of |
0bc2cdd5 | 13 | the previous `-L` range, if any, otherwise from the start of file. |
fd5c74e7 PB |
14 | If '<start>' is `^/regex/`, it will search from the start of file. |
15 | If '<end>' is a regex, it will search | |
16 | starting at the line given by '<start>'. | |
25ed3412 BY |
17 | + |
18 | ||
19 | - +offset or -offset | |
20 | + | |
fd5c74e7 PB |
21 | This is only valid for '<end>' and will specify a number |
22 | of lines before or after the line given by '<start>'. | |
13b8f68c | 23 | |
13b8f68c | 24 | + |
fd5c74e7 | 25 | If `:<funcname>` is given in place of '<start>' and '<end>', it is a |
d349e0ee | 26 | regular expression that denotes the range from the first funcname line |
fd5c74e7 | 27 | that matches '<funcname>', up to the next funcname line. `:<funcname>` |
d349e0ee | 28 | searches from the end of the previous `-L` range, if any, otherwise |
fd5c74e7 | 29 | from the start of file. `^:<funcname>` searches from the start of |
0cce88f1 PB |
30 | file. The function names are determined in the same way as `git diff` |
31 | works out patch hunk headers (see 'Defining a custom hunk-header' | |
32 | in linkgit:gitattributes[5]). |