tool

Describe the bug you encountered:

The options --map-syntax and --ignored-suffix cannot work together.

How to reproduce it:

1. Prepare a file foo.demo in YAML syntax:

   # file: foo.demo
   foo: "bar"

2. Use bat --map-syntax "*.demo:YAML" foo.demo can print it with YAML syntax highlighting:

   bat foo.demo \
       --map-syntax "

(As discussed in #885,) the current benchmark suite has a few shortcomings.

The most obvious one is that there is no standardized dataset. Past ideas involved using large Git repositories (Linux, Chromium, Rust compiler), but these repositories change over time. We can not simply check out a certain state because the .git folder will still grow. It'

It would be helpful to see the elapsed time on the initial time measurement.

Right now, I have a very long running benchmark subject sitting at "Initial time measurement" and "ETA 00:00:00"; I'd love to see the elapsed time ticking at least in this case, e.g. as " AT 00:10:23", indicating that hyperfine is 10 minutes 23 seconds into the initial run.

I tried a lot of ways，but it dosen't show any information in console. I don't know what's wrong.

import { times } from "lodash";
import React from "react";
import ReactDOM from "react-dom";
import whyDidYouRender from "@welldone-software/why-did-you-render";

if (process.env.NODE_ENV === 'development') {
  const whyDidYouRender = require('@welldone-software/why-did-you-rende

I think it would be interesting to try and maintain some level of compatibility with xxd. I recently came across this when following a blog post, trying to use hexyl instead of xxd.

• The most obvious thing would be to introduce (yet another) alias for --length/--bytes, i.e. -l in addition to -n and -c

Unless I missed something, the documentation doesn't explain how to query document metadata (searching "site:montferret.dev metadata" through Google returned nothing, neither did grepping the source code).

As an example, I tried to query the og:url metadata.
I tried variations of //meta[property='og:url']::attr(content), with or without the leading //, and with or without the `attr(conte

SUSE Security has requested an update to address CVE-2022-24713. Upstream commit.
Please take the time to adjust Cargo.lock and upgrade at least regex.

Thank you.

Related with nunomaduro/phpinsights#23 will be a great idea to allow set all commands parameters from config/insights.php when is used with php artisan insights.

Maybe something like:

'parameters' => '--format=json -d memo

Just came across this nice program, only to realize that it is missing many named colors:

$ pastel color red3
[pastel error]: Could not parse color 'red3'

Please see https://en.wikipedia.org/wiki/X11_color_names and https://cgit.freedesktop.org/xorg/app/rgb/tree/rgb.txt .

The few clashing color names could be resolved by using a x11- prefix like in x11-gray.

Description

Scrolling with a trackpad is way too fast.

What would you like to be added:

Please add some basic instructions for compiling the binaries to the install readme as an alternative to curl to bash.

Why is this needed:

Some folks are uncomfortable with the security implications of curl to bash

There are additional use cases where users may wish to modify the functionality of the project to better fit their needs

**Addit