Created
August 18, 2023 09:04
-
-
Save rvangsgaard/38f0a6065d2ef7e807f9f2df535c16ad to your computer and use it in GitHub Desktop.
Asciinema test
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{"version": 2, "width": 158, "height": 73, "timestamp": 1692348982, "idle_time_limit": 2.5, "env": {"SHELL": "/bin/bash", "TERM": "xterm-256color"}} | |
[0.042212, "o", "\u001b]777;notify;Command completed;ls\u001b\\\u001b]777;precmd\u001b\\\u001b]0;rva@fedora:/tmp\u001b\\"] | |
[0.04298, "o", "\u001b]7;file://fedora/tmp\u001b\\\u001b[?2004h"] | |
[0.043044, "o", "[rva@fedora tmp]$ "] | |
[29.83644, "o", "p"] | |
[29.923104, "o", "w"] | |
[29.980237, "o", "d"] | |
[30.179476, "o", "\r\n\u001b[?2004l\r\u001b]777;preexec\u001b\\/tmp\r\n"] | |
[30.183352, "o", "\u001b]777;notify;Command completed;pwd\u001b\\\u001b]777;precmd\u001b\\\u001b]0;rva@fedora:/tmp\u001b\\"] | |
[30.184907, "o", "\u001b]7;file://fedora/tmp\u001b\\"] | |
[30.184958, "o", "\u001b[?2004h[rva@fedora tmp]$ "] | |
[34.931375, "o", "m"] | |
[35.019439, "o", "a"] | |
[35.155761, "o", "n"] | |
[35.683496, "o", " "] | |
[35.851209, "o", "g"] | |
[35.931677, "o", "i"] | |
[36.035521, "o", "t"] | |
[36.202016, "o", "\r\n\u001b[?2004l\r"] | |
[36.202058, "o", "\u001b]777;preexec\u001b\\"] | |
[36.243338, "o", "\u001b[?1049h\u001b[22;0;0t\u001b[73;1H\u001b[?1h\u001b=\r"] | |
[36.257653, "o", "GIT(1) Git Manual GIT(1)\u001b[m\r\n\u001b[m\r\n\u001b[1mNAME\u001b[0m\u001b[m\r\n git - the stupid content tracker\u001b[m\r\n\u001b[m\r\n\u001b[1mSYNOPSIS\u001b[0m\u001b[m\r\n \u001b[4mgit\u001b[24m [-v | --version] [-h | --help] [-C <path>] [-c <name>=<value>]\u001b[m\r\n [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]\u001b[m\r\n [-p|--paginate|-P|--no-pager] [--no-replace-objects] [--bare]\u001b[m\r\n [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]\u001b[m\r\n [--config-env=<name>=<envvar>] <command> [<args>]\u001b[m\r\n\u001b[m\r\n\u001b[1mDESCRIPTION\u001b[0m\u001b[m\r\n Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full\u001b[m\r\n access to internals.\u001b[m\r\n\u001b[m\r\n See \u001b[1mgittutorial\u001b[22m(7) to get started, then see \u001b[1mgiteveryday\u001b[22m(7) for a useful minimum set of commands. The \u001b[34m\u001b[1mGit User’s Manual\u001b[0m\u001b[1m\u001b[22m[1] has a more in-depth\u001b[m\r\n introduction.\u001b[m\r\n\u001b[m\r\n After you mastered the basic concepts, you can come back to this page to learn what commands Git offers. You can learn more about individual Git\u001b[m\r\n commands with \"git help command\". \u001b[1mgitcli\u001b[22m(7) manual page gives you an overview of the command-line command syntax.\u001b[m\r\n\u001b[m\r\n A formatted and hyperlinked copy of the latest Git documentation can be viewed at \u001b[34m\u001b[1mhttps://git.github.io/htmldocs/git.html \u001b[0m\u001b[1m\u001b[22mor\u001b[m\r\n \u001b[34m\u001b[1mhttps://git-scm.com/docs\u001b[0m\u001b[1m\u001b[22m.\u001b[m\r\n\u001b[m\r\n\u001b[1mOPTIONS\u001b[0m\u001b[m\r\n -v, --version\u001b[m\r\n Prints the Git suite version that the \u001b[4mgit\u001b[24m program came from.\u001b[m\r\n\u001b[m\r\n This option is internally converted to \u001b[1mgit version ... \u001b[22mand accepts the same options as the \u001b[1mgit-version\u001b[22m(1) command. If \u001b[1m--help \u001b[22mis also given, it\u001b[m\r\n takes precedence over \u001b[1m--version\u001b[22m.\u001b[m\r\n\u001b[m\r\n -h, --help\u001b[m\r\n Prints the synopsis and a list of the most commonly used commands. If the option \u001b[1m--all \u001b[22mor \u001b[1m-a \u001b[22mis given then all available commands are printed.\u001b[m\r\n If a Git command is named this option will bring up the manual page for that command.\u001b[m\r\n\u001b[m\r\n Other options are available to control how the manual page is displayed. See \u001b[1mgit-help\u001b[22m(1) for more information, because \u001b[1mgit --help ... \u001b[22mis\u001b[m\r\n converted internally into \u001b[1mgit help ...\u001b[22m.\u001b[m\r\n\u001b[m\r\n -C <path>\u001b[m\r\n Run as if git was started in \u001b[4m<path>\u001b[24m instead of the current working directory. When multiple \u001b[1m-C \u001b[22moptions are given, each subsequent non-absolute\u001b[m\r\n \u001b[1m-C <path> \u001b[22mis interpreted relative to the preceding \u001b[1m-C <path>\u001b[22m. If \u001b[4m<path>\u001b[24m is present but empty, e.g. \u001b[1m-C \"\"\u001b[22m, then the current working directory\u001b[m\r\n is left unchanged.\u001b[m\r\n\u001b[m\r\n This option affects options that expect path name like \u001b[1m--git-dir \u001b[22mand \u001b[1m--work-tree \u001b[22min that their interpretations of the path names"] | |
[36.257796, "o", " would be made\u001b[m\r\n relative to the working directory caused by the \u001b[1m-C \u001b[22moption. For example the following invocations are equivalent:\u001b[m\r\n\u001b[m\r\n git --git-dir=a.git --work-tree=b -C c status\u001b[m\r\n git --git-dir=c/a.git --work-tree=c/b status\u001b[m\r\n\u001b[m\r\n -c <name>=<value>\u001b[m\r\n Pass a configuration parameter to the command. The value given will override values from configuration files. The <name> is expected in the\u001b[m\r\n same format as listed by \u001b[4mgit\u001b[24m \u001b[4mconfig\u001b[24m (subkeys separated by dots).\u001b[m\r\n\u001b[m\r\n Note that omitting the \u001b[1m= \u001b[22min \u001b[1mgit -c foo.bar ... \u001b[22mis allowed and sets \u001b[1mfoo.bar \u001b[22mto the boolean true value (just like \u001b[1m[foo]bar \u001b[22mwould in a config\u001b[m\r\n file). Including the equals but with an empty value (like \u001b[1mgit -c foo.bar= ...\u001b[22m) sets \u001b[1mfoo.bar \u001b[22mto the empty string which \u001b[1mgit config --type=bool\u001b[0m\u001b[m\r\n will convert to \u001b[1mfalse\u001b[22m.\u001b[m\r\n\u001b[m\r\n --config-env=<name>=<envvar>\u001b[m\r\n Like \u001b[1m-c <name>=<value>\u001b[22m, give configuration variable \u001b[4m<name>\u001b[24m a value, where <envvar> is the name of an environment variable from which to\u001b[m\r\n"] | |
[36.257964, "o", " retrieve the value. Unlike \u001b[1m-c \u001b[22mthere is no shortcut for directly setting the value to an empty string, instead the environment variable itself\u001b[m\r\n must be set to the empty string. It is an error if the \u001b[1m<envvar> \u001b[22mdoes not exist in the environment. \u001b[1m<envvar> \u001b[22mmay not contain an equals sign to\u001b[m\r\n avoid ambiguity with \u001b[1m<name> \u001b[22mcontaining one.\u001b[m\r\n\u001b[m\r\n This is useful for cases where you want to pass transitory configuration options to git, but are doing so on OS’s where other processes might\u001b[m\r\n be able to read your cmdline (e.g. \u001b[1m/proc/self/cmdline\u001b[22m), but not your environ (e.g. \u001b[1m/proc/self/environ\u001b[22m). That behavior is the default on\u001b[m\r\n Linux, but may not be on your system.\u001b[m\r\n\u001b[m\r\n Note that this might add security for variables such as \u001b[1mhttp.extraHeader \u001b[22mwhere the sensitive information is part of the value, but not e.g.\u001b[m\r\n \u001b[1murl.<base>.insteadOf \u001b[22mwhere the sensitive information can be part of the key.\u001b[m\r\n\u001b[m\r\n --exec-path[=<path>]\u001b[m\r\n\u001b[7m Manual page git(1) line 1 (press h for help or q to quit)\u001b[27m\u001b[K"] | |
[37.483834, "o", "\r\u001b[K \u001b[KESC\b\b\bESC\u001b[K[\b[\u001b[K6\b6\u001b[K~\b~\r\u001b[K"] | |
[37.483885, "o", " Path to wherever your core Git programs are installed. This can also be controlled by setting the GIT_EXEC_PATH environment variable. If no\u001b[m\r\n path is given, \u001b[4mgit\u001b[24m will print the current setting and then exit.\u001b[m\r\n\u001b[m\r\n --html-path\u001b[m\r\n Print the path, without trailing slash, where Git’s HTML documentation is installed and exit.\u001b[m\r\n\u001b[m\r\n --man-path\u001b[m\r\n Print the manpath (see \u001b[1mman(1)\u001b[22m) for the man pages for this version of Git and exit.\u001b[m\r\n\u001b[m\r\n --info-path\u001b[m\r\n Print the path where the Info files documenting this version of Git are installed and exit.\u001b[m\r\n\u001b[m\r\n -p, --paginate\u001b[m\r\n Pipe all output into \u001b[4mless\u001b[24m (or if set, $PAGER) if standard output is a terminal. This overrides the \u001b[1mpager.<cmd> \u001b[22mconfiguration options (see the\u001b[m\r\n \"Configuration Mechanism\" section below).\u001b[m\r\n\u001b[m\r\n -P, --no-pager\u001b[m\r\n Do not pipe Git output into a pager.\u001b[m\r\n\u001b[m\r\n --git-dir=<path>\u001b[m\r\n S"] | |
[37.484135, "o", "et the path to the repository (\".git\" directory). This can also be controlled by setting the \u001b[1mGIT_DIR \u001b[22menvironment variable. It can be an\u001b[m\r\n absolute path or relative path to current working directory.\u001b[m\r\n\u001b[m\r\n Specifying the location of the \".git\" directory using this option (or \u001b[1mGIT_DIR \u001b[22menvironment variable) turns off the repository discovery that\u001b[m\r\n tries to find a directory with \".git\" subdirectory (which is how the repository and the top-level of the working tree are discovered), and\u001b[m\r\n tells Git that you are at the top level of the working tree. If you are not at the top-level directory of the working tree, you should tell Git\u001b[m\r\n where the top-level of the working tree is, with the \u001b[1m--work-tree=<path> \u001b[22moption (or \u001b[1mGIT_WORK_TREE \u001b[22menvironment variable)\u001b[m\r\n\u001b[m\r\n If you just want to run git as if it was started in \u001b[1m<path> \u001b[22mthen use \u001b[1mgit -C <path>\u001b[22m.\u001b[m\r\n\u001b[m\r\n --work-tree=<path>\u001b[m\r\n Set the path to the working tree. It can be an absolute path or a path relative to the current working directory. This can also be controlled\u001b[m\r\n by setting the GIT_WORK_TREE environment variable and the core.worktree configuration variable (see core.worktree in \u001b[1mgit-config\u001b[22m(1) for a more\u001b[m\r\n detailed discussion).\u001b[m\r\n\u001b[m\r\n --namespace=<path>\u001b[m\r\n Set the Git namespace. See \u001b[1mgitnamespaces\u001b[22m(7) for more details. Equivalent to setting the \u001b[1mGIT_NAMESPACE \u001b[22menvironment variable.\u001b[m\r\n\u001b[m\r\n --bare\u001b[m\r\n Treat the repository as a bare repository. If GIT_DIR environment is not set, it is set to the current working directory.\u001b[m\r\n\u001b[m\r\n --no-replace-objects\u001b[m\r\n Do not use replacement refs to replace Git objects. See \u001b[1mgit-replace\u001b[22m(1) for more information.\u001b[m\r\n\u001b[m\r\n --literal-pathspecs\u001b[m\r\n Treat pathspecs literally (i.e. no globbing, no pathspec magic). This is equivalent to setting the \u001b[1mGIT_LITERAL_PATHSPECS \u001b[22menvironment v"] | |
[37.484386, "o", "ariable\u001b[m\r\n to \u001b[1m1\u001b[22m.\u001b[m\r\n\u001b[m\r\n --glob-pathspecs\u001b[m\r\n Add \"glob\" magic to all pathspec. This is equivalent to setting the \u001b[1mGIT_GLOB_PATHSPECS \u001b[22menvironment variable to \u001b[1m1\u001b[22m. Disabling globbing on\u001b[m\r\n individual pathspecs can be done using pathspec magic \":(literal)\"\u001b[m\r\n\u001b[m\r\n --noglob-pathspecs\u001b[m\r\n Add \"literal\" magic to all pathspec. This is equivalent to setting the \u001b[1mGIT_NOGLOB_PATHSPECS \u001b[22menvironment variable to \u001b[1m1\u001b[22m. Enabling globbing on\u001b[m\r\n individual pathspecs can be done using pathspec magic \":(glob)\"\u001b[m\r\n\u001b[m\r\n --icase-pathspecs\u001b[m\r\n Add \"icase\" magic to all pathspec. This is equivalent to setting the \u001b[1mGIT_ICASE_PATHSPECS \u001b[22menvironment variable to \u001b[1m1\u001b[22m.\u001b[m\r\n\u001b[m\r\n --no-optional-locks\u001b[m\r\n Do not perform optional operations that require locks. This is equivalent to setting the \u001b[1mGIT_OPTIONAL_LOCKS \u001b[22mto \u001b[1m0\u001b[22m.\u001b[m\r\n\u001b[m\r\n --list-cmds=group[,group...]\u001b[m\r\n List commands by group. This is an internal/experimental option and may chang"] | |
[37.484548, "o", "e or be removed in the future. Supported groups are: builtins,\u001b[m\r\n parseopt (builtin commands that use parse-options), main (all commands in libexec directory), others (all other commands in \u001b[1m$PATH \u001b[22mthat have\u001b[m\r\n git- prefix), list-<category> (see categories in command-list.txt), nohelpers (exclude helper commands), alias and config (retrieve command\u001b[m\r\n list from config variable completion.commands)\u001b[m\r\n\u001b[m\r\n --attr-source=<tree-ish>\u001b[m\r\n Read gitattributes from <tree-ish> instead of the worktree. See \u001b[1mgitattributes\u001b[22m(5). This is equivalent to setting the \u001b[1mGIT_ATTR_SOURCE \u001b[22menvironment\u001b[m\r\n variable.\u001b[m\r\n\u001b[m\r\n\u001b[7m Manual page git(1) line 73 (press h for help or q to quit)\u001b[27m\u001b[K"] | |
[41.731755, "o", "\r\u001b[K\u001b[?1l\u001b>\u001b[?1049l\u001b[23;0;0t"] | |
[41.738754, "o", "\u001b]777;notify;Command completed;man git\u001b\\\u001b]777;precmd\u001b\\\u001b]0;rva@fedora:/tmp\u001b\\"] | |
[41.740779, "o", "\u001b]7;file://fedora/tmp\u001b\\\u001b[?2004h[rva@fedora tmp]$ "] | |
[43.139987, "o", "\u001b[?2004l\r\r\nexit\r\n"] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment