Age | Commit message (Collapse) | Author |
|
Only cloneable when testing, the types git2::Config and
git2::Repository in GitConfig contain C pointers and can't
really be cloned.
|
|
Ref #829
|
|
|
|
Unify handling of styles parsed from raw line and computed diff
styles. This enables syntax highlighting to be used in color-moved
sections.
Fixes #72
|
|
Similar to 7a64fa5a26314c05c811d7c1276388a4963fa0bd which allowed
custom styles. Custom styles must end in -style, but colors can be
anything. It unfortunately seems not to be possible currently to store
a global reference to git config, hence the size of this
commit (passing the reference down the call stack).
|
|
Fixes #426
Partial versions of these changes were previously in master and then
reverted multiple times.
See #746
0745f853d4bed52aca0b6739ac452d54ff54a153
3aab5d19569fa52ace2d7e6d196a1256990c4e20
|
|
|
|
If the current line does not fit into the panel, then
it is not truncated but split into multiple lines. A
wrapping symbol is placed at the end of the line. If
the new line is short enough, it is right-aligned.
Wrapping is limited to a certain number of lines
(--wrap-max-lines), if this is exceeded the line is
truncated by a now highlighted truncation symbol.
To disable wrapping set this value to 0.
|
|
|
|
|
|
Fixes #481
|
|
* remove some clippy warnings
* revert comparison_chain clippy lint
Allow it locally
|
|
|
|
Reimplement utility functions from `console` crate, but with support
for OSC sequences.
|
|
|
|
|
|
|
|
|
|
|
|
- Inspect the raw hunk line
- If it does not appear to be a standard minus/plus line, treat it as moved
- Apply special delta color-moved-* styles
|
|
|
|
|
|
|
|
Drop old command --show-background-colors
|
|
|
|
|
|
Thanks @phillipwood
|
|
|
|
'underline' and 'overline' are interpreted specially (as a decoration
directive), for backwards-compatibility with early versions of delta.
|
|
Ref #205
|
|
|
|
|
|
|
|
This isn't a correct approach. The problem being addressed is that
currently, Style instances are being used to represent things like the
presence of an emph section in a line with edit annotations. A
consequence is that if an emph and non-emph section are styled the
same, then it's impossible to tell that the sections are different in
any way at all. I think the correct approach is probably to start
using a Struct that models elements such as emph/non-emph to represent
these things, and make each such struct instance possess a style.
|
|
|
|
|
|
If this attribute is set in --thing-style then the `thing` element
text received from git should be passed though unchanged. (It may or
may not have a decoration.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Do not apply foreground syntax style if it is "null syntect style"
This isn't really correct. We should find either a valid sentinel
value, or a way to only do the superimposing when we're doing
syntax-highlighting.
- Add --zero-style option (style for unchanged hunk lines)
- Implement --color-only using an option rewrite rule
|
|
|
|
https://git-scm.com/docs/git-config#Documentation/git-config.txt-color
- Support "syntax" pseudo foreground color
- Delete the --syntax-highlight CLI option
This was never released.
|
|
Fixes #110
With this commit, delta enters "24 bit color mode" iff either of the
following are true:
1. The --24-bit-color command line option value is "always"
2. The --24-bit-color command line option value is "auto" and the
COLORTERM environment variable is set to "truecolor" or "24bit".
See
https://gist.github.com/XVilka/8346728#true-color-detection
https://github.com/sharkdp/bat/blob/7779d9f6221b3e98c43a43ceb5596ba285fdf4f8/src/bin/bat/app.rs#L29-L33
Otherwise, delta enters "8-bit color mode".
In "24 bit color mode", delta will
1. Emit 24-bit RGB color shell escape sequences that will only be
displayed correctly by a terminal application that supports 24 bit
colors.
2. Select default background colors that will only be displayed
correctly by a terminal application that supports 24 bit colors.
In "8-bit color mode", delta will
1. Emit color shell escape sequences specifying the entry in the ANSI
256 color palette that is closest (according to the ansi_colours
library) to the requested color.
2. Select default background colors that will work well in a terminal
application that supports 8-bit color but not 24-bit color.
|