Bumps [assert_cmd](https://github.com/assert-rs/assert_cmd) from 0.11.0 to 0.11.1.
*Sourced from [assert_cmd's changelog](https://github.com/assert-rs/assert_cmd/blob/master/CHANGELOG.md).*
> ## 0.11.1 (2019-03-23)
> #### Bug Fixes
> * **stdin:** Docs didn't work ([2d4756a2](https://github.com/assert-rs/assert_cmd/commit/2d4756a2e20cafd5fa8904090eee53798a825196), closes [#71](https://github-redirect.dependabot.com/assert-rs/assert_cmd/issues/71))
> <a name="0.11.0"></a>
- [`e3070fa`](https://github.com/assert-rs/assert_cmd/commit/e3070fa292af3495d873a13f7667f186aef5b6da) chore: Release v0.11.1
- [`7acfee7`](https://github.com/assert-rs/assert_cmd/commit/7acfee7e988ad3ef66e582ee872ecd1f39872400) Merge pull request [#72](https://github-redirect.dependabot.com/assert-rs/assert_cmd/issues/72) from epage/stdin
- [`2d4756a`](https://github.com/assert-rs/assert_cmd/commit/2d4756a2e20cafd5fa8904090eee53798a825196) fix(stdin): Docs didn't work
- [`84f6332`](https://github.com/assert-rs/assert_cmd/commit/84f633258e8dda9abe5228232d8f63e00bbf14c5) docs: Update changelog to help with the transition
- See full diff in [compare view](https://github.com/assert-rs/assert_cmd/compare/v0.11.0...v0.11.1)
[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=assert_cmd&package-manager=cargo&previous-version=0.11.0&new-version=0.11.1)](https://dependabot.com/compatibility-score.html?dependency-name=assert_cmd&package-manager=cargo&previous-version=0.11.0&new-version=0.11.1)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
<summary>Dependabot commands and options</summary>
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
Paging isn't enabled automatically and doesn't work with ```bat --paging always```
This new syntax file is based on [Ionide's grammar file @ be0bdfd1](https://github.com/ionide/ionide-fsgrammar/blob/be0bdfd1/grammar/fsharp.json), which also fixes some problems with the previous one.
I currently use bat as cat replacement but because bat uses line numbers and file notations i added the `-p` flag in my fish config:
bat -p $argv
This works great but i noticed there is no output when i bat over binary files.
yes i know that this is totally useless but this confuses me sometimes with thinking that it's just an empty text file.
It would be nice to get some feedback like cat where it shows a corrupted output or let it say something like `<BINARY>` the same as without `-p`
**How to reproduce:**
`echo 'v5.18' | bat -l perl`
All string is highlighted with one color — it's a version string: https://perldoc.perl.org/perldata.html
`v5`, `.` and `18` are highlighted with three different colors.
### Initial Shell Completions
For fish shell only; contains completions for flags but does not include flag sub-options like language lists or subcommands.
From what I understand #482 took place because of bugs with completion autogeneration. I added the 'completions' directory to assets so that perhaps others will follow with ported or manually written bash/zsh completions.
I would like to use `bat` as my `MANPAGER`. I am not a fan of `most(1)`, my current alternative is using `nvim(1)` with the `:Man!` command.
* theme TwoDark
I executed `bat` on `.sh`, but Brackets color does not correspond.
This bug was only in this line, and there was no problem except it.
I'd be more than happy to create an automatically updating Chocolatey package to hand off to whoever wants it -- is that interesting at all? I use Chocolatey to automate my own workflow right now, and this is a slick tool I'd love to add to my automatic toolbelt. :)
When updating the `assets/syntaxes/Packages` submodule to the latest state, calling `assets/create.sh` fails with:
[..] assets/syntaxes/Packages/Go/Go.sublime-syntax: Invalid YAML file syntax
This is probably an upstream problem (either in sublimehq/Packages or syntect). Any help is greatly appreciated.
I spent a lot of time to customize my terminal named colors, and I wish there was a bat theme that uses them so it doesn’t look bad in my terminal.
The benefit is that it provides a backup theme that works across terminals if no other theme works with the terminal theme.
Would you be amenable to accepting a separate highlighter for fish? Currently bat is using the bash syntax highlighter for fish files - whilst this is close, bash and fish do have different syntaxes. As to usage stats, I'd imagine (but I have no actually evidence of this) that fish is the 3rd most popular shell behind bash and zsh and that it's in pretty wide use. There's a sublime package for it that has about 8K installations. I could make a PR, but I thought I'd ask first
This is an experiment to work on #423
% bat --version
% bat --style=plain .DS_Store
% bat --style=changes .DS_Store
% bat --style=grid .DS_Store
% bat --style=numbers .DS_Store
% bat --style=header .DS_Store
File: .DS_Store <BINARY>
`--style=full` omitted as it's somewhat bulky.
Personally I am using `bat` indirectly through commands I'm already familiar with:
% which cat
cat: aliased to bat --plain --paging=never
% which more
more: aliased to bat --plain --pager="less --no-init --quit-at-eof"
So my preference would be to just spew binary data and junk to my terminal. However, in other modes any sort of indication that the output is being omitted would be helpful.
I believe this is related to https://github.com/sharkdp/bat/issues/248 and the issue is present in `master`.
Continued discussion from #440 regarding `bat` showing diff chunks.
Currently, inside of a git repo, `bat` will compare the file being viewed with the previous version and decorate the left-hand gutter with
- Green `+` to indicate that the line has been added
- Red `-` to indicate that one or more lines have been removed
- Yellow `~` to indicate that the line has changed
This feature request asks that `bat` go a step further by inserting the block of old lines into the output:
- Where lines have been added, no change is necessary; they are decorated with a green `+`
- Where lines have been removed, display the old lines in a monochrome color (gray?) decorated with a red `-`
- Where lines have been changed,
- display the old lines in a monochrome color (gray?) decorated with a red `-`
- decorate the replacement/current lines with a green `+`
A couple additional things that would be nice to have:
- The ability to specify a commit ID to _diff against_, rather than only "the previous commit for this file"
- The ability to specify a commit ID to _view_, rather than the current version of the file
- Where the old lines are displayed in monochrome, highlight the differences in some way, similar to how [diff-so-fancy](https://github.com/so-fancy/diff-so-fancy) does:
We should add a "Integration with other tools" section to the README to document some of the ways in which `bat` can be combined with other tools:
- [ ] Use `bat` as a `--preview` program with `fzf`.
- [x] Execute `bat` on the search results of `fd`/`find` via `fd pattern -X bat`
- [x] Combine it with `git show` to view older versions of files: `git show v0.6.0:src/main.rs | bat -l rs`
- [x] Use it with `xclip` to copy a file to the console
- [x] Continuously monitor a growing file with `tail -f some-file.ext | bat -l ext --paging=never` with syntax highlighting.
Recently I needed a way to pretty-print some Rust code to the command-line while building [cargo-inspect](https://github.com/mre/cargo-inspect/).
I used syntect, but in a very crude way. It occured to me, that by using `bat` as a pretty-printer, I could piggy-back on what already exists and get features like line-numbers for free.
Probably other projects would want to do the same.
So I wonder if you considered providing a `lib.rs`, which would allow for using this crate as a library.
The `main.rs`, would then simply use the `lib.rs` as a dependency. That seems to be quite a common pattern. As an additional advantage, it would decouple the argument parsing from the rest of the code. Would that be possible?
Hello, thank you for your awesome works on `bat` ! But I think there is a feature that still missing.
Suppose that I just want to change the line number color, I have to make a copy of the theme file and change its `gutterForeground` value. And the theme file is verbose, normally 400+ lines.
So it will be great the `bat` can provide an argument to overwirte the theme color e.g. `bat --theme Tomorrow-Night --colors gutterForeground=f5f5f5 README.md`.
Providing a PPA would be an awesome way to gain more users. Personally I usually don't install a .deb alone, unless is sets up its own repository, such that I will get updates automatically.
I am not really sure if this is an issue or intended behaviour.
It took me forever to move to end of a 6Mb file.
Steps to reproduce:
- `$ seq 1 1000000 > test`
- `$ bat test`
Press `G` to move to end of the file.
This step took a long time. It seems `bat` was going through the file sequentially.
Apologies, if this is not the place to ask this question or this is a known bug/feature.
it would be nice to have `bat` as a regular debian package so that we can install it via `apt`.
First: congrats on the release, and props for creatively putting together the pieces that make this work!
Anyway: It'd be really neat if this could be used as an alternative to the default `pager` in Git -- this is REALLY nice-looking, and I'd love to use this as a pager. Would you be open to a PR or implementing yourself a feature to filter out everything that's not a hunk in a diff? I'm not sure if this should be a special way to process `diff`/`patch` files or just integrated with `libgit2` directly -- the latter is probably easier, since you're already using `libgit2` as a dependency.