Skip to content
Snippets Groups Projects
line-range-format.txt 1.13 KiB
Newer Older
  • Learn to ignore specific revisions
  • '<start>' and '<end>' can take one of these forms:
    
    Jean-Noël Avila's avatar
    Jean-Noël Avila committed
    
    - number
    +
    
    If '<start>' or '<end>' is a number, it specifies an
    
    Jean-Noël Avila's avatar
    Jean-Noël Avila committed
    absolute line number (lines count from 1).
    +
    
    
    - `/regex/`
    
    Jean-Noël Avila's avatar
    Jean-Noël Avila committed
    +
    This form will use the first line matching the given
    
    POSIX regex. If '<start>' is a regex, it will search from the end of
    
    Jean-Noël Avila's avatar
    Jean-Noël Avila committed
    the previous `-L` range, if any, otherwise from the start of file.
    
    If '<start>' is `^/regex/`, it will search from the start of file.
    If '<end>' is a regex, it will search
    starting at the line given by '<start>'.
    
    Jean-Noël Avila's avatar
    Jean-Noël Avila committed
    +
    
    - +offset or -offset
    +
    
    This is only valid for '<end>' and will specify a number
    of lines before or after the line given by '<start>'.
    
    Jean-Noël Avila's avatar
    Jean-Noël Avila committed
    
    +
    
    If `:<funcname>` is given in place of '<start>' and '<end>', it is a
    
    Jean-Noël Avila's avatar
    Jean-Noël Avila committed
    regular expression that denotes the range from the first funcname line
    
    that matches '<funcname>', up to the next funcname line. `:<funcname>`
    
    Jean-Noël Avila's avatar
    Jean-Noël Avila committed
    searches from the end of the previous `-L` range, if any, otherwise
    
    from the start of file. `^:<funcname>` searches from the start of
    file. The function names are determined in the same way as `git diff`
    works out patch hunk headers (see 'Defining a custom hunk-header'
    in linkgit:gitattributes[5]).