summaryrefslogtreecommitdiffstats
path: root/src
AgeCommit message (Collapse)Author
2020-10-01Simplify codesharkdp
2020-10-01Remove .unwrap() in insert call to prevent crashessharkdp
2020-10-01Remove .unwrap() to prevent crashessharkdp
2020-10-01Remove non-working unit testsharkdp
2020-10-01Support XDG_CONFIG_HOME git config filesAhmed El Gabri
2020-09-20Improve --style help text, closes #1146sharkdp
2020-09-20Code formattingsharkdp
2020-09-20Improve --file-name help text, closes #1109sharkdp
2020-09-20Fix unwrap errorsharkdp
2020-09-20Use unwrapKienyew
2020-09-20Handle file extension conflicts in --list-languagesKienyew
2020-09-20Revert to previous commitKienyew
2020-09-20Fix undesired behaviorKienyew
2020-09-20Handle file extension conflicts in --list-languages (#1076)Kienyew
2020-09-14Remove unnecessary parenthesissharkdp
2020-09-14removed printlns, updated Changelog, updated manAlexander Karlis
2020-09-14updated PR based on commentsAlexander Karlis
2020-09-14remove printlnAlexander Karlis
2020-09-14added additional alias for color=always when always-decorations flag is ↵Alexander Karlis
triggered
2020-09-14Added new alias for 'decoration=always'Alexander Karlis
2020-09-14Adds custom mapping for nginx and apache config filesNiklas Mohrin
2020-08-12Fix TypoKienyew
2020-08-03Add new theme: base16-256Mitchell Kember
Bat already has a base16 theme. The new base16-256 theme is for users of base16-shell, who configure their terminal with a 256-color variant of a base16 theme. These variants put some of the base16 colors in elsewhere in the 256-color table to avoid clobbering bright color slots (ansi codes 8 to 15) with colors that don't respect the ordinary meaning of that slot (e.g. bright green in ordinary base16 is not green). For more details, see https://github.com/chriskempson/base16-shell
2020-07-25Update --help text for --colorsharkdp
2020-07-09Switch to "·" (U+00B7) Middle Dot from "•" (U+2022) BulletDash Peters
2020-07-09Update generated config to reflect pager argument behaviourAttila Gonda
2020-07-02Hide alias in help, update man and completionsDash Peters
A long alias doesn't make sense, since `--paging=never` already exists
2020-07-02Merge remote-tracking branch 'sharkdp/master'Dash Peters
2020-07-02Merge pull request #1066 from gsomix/feature/1061-show-all-redirectedDavid Peter
Enable non-printable characters for redirected output
2020-07-02Enable non-printable chars for redirected output (#1061)Evgeniy Andreev (gsomix)
2020-07-01Change to name no-paging, add long flag and aliasDash Peters
2020-06-30Add short flag for --paging=neverDash Peters
2020-06-26Defaults *.fs to F#Caio Alonso
2020-06-21Highlight pacman hooks as iniGuido Cella
2020-06-21Highlight systemd files as iniGuido Cella
2020-06-03Remove explicit type annotationsharkdp
2020-06-03Prevent allocation of additional Stringssharkdp
2020-06-03Use 'or_insert_with'sharkdp
2020-06-03Return mappings as a slicesharkdp
2020-06-03Use 'if let' instead of 'match'sharkdp
2020-06-03Incorporating feedbackAlex Novak
2020-06-03Adds a little logic to main to get other mappings from configAlex Novak
2020-06-03Revert 9ed8db22c ('windows' pager process execution fix) based on PR ↵Roy Ivy III
feedback/owner request
2020-06-03Fix pager process execution under 'windows'Roy Ivy III
## [why] For 'windows' platforms, directly spawning a process (eg, called PATHNAME) bypasses the usual windows shell machinery for determining which process to execute. Specifically, the extensions in PATHEXT will not be used to determine the final executable. So, `PATHNAME.bat`, `PATHNAME.cmd`, ... will *not* be executed even if on they exist on the PATH; and this is counter to the usual expectation of a Windows user. Additionally, built-in commands, such as `echo` and `dir`, will never be accessible as they do not have a PATH to execute and, so, will never be found. To use the usual machinery, giving access to PATHNAME.bat and `echo`, execute the PATHNAME using the windows shell, eg `cmd /d/c PATHNAME`. Note this may expose the constructed command line to the windows shell quoting vagaries (sadly, that may be part of the price). Following Windows standards, the ComSpec environment variable is used to determine which shell to use, with a fallback to the "modern", built-in `cmd` shell.
2020-06-03Fix compiler warning for 'windows' tests (dead_code)Roy Ivy III
2020-05-29Change use of 'BatInput' to 'input::Input'Ethan P
2020-05-29Remove unnecessary '-> ()'sEthan P
2020-05-29Replace Input::stdin_as_file with bat-application functionsEthan P
2020-05-29Remove unused with_name for theme preview fileEthan P
2020-05-29Remove Input.as_file and add Input::stdin_as_fileEthan P