NAME
bat — a cat(1) clone with syntax highlighting and Git integration.
USAGE
DESCRIPTION
bat prints the syntax-highlighted content of a collection of FILEs to the terminal. If no FILE is specified, or when FILE is ‘-‘, it reads from standard input.
bat supports a large number of programming and markup languages. It also communicates with git(1) to show modifications with respect to the git index. bat automatically pipes its output through a pager (by default: less).
Whenever the output of bat goes to a non-interactive terminal, i.e. when the output is piped into another process or into a file, bat will act as a drop-in replacement for cat(1) and fall back to printing the plain file contents.
OPTIONS
General remarks: Command-line options like ‘-l’/’—language’ that take values can be specified as either ‘—language value’, ‘—language=value’, ‘-l value’ or ‘-lvalue’.
Show non-printable characters like space, tab or newline. Use ‘—tabs’ to control the width of the tab-placeholders.
Specify how to display non-printable characters when using —show-all.
caret Use character sequences like ^G, ^J, ^@, .. to identify non-printable characters unicode Use special Unicode code points to identify non-printable characters
Only show plain style, no decorations. This is an alias for ‘—style=plain’. When ‘-p’ is used twice (‘-pp’), it also disables automatic paging (alias for ‘—style=plain —paging=never‘).
Explicitly set the language for syntax highlighting. The language can be specified as a name (like ‘C++’ or ‘LaTeX’) or possible file extension (like ‘cpp’, ‘hpp’ or ‘md’). Use ‘—list-languages’ to show all supported language names and file extensions.
-H, —highlight-line .
Highlight the specified line ranges with a different background color. For example:
—highlight-line 40 highlights line 40 —highlight-line 30:40 highlights lines 30 to 40 —highlight-line :40 highlights lines 1 to 40 —highlight-line 40: highlights lines 40 to the end of the file —highlight-line 30:+10 highlights lines 30 to 40
Specify the name to display for a file. Useful when piping data to bat from STDIN when bat does not otherwise know the filename. Note that the provided file name is also used for syntax detection.
Only show lines that have been added/removed/modified with respect to the Git index. Use ‘—diff-context=N’ to control how much context you want to see.
Include N lines of context around added/removed/modified lines when using ‘—diff’.
Set the tab width to T spaces. Use a width of 0 to pass tabs through directly
Specify the text-wrapping mode (*auto*, never, character). The ‘—terminal-width’ option can be used in addition to control the output width.
Explicitly set the width of the terminal instead of determining it automatically. If prefixed with ‘+’ or ‘-‘, the value will be treated as an offset to the actual terminal width. See also: ‘—wrap’.
Only show line numbers, no other decorations. This is an alias for ‘—style=numbers’
Specify when to use colored output. The automatic mode only enables colors if an interactive terminal is detected. Possible values: *auto*, never, always.
Specify when to use ANSI sequences for italic text in the output. Possible values: always, *never*.
Specify when to use the decorations that have been specified via ‘—style’. The automatic mode only enables decorations if an interactive terminal is detected. Possible values: *auto*, never, always.
-f, —force-colorization
Alias for ‘—decorations=always —color=always’. This is useful if the output of bat is piped to another program, but you want to keep the colorization/decorations.
Specify when to use the pager. To disable the pager, use ‘—paging=never’ or its alias, -P. To disable the pager permanently, set BAT_PAGER to an empty string. To control which pager is used, see the ‘—pager’ option. Possible values: *auto*, never, always.
Determine which pager is used. This option will override the PAGER and BAT_PAGER environment variables. The default pager is ‘less’. To control when the pager is used, see the ‘—paging’ option. Example: ‘—pager «less -RF«‘.
Note: By default, if the pager is set to ‘less’ (and no command-line options are specified), ‘bat’ will pass the following command line options to the pager: ‘-R’/’—RAW-CONTROL-CHARS’, ‘-F’/’—quit-if-one-screen’ and ‘-X’/’—no-init’. The last option (‘-X’) is only used for ‘less’ versions older than 530. The ‘-R’ option is needed to interpret ANSI colors correctly. The second option (‘-F’) instructs less to exit immediately if the output size is smaller than the vertical size of the terminal. This is convenient for small files because you do not have to press ‘q’ to quit the pager. The third option (‘-X’) is needed to fix a bug with the ‘—quit-if-one-screen’ feature in old versions of ‘less’. Unfortunately, it also breaks mouse-wheel support in ‘less’. If you want to enable mouse-wheel scrolling on older versions of ‘less’, you can pass just ‘-R’ (as in the example above, this will disable the quit-if-one-screen feature). For less 530 or newer, it should work out of the box.
Map a glob pattern to an existing syntax name. The glob pattern is matched on the full path and the filename. For example, to highlight *.build files with the Python syntax, use -m ‘*.build:Python’. To highlight files named ‘.myignore’ with the Git Ignore syntax, use -m ‘.myignore:Git Ignore’. Note that the right-hand side is the *name* of the syntax, not a file extension.
Set the theme for syntax highlighting. Use ‘—list-themes’ to see all available themes. To set a default theme, add the ‘—theme=». «‘ option to the configuration file or export the BAT_THEME environment variable (e.g.: export BAT_THEME=». «).
Display a list of supported themes for syntax highlighting.
Configure which elements (line numbers, file headers, grid borders, Git modifications, ..) to display in addition to the file contents. The argument is a comma-separated list of components to display (e.g. ‘numbers,changes,grid’) or a pre-defined style (‘full’). To set a default style, add the ‘—style=»..»‘ option to the configuration file or export the BAT_STYLE environment variable (e.g.: export BAT_STYLE=»..»). Possible values: *default*, full, auto, plain, changes, header, header-filename, header-filesize, grid, rule, numbers, snip.
Only print the specified range of lines for each file. For example:
—line-range 30:40 prints lines 30 to 40 —line-range :40 prints lines 1 to 40 —line-range 40: prints lines 40 to the end of the file —line-range 30:+10 prints lines 30 to 40
-L, —list-languages
Display a list of supported languages for syntax highlighting.
This option exists for POSIX-compliance reasons (‘u’ is for ‘unbuffered’). The output is always unbuffered — this option is simply ignored.
POSITIONAL ARGUMENTS
Files to print and concatenate. Use a dash (‘-‘) or no argument at all to read from standard input.
SUBCOMMANDS
cache — Modify the syntax-definition and theme cache.
FILES
bat can also be customized with a configuration file. The location of the file is dependent on your operating system. To get the default path for your system, call:
Alternatively, you can use the BAT_CONFIG_PATH environment variable to point bat to a non-default location of the configuration file.
To generate a default configuration file, call:
bat —generate-config-file
ADDING CUSTOM LANGUAGES
bat supports Sublime Text .sublime-syntax language files, and can be customized to add additional languages to your local installation. To do this, add the .sublime-syntax language files to `$(bat —config-dir)/syntaxes` and run `bat cache —build`.
# Put new ‘.sublime-syntax’ language definition files
# in this folder (or its subdirectories), for example:
git clone https://github.com/tellnobody1/sublime-purescript-syntax
# And then build the cache.
bat cache —build
Once the cache is built, the new language will be visible in `bat —list-languages`.
If you ever want to remove the custom languages, you can clear the cache with `bat cache —clear`.
ADDING CUSTOM THEMES
Similarly to custom languages, bat supports Sublime Text .tmTheme themes. These can be installed to `$(bat —config-dir)/themes`, and are added to the cache with `bat cache —build`.
MORE INFORMATION
For more information and up-to-date documentation, visit the bat repo:
https://github.com/sharkdp/bat
Package name: extra/bat Version: 0.23.0-3 Upstream: https://github.com/sharkdp/bat Licenses: APACHE, MIT Manuals: /listing/extra/bat/ Table of contents
Powered by archmanweb, using mandoc for the conversion of manual pages.
The website is available under the terms of the GPL-3.0 license, except for the contents of the manual pages, which have their own license specified in the corresponding Arch Linux package.
How do I create a batch file and run it? [duplicate]
Your question is more likely to receive useful answers if it contains some specifics. Such as what type of data is to be processed, including realistic examples of input and output.
@SergiyKolodyazhnyy The duplicate nominee is closed as too broad. As such the close vote on this one should be «too broad» as well. That said it seems like a reasonable question to me as I was once in the dark myself 🙂
@WinEunuuchs2Unix It is closed but does have an accepted answer, which will give OP what they want, or at least a starting point.
@EliahKagan If a mod agrees perhaps he can reopen that one and then merge the answers from here to there?
@WinEunuuchs2Unix That question, which this received close votes to be duped to, was actually reopened a few hours ago, then closed again as duplicate of that highly voted question. Both of them are listed as «originals» in the duplicate banner here (i.e., this question is duped to both of them). So if answers are to be merged, they’d probably be put there. Do you think that would be useful?
3 Answers 3
To create one use the .sh extension but it doesn’t really matter but it helps future users to quickly determine which file type it is. The bat name is mostly used on Windows but in Linux file name extensions do not really matter. Meaning I can call my file say run.de and it would still run in bash file but I believe it’s a good practice to name them with the .sh file extension.
For the editor, part uses any that is best for you between nano vim gedit emacs , but I believe gedit would be nice to start with.
Как создать пакетный файл и запустить его? [dубликат]
следует ли использовать текстовый редактор? расширение должно быть .sh или .bat?
6 ответов
Для создания одного используйте расширение .sh, но это не имеет особого значения, но оно помогает будущим пользователям быстро определить, какой тип файла он есть. Имя bat в основном используется в Windows, но в расширениях имен файлов Linux не имеет большого значения. Это означает, что я могу назвать свой файл say run.de, и он все равно будет работать в файле bash, но я считаю, что рекомендуется использовать их с расширением файла .sh.
Для редактора часть использует любое, что лучше для вас между nano vim gedit emacs, но я считаю, что gedit было бы неплохо начать с.
с использованием текстового редактора gedit: [ ! d3] Создать файл: gedit runme.sh Добавить код в файл: #!/bin/bash echo «Hello World!» Сделать исполняемым файл: chmod +x runme.sh Запустить файл с терминала: ./runme.sh
В linux это скрипты bash. Вы можете использовать большинство редакторов, и вы можете назвать это так, как хотите, Linux не использует расширения, такие как .sh или .bat или .exe для .doc для идентификации файлов, использует магию.
Возможно, gedit для графического редактора и nano из командной строки.
Избегайте текстовых процессоров, таких как libre office, поскольку они добавляют заголовки, которые вам не нужны.
http: //www.linfo. org / magic_number.html
Чтобы написать сценарий bash, запустите файл с помощью «SheBang» или #! / bin / bash
#!/bin/bash # comments start with a ‘#» command 1 command 2