Hi,

Thank you for a new release. I was looking into updating the package for NetBSD and realized the man page is provided in markdown. Would it possible to provide the man page in the man page Unix format, i.e. like hexyl.1 or hexyl.1.gz ? It would be desirable to avoid the need of external build dependencies for a simple man page.

TIA

I have some small binary masks, size 20x12 that I can display in my terminal using e.g hexdump:

❯ hexdump -v -e '20/1 " %02X" "\n"' mask_20x12.y
 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
 FF FF FF FF FF FF FF FF FF 00 00 00 FF FF FF FF FF FF FF FF
 FF FF FF FF FF FF FF FF FF 00 00 00 FF FF FF FF FF FF FF FF
 FF FF FF FF FF FF FF FF FF 00 00 00 FF FF FF FF FF FF FF FF
 FF FF FF FF FF FF FF FF 00 00 00 00 FF FF FF FF FF FF FF FF
 FF FF FF FF FF FF FF FF 00 00 00 00 FF FF FF FF FF FF FF FF
 FF FF FF FF FF FF FF FF 00 00 00 00 00 00 FF FF FF FF FF FF
 FF FF FF FF FF FF FF FF 00 00 00 00 00 00 00 FF FF FF FF FF
 FF FF FF FF FF FF FF 00 00 00 00 00 00 00 00 FF FF FF FF FF
 FF FF FF FF FF FF FF 00 00 00 00 00 00 00 00 FF FF FF FF FF

It would be wonderful if hexyl had the same capability.

Any shell completion is good.

Thanks!

Fixes #410.

Fixes #410.

New flags added:

OPTIONS:
    -p, --plain                 Display output with --no-chars, --no-position, and
                                --border=none.
    -C, --no-chars              Whether to display the character table on the right.
    -P, --no-position           Whether to display the position indicator on the left.

Motivation was mainly for diffing two separate binary files, borders could be removed but char table and position still created a lot of noise.

Output example:

Fixes #410.

Fixes #410.

Also changes try_arg() to return a Result instead of just a bool.

Also changes try_arg() to return a Result instead of just a bool.

Sorry for not using the official bug template, it always returned error code 400 on my end, and acted pretty buggy in general.

Bug description

I use a variant of the following line to find pdf files and sort them by date:

fd --strip-cwd-prefix -e pdf -X ls -t

--strip-cwd-prefix should remove the leading ./ string from the output (as per https://github.com/sharkdp/fd/pull/861). However, this string is still present in the output of fd in my interactive shell session, as well as in my shell scripts.

Expected behavior

fd should always remove the leading ./ when I invoke it with --strip-cwd-prefix.

Version information

$ fd --version
fd 8.3.0
$ uname -srm
Linux 5.15.5-arch1-1 x86_64
$ lsb-release -a
-e LSB Version:	1.4
-e Distributor ID:	Arch
-e Description:	Arch Linux
-e Release:	rolling
-e Codename:	n/a

if you need a large font (mine's currently set to 22, which isn't huge compared to some low vision folks) then the screencast is unreadable. See attached screenshot:

Windows 10 Version 1909 OS Build: 18363.1198

What version of bat are you using? bat 0.17.1

Describe the bug you encountered: tail | bat does not work on Windows 10.

Example: tail -f C:\app\oracle\diag\tnslsnr\DESKTOP-L5GI3V9\listener\trace\listener.log | bat --paging=never -l log

What did you expect to happen instead? tail should continue to function and tailed output should be piped to bat to show syntax highlighting.

How did you install bat? choco install bat

Proof of concept to aid discussion in #2185. I have not made up my mind yet if this change in sensible, but I think it helps to see it in person. Make sure to ignore whitespace changes when diffing.

IMO this problem is not a blocker to get the v0.21.0 release out since this is not a change in behaviour compared to v0.20.0.

The main use case for the old code seems to be that colored input across newlines should be handled correctly. If you try this:

echo "\x1B[33mColor\nColor \x1B[m\nPlain\n" | ./target/debug/bat

it looks like this with cat:

and the same with the latest release of bat, but with the code in this PR it looks like this instead:

since we reset colors when we encounter \n it seems. But IMHO we should just consider ANSI escape inputs as out-of-scope for bat, since syntax highlighting is broken when input contains ANSI escape characters anyway.

I have also confirmed that this change makes bat show bat-bug-test in #2185 the same way as cat.

IIUC in diff -d mode if I pass --tabs 0 it should display tabs as it is but in my terminals (iTerm2 and Terminal) its converting those to spaces. This (--tabs = 0) is also what delta uses to display tabs and it seems to have the same problem.

I can verify my file has tabs by using cat or bat -A as you can see in the attached image.

I know bat is printing spaces because if I copy the content of my terminal after bat prints it and past it into sublime text, I can see the spaces. Attached image for reference.

Proof of concept to aid discussion in #2185. I have not made up my mind yet if this change in sensible, but I think it helps to see it in person. Make sure to ignore whitespace changes when diffing.

IMO this problem is not a blocker to get the v0.21.0 release out since this is not a change in behaviour compared to v0.20.0.

The main use case for the old code seems to be that colored input across newlines should be handled correctly. If you try this:

echo "\x1B[33mColor\nColor \x1B[m\nPlain\n" | ./target/debug/bat

it looks like this with cat:

and the same with the latest release of bat, but with the code in this PR it looks like this instead:

since we reset colors when we encounter \n it seems. But IMHO we should just consider ANSI escape inputs as out-of-scope for bat, since syntax highlighting is broken when input contains ANSI escape characters anyway.

I have also confirmed that this change makes bat show bat-bug-test in #2185 the same way as cat.

Hi, Are you support an equivalent feature to zless (opening .gz file in plain text)? I tried using -A but the file is not human readable. Best,

Describe the bug you encountered:

I set --paging=always in my ~/.config/bat/config file. Then I can turn paging off by issuing the long option bat --paging=never. However neither bat -P or bat -pp work.

Note: this issue may affect also other short options, but I have tried only these ones.

What did you expect to happen instead?

Both bat -P and bat -pp should disable paging.

How did you install bat?

sudo pacman -S bat

bat version and environment

Software version

bat 0.20.0 (0655ecf2)

Operating system

Linux 5.16.15-arch1-1

Command-line

bat -P /home/luca/.config/bat/config --diagnostic

Environment variables

SHELL=/bin/bash
PAGER=<not set>
LESS=<not set>
LANG=en_US.utf8
LC_ALL=<not set>
BAT_PAGER=<not set>
BAT_CACHE_PATH=<not set>
BAT_CONFIG_PATH=<not set>
BAT_OPTS=<not set>
BAT_STYLE=<not set>
BAT_TABS=<not set>
BAT_THEME=<not set>
XDG_CONFIG_HOME=<not set>
XDG_CACHE_HOME=<not set>
COLORTERM=truecolor
NO_COLOR=<not set>
MANPAGER='sh -c '\''col -bx | bat -l man -p'\'''

Config file

# This is `bat`s configuration file. Each line either contains a comment or
# a command-line option that you want to pass to `bat` by default. You can
# run `bat --help` to get a list of all possible configuration options.

# Specify desired highlighting theme (e.g. "TwoDark"). Run `bat --list-themes`
# for a list of all available themes
--theme="OneHalfDark"

# Enable this to use italic text on the terminal. This is not supported on all
# terminal emulators (like tmux, by default):
--italic-text=always

# Uncomment the following line to disable automatic paging:
--paging=always

# Uncomment the following line if you are using less version >= 551 and want to
# enable mouse scrolling support in `bat` when running inside tmux. This might
# disable text selection, unless you press shift.
#--pager="less --RAW-CONTROL-CHARS --quit-if-one-screen --mouse"

# Syntax mappings: map a certain filename pattern to a language.
#   Example 1: use the C++ syntax for Arduino .ino files
#   Example 2: Use ".gitignore"-style highlighting for ".ignore" files
#--map-syntax "*.ino:C++"
#--map-syntax ".ignore:Git Ignore"

Compile time information

• Profile: release
• Target triple: x86_64-unknown-linux-gnu
• Family: unix
• OS: linux
• Architecture: x86_64
• Pointer width: 64
• Endian: little
• CPU features: fxsr,sse,sse2
• Host: x86_64-unknown-linux-gnu

Less version

> less --version
less 590 (PCRE2 regular expressions)
Copyright (C) 1984-2021  Mark Nudelman

less comes with NO WARRANTY, to the extent permitted by law.
For information about the terms of redistribution,
see the file named README in the less distribution.
Home page: https://greenwoodsoftware.com/less

When typing bat r<tab> no completion happens for files starting with capital R.

The problem in the case statement after the _arguments call in _bat_main https://github.com/sharkdp/bat/blob/9ab378b5dc7fa7835a27a641e51b5c362bf3bb00/assets/completions/bat.zsh.in#L58-L61

Can be "fixed" with disabling the case statement. But I don't know how to fix it properly to keep completion working for language, theme, style.

Maybe it's an intended behavior. In that case the issue report hopefully helps someone else with a workaround.