Title: | Helpers for Developing Command Line Interfaces |
---|---|
Description: | A suite of tools to build attractive command line interfaces ('CLIs'), from semantic elements: headings, lists, alerts, paragraphs, etc. Supports custom themes via a 'CSS'-like language. It also contains a number of lower level 'CLI' elements: rules, boxes, trees, and 'Unicode' symbols with 'ASCII' alternatives. It support ANSI colors and text styles as well. |
Authors: | Gábor Csárdi [aut, cre], Hadley Wickham [ctb], Kirill Müller [ctb], Salim Brüggemann [ctb] , Posit Software, PBC [cph, fnd] |
Maintainer: | Gábor Csárdi <[email protected]> |
License: | MIT + file LICENSE |
Version: | 3.6.3.9001 |
Built: | 2024-11-13 17:14:10 UTC |
Source: | https://github.com/r-lib/cli |
Align an ANSI colored string
ansi_align( text, width = console_width(), align = c("left", "center", "right"), type = "width" )
ansi_align( text, width = console_width(), align = c("left", "center", "right"), type = "width" )
text |
The character vector to align. |
width |
Width of the field to align in. |
align |
Whether to align |
type |
Passed on to |
str <- c( col_red("This is red"), style_bold("This is bold") ) astr <- ansi_align(str, width = 30) boxx(astr)
#> ┌────────────────────────────────────┐ #> │ │ #> │ This is red │ #> │ This is bold │ #> │ │ #> └────────────────────────────────────┘
str <- c( col_red("This is red"), style_bold("This is bold") ) astr <- ansi_align(str, align = "center", width = 30) boxx(astr)
#> ┌────────────────────────────────────┐ #> │ │ #> │ This is red │ #> │ This is bold │ #> │ │ #> └────────────────────────────────────┘
str <- c( col_red("This is red"), style_bold("This is bold") ) astr <- ansi_align(str, align = "right", width = 30) boxx(astr)
#> ┌────────────────────────────────────┐ #> │ │ #> │ This is red │ #> │ This is bold │ #> │ │ #> └────────────────────────────────────┘
The aligned character vector.
Other ANSI string operations:
ansi_columns()
,
ansi_nchar()
,
ansi_strsplit()
,
ansi_strtrim()
,
ansi_strwrap()
,
ansi_substr()
,
ansi_substring()
,
ansi_toupper()
,
ansi_trimws()
Features:
custom separator (sep
),
custom separator for length-two input (sep2
),
custom last separator (last
),
adds ellipsis to truncated strings,
uses Unicode ellipsis character on UTF-8 console,
can collapse "from both ends", with style = "both-ends"
,
can consider a limit for the display width of the result, in characters,
handles ANSI control sequences correctly when measuring display width.
ansi_collapse( x, sep = ", ", sep2 = sub("^,", "", last), last = ", and ", trunc = Inf, width = Inf, ellipsis = symbol$ellipsis, style = c("both-ends", "head") )
ansi_collapse( x, sep = ", ", sep2 = sub("^,", "", last), last = ", and ", trunc = Inf, width = Inf, ellipsis = symbol$ellipsis, style = c("both-ends", "head") )
x |
Character vector, or an object with an |
sep |
Separator. A character string. |
sep2 |
Separator for the special case that |
last |
Last separator, if there is no truncation. E.g. use
|
trunc |
Maximum number of elements to show. For |
width |
Limit for the display width of the result, in characters.
This is a hard limit, and the output will never exceed it.
This argument is not implemented for the |
ellipsis |
Character string to use at the place of the truncation. By default, the Unicode ellipsis character is used if the console is UTF-8, and three dots otherwise. |
style |
Truncation style:
|
Character scalar. It is NA_character_
if any elements in x
are NA
.
glue_collapse
in the glue package inspired this function.
ansi_collapse(letters) # truncate ansi_collapse(letters, trunc = 5) # head style ansi_collapse(letters, trunc = 5, style = "head")
ansi_collapse(letters) # truncate ansi_collapse(letters, trunc = 5) # head style ansi_collapse(letters, trunc = 5, style = "head")
This function helps with multi-column output of ANSI styles strings.
It works well together with boxx()
, see the example below.
ansi_columns( text, width = console_width(), sep = " ", fill = c("rows", "cols"), max_cols = 4, align = c("left", "center", "right"), type = "width", ellipsis = symbol$ellipsis )
ansi_columns( text, width = console_width(), sep = " ", fill = c("rows", "cols"), max_cols = 4, align = c("left", "center", "right"), type = "width", ellipsis = symbol$ellipsis )
text |
Character vector to format. Each element will formatted as a cell of a table. |
width |
Width of the screen. |
sep |
Separator between the columns. It may have ANSI styles. |
fill |
Whether to fill the columns row-wise or column-wise. |
max_cols |
Maximum number of columns to use. Will not use more, even if there is space for it. |
align |
Alignment within the columns. |
type |
Passed to |
ellipsis |
The string to append to truncated strings. Supply an empty string if you don't want a marker. |
If a string does not fit into the specified width
, it will be
truncated using ansi_strtrim()
.
fmt <- ansi_columns( paste(col_red("foo"), 1:10), width = 50, fill = "rows", max_cols=10, align = "center", sep = " " ) boxx(fmt, padding = c(0,1,0,1), header = col_cyan("Columns"))
#> ┌ Columns ───────────────────────────────────────────┐ #> │ foo 1 foo 2 foo 3 foo 4 foo 5 │ #> │ foo 6 foo 7 foo 8 foo 9 foo 10 │ #> └────────────────────────────────────────────────────┘
ANSI string vector.
Other ANSI string operations:
ansi_align()
,
ansi_nchar()
,
ansi_strsplit()
,
ansi_strtrim()
,
ansi_strwrap()
,
ansi_substr()
,
ansi_substring()
,
ansi_toupper()
,
ansi_trimws()
base::grep()
and base::grepl()
, but for ANSI stringsFirst ANSI sequences will be stripped with ansi_strip()
, both
ansi_grep(pattern, x, ignore.case = FALSE, perl = FALSE, value = FALSE, ...) ansi_grepl(pattern, x, ...)
ansi_grep(pattern, x, ignore.case = FALSE, perl = FALSE, value = FALSE, ...) ansi_grepl(pattern, x, ...)
pattern |
Character scalar, regular expression or fixed string
(if |
x |
Character vector to search in. Other objects will be coerced
using |
ignore.case , perl , value
|
Passed to |
... |
Extra arguments are passed to |
Note that these functions work on code points (or bytes if
useBytes = TRUE
), and not graphemes.
Unlike base::grep()
and base::grepl()
these functions do not special
case factors.
Both pattern
and x
are converted to UTF-8.
The same as base::grep()
and base::grepl()
, respectively.
red_needle <- col_red("needle") haystack <- c("foo", "needle", "foo") green_haystack <- col_green(haystack) ansi_grepl(red_needle, haystack) ansi_grepl(red_needle, green_haystack)
red_needle <- col_red("needle") haystack <- c("foo", "needle", "foo") green_haystack <- col_green(haystack) ansi_grepl(red_needle, haystack) ansi_grepl(red_needle, green_haystack)
Check if a string has some ANSI styling
ansi_has_any(string, sgr = TRUE, csi = TRUE, link = TRUE)
ansi_has_any(string, sgr = TRUE, csi = TRUE, link = TRUE)
string |
The string to check. It can also be a character vector. |
sgr |
Whether to look for SGR (styling) control sequences. |
csi |
Whether to look for non-SGR control sequences. |
link |
Whether to look for ANSI hyperlinks. |
Logical vector, TRUE
for the strings that have some
ANSI styling.
Other low level ANSI functions:
ansi_hide_cursor()
,
ansi_regex()
,
ansi_string()
,
ansi_strip()
## The second one has style if ANSI colors are supported ansi_has_any("foobar") ansi_has_any(col_red("foobar"))
## The second one has style if ANSI colors are supported ansi_has_any("foobar") ansi_has_any(col_red("foobar"))
This only works in terminal emulators. In other environments, it does nothing.
ansi_hide_cursor(stream = "auto") ansi_show_cursor(stream = "auto") ansi_with_hidden_cursor(expr, stream = "auto")
ansi_hide_cursor(stream = "auto") ansi_show_cursor(stream = "auto") ansi_with_hidden_cursor(expr, stream = "auto")
stream |
The stream to inspect or manipulate, an R connection
object. It can also be a string, one of |
expr |
R expression to evaluate. |
ansi_hide_cursor()
hides the cursor.
ansi_show_cursor()
shows the cursor.
ansi_with_hidden_cursor()
temporarily hides the cursor for
evaluating an expression.
Other terminal capabilities:
is_ansi_tty()
,
is_dynamic_tty()
Other low level ANSI functions:
ansi_has_any()
,
ansi_regex()
,
ansi_string()
,
ansi_strip()
Convert ANSI styled text to HTML
ansi_html(x, escape_reserved = TRUE, csi = c("drop", "keep"))
ansi_html(x, escape_reserved = TRUE, csi = c("drop", "keep"))
x |
Input character vector. |
escape_reserved |
Whether to escape characters that are reserved
in HTML ( |
csi |
What to do with non-SGR ANSI sequences, either |
Character vector of HTML.
Other ANSI to HTML conversion:
ansi_html_style()
## Syntax highlight the source code of an R function with ANSI tags, ## and export it to a HTML file. code <- withr::with_options( list(ansi.num_colors = 256), code_highlight(format(ansi_html)) ) hcode <- paste(ansi_html(code), collapse = "\n") css <- paste(format(ansi_html_style()), collapse= "\n") page <- htmltools::tagList( htmltools::tags$head(htmltools::tags$style(css)), htmltools::tags$pre(htmltools::HTML(hcode)) ) if (interactive()) htmltools::html_print(page)
## Syntax highlight the source code of an R function with ANSI tags, ## and export it to a HTML file. code <- withr::with_options( list(ansi.num_colors = 256), code_highlight(format(ansi_html)) ) hcode <- paste(ansi_html(code), collapse = "\n") css <- paste(format(ansi_html_style()), collapse= "\n") page <- htmltools::tagList( htmltools::tags$head(htmltools::tags$style(css)), htmltools::tags$pre(htmltools::HTML(hcode)) ) if (interactive()) htmltools::html_print(page)
ansi_html()
CSS styles for the output of ansi_html()
ansi_html_style( colors = TRUE, palette = c("vscode", "dichro", "vga", "winxp", "win10", "macos", "putty", "mirc", "xterm", "ubuntu", "eclipse", "iterm", "iterm-pastel", "iterm-smoooooth", "iterm-snazzy", "iterm-solarized", "iterm-tango") )
ansi_html_style( colors = TRUE, palette = c("vscode", "dichro", "vga", "winxp", "win10", "macos", "putty", "mirc", "xterm", "ubuntu", "eclipse", "iterm", "iterm-pastel", "iterm-smoooooth", "iterm-snazzy", "iterm-solarized", "iterm-tango") )
colors |
Whether or not to include colors. |
palette |
Character scalar, palette to use for the first eight colors plus their bright variants. Terminals define these colors differently, and cli includes a couple of examples. Sources of palettes:
|
Named list of CSS declaration blocks, where the names are
CSS selectors. It has a format()
and print()
methods, which you
can use to write the output to a CSS or HTML file.
Other ANSI to HTML conversion:
ansi_html()
ansi_html_style(colors = FALSE) ansi_html_style(colors = 8, palette = "iterm-snazzy")
ansi_html_style(colors = FALSE) ansi_html_style(colors = 8, palette = "iterm-snazzy")
This is a color-aware counterpart of utf8_nchar()
. By default it
counts Unicode grapheme clusters, instead of code points.
ansi_nchar(x, type = c("chars", "bytes", "width", "graphemes", "codepoints"))
ansi_nchar(x, type = c("chars", "bytes", "width", "graphemes", "codepoints"))
x |
Character vector, potentially ANSI styled, or a vector to be coerced to character. If it converted to UTF-8. |
type |
Whether to count graphemes (characters), code points, bytes, or calculate the display width of the string. |
Numeric vector, the length of the strings in the character vector.
Other ANSI string operations:
ansi_align()
,
ansi_columns()
,
ansi_strsplit()
,
ansi_strtrim()
,
ansi_strwrap()
,
ansi_substr()
,
ansi_substring()
,
ansi_toupper()
,
ansi_trimws()
str <- paste( col_red("red"), "default", col_green("green") ) cat(str, "\n") nchar(str) ansi_nchar(str) nchar(ansi_strip(str))
str <- paste( col_red("red"), "default", col_green("green") ) cat(str, "\n") nchar(str) ansi_nchar(str) nchar(ansi_strip(str))
base::nzchar()
, but for ANSI stringsLike base::nzchar()
, but for ANSI strings
ansi_nzchar(x, ...)
ansi_nzchar(x, ...)
x |
Charcater vector. Other objects are coarced using
|
... |
Passed to |
ansi_nzchar("") ansi_nzchar(col_red(""))
ansi_nzchar("") ansi_nzchar(col_red(""))
Don't forget to use perl = TRUE
when using this with grepl()
and
friends.
ansi_regex()
ansi_regex()
String scalar, the regular expression.
Other low level ANSI functions:
ansi_has_any()
,
ansi_hide_cursor()
,
ansi_string()
,
ansi_strip()
It creates an equivalent, but possibly shorter ANSI styled string, by removing duplicate and empty tags.
ansi_simplify(x, csi = c("keep", "drop"))
ansi_simplify(x, csi = c("keep", "drop"))
x |
Input string |
csi |
What to do with non-SGR ANSI sequences, either |
Simplified cli_ansi_string
vector.
This function sets the class of its argument, activating ANSI-string-specific methods such as for printing.
ansi_string(x)
ansi_string(x)
x |
A character vector or something that can be coerced into one. |
A cli_ansi_string
object, a subclass of
character
, with the same length and contents
as x
.
Other low level ANSI functions:
ansi_has_any()
,
ansi_hide_cursor()
,
ansi_regex()
,
ansi_strip()
The input may be of class cli_ansi_string
class, this is also dropped
from the result.
ansi_strip(string, sgr = TRUE, csi = TRUE, link = TRUE)
ansi_strip(string, sgr = TRUE, csi = TRUE, link = TRUE)
string |
The input string. |
sgr |
Whether to remove for SGR (styling) control sequences. |
csi |
Whether to remove for non-SGR control sequences. |
link |
Whether to remove ANSI hyperlinks. |
The cleaned up string. Note that ansi_strip()
always drops
the cli_ansi_string
class, even if sgr
and sciare
FALSE'.
Other low level ANSI functions:
ansi_has_any()
,
ansi_hide_cursor()
,
ansi_regex()
,
ansi_string()
ansi_strip(col_red("foobar")) == "foobar"
ansi_strip(col_red("foobar")) == "foobar"
This is the color-aware counterpart of base::strsplit()
.
It works almost exactly like the original, but keeps the colors in the
substrings.
ansi_strsplit(x, split, ...)
ansi_strsplit(x, split, ...)
x |
Character vector, potentially ANSI styled, or a vector to coerced to character. |
split |
Character vector of length 1 (or object which can be coerced to
such) containing regular expression(s) (unless |
... |
Extra arguments are passed to |
A list of the same length as x
, the i
-th element of
which contains the vector of splits of x[i]
. ANSI styles are
retained.
Other ANSI string operations:
ansi_align()
,
ansi_columns()
,
ansi_nchar()
,
ansi_strtrim()
,
ansi_strwrap()
,
ansi_substr()
,
ansi_substring()
,
ansi_toupper()
,
ansi_trimws()
str <- paste0( col_red("I am red---"), col_green("and I am green-"), style_underline("I underlined") ) cat(str, "\n") # split at dashes, keep color cat(ansi_strsplit(str, "[-]+")[[1]], sep = "\n") strsplit(ansi_strip(str), "[-]+") # split to characters, keep color cat(ansi_strsplit(str, "")[[1]], "\n", sep = " ") strsplit(ansi_strip(str), "")
str <- paste0( col_red("I am red---"), col_green("and I am green-"), style_underline("I underlined") ) cat(str, "\n") # split at dashes, keep color cat(ansi_strsplit(str, "[-]+")[[1]], sep = "\n") strsplit(ansi_strip(str), "[-]+") # split to characters, keep color cat(ansi_strsplit(str, "")[[1]], "\n", sep = " ") strsplit(ansi_strip(str), "")
This function is similar to base::strtrim()
, but works correctly with
ANSI styled strings. It also adds ...
(or the corresponding Unicode
character if Unicode characters are allowed) to the end of truncated
strings.
ansi_strtrim(x, width = console_width(), ellipsis = symbol$ellipsis)
ansi_strtrim(x, width = console_width(), ellipsis = symbol$ellipsis)
x |
Character vector of ANSI strings. |
width |
The width to truncate to. |
ellipsis |
The string to append to truncated strings. Supply an empty string if you don't want a marker. |
Note: ansi_strtrim()
does not support NA values currently.
Other ANSI string operations:
ansi_align()
,
ansi_columns()
,
ansi_nchar()
,
ansi_strsplit()
,
ansi_strwrap()
,
ansi_substr()
,
ansi_substring()
,
ansi_toupper()
,
ansi_trimws()
text <- cli::col_red(cli:::lorem_ipsum()) ansi_strtrim(c(text, "foobar"), 40)
text <- cli::col_red(cli:::lorem_ipsum()) ansi_strtrim(c(text, "foobar"), 40)
This function is similar to base::strwrap()
, but works on ANSI
styled strings, and leaves the styling intact.
ansi_strwrap( x, width = console_width(), indent = 0, exdent = 0, simplify = TRUE )
ansi_strwrap( x, width = console_width(), indent = 0, exdent = 0, simplify = TRUE )
x |
ANSI string. |
width |
Width to wrap to. |
indent |
Indentation of the first line of each paragraph. |
exdent |
Indentation of the subsequent lines of each paragraph. |
simplify |
Whether to return all wrapped strings in a single
character vector, or wrap each element of |
If simplify
is FALSE
, then a list of character vectors,
each an ANSI string. Otherwise a single ANSI string vector.
Other ANSI string operations:
ansi_align()
,
ansi_columns()
,
ansi_nchar()
,
ansi_strsplit()
,
ansi_strtrim()
,
ansi_substr()
,
ansi_substring()
,
ansi_toupper()
,
ansi_trimws()
text <- cli:::lorem_ipsum() # Highlight some words, that start with 's' rexp <- gregexpr("\\b([sS][a-zA-Z]+)\\b", text) regmatches(text, rexp) <- lapply(regmatches(text, rexp), col_red) cat(text) wrp <- ansi_strwrap(text, width = 40) cat(wrp, sep = "\n")
text <- cli:::lorem_ipsum() # Highlight some words, that start with 's' rexp <- gregexpr("\\b([sS][a-zA-Z]+)\\b", text) regmatches(text, rexp) <- lapply(regmatches(text, rexp), col_red) cat(text) wrp <- ansi_strwrap(text, width = 40) cat(wrp, sep = "\n")
This is a color-aware counterpart of base::substr()
.
It works exactly like the original, but keeps the colors
in the substrings. The ANSI escape sequences are ignored when
calculating the positions within the string.
ansi_substr(x, start, stop)
ansi_substr(x, start, stop)
x |
Character vector, potentially ANSI styled, or a vector to coerced to character. |
start |
Starting index or indices, recycled to match the length
of |
stop |
Ending index or indices, recycled to match the length
of |
Character vector of the same length as x
, containing
the requested substrings. ANSI styles are retained.
Other ANSI string operations:
ansi_align()
,
ansi_columns()
,
ansi_nchar()
,
ansi_strsplit()
,
ansi_strtrim()
,
ansi_strwrap()
,
ansi_substring()
,
ansi_toupper()
,
ansi_trimws()
str <- paste( col_red("red"), "default", col_green("green") ) cat(str, "\n") cat(ansi_substr(str, 1, 5), "\n") cat(ansi_substr(str, 1, 15), "\n") cat(ansi_substr(str, 3, 7), "\n") substr(ansi_strip(str), 1, 5) substr(ansi_strip(str), 1, 15) substr(ansi_strip(str), 3, 7) str2 <- paste( "another", col_red("multi-", style_underline("style")), "text" ) cat(str2, "\n") cat(ansi_substr(c(str, str2), c(3,5), c(7, 18)), sep = "\n") substr(ansi_strip(c(str, str2)), c(3,5), c(7, 18))
str <- paste( col_red("red"), "default", col_green("green") ) cat(str, "\n") cat(ansi_substr(str, 1, 5), "\n") cat(ansi_substr(str, 1, 15), "\n") cat(ansi_substr(str, 3, 7), "\n") substr(ansi_strip(str), 1, 5) substr(ansi_strip(str), 1, 15) substr(ansi_strip(str), 3, 7) str2 <- paste( "another", col_red("multi-", style_underline("style")), "text" ) cat(str2, "\n") cat(ansi_substr(c(str, str2), c(3,5), c(7, 18)), sep = "\n") substr(ansi_strip(c(str, str2)), c(3,5), c(7, 18))
This is the color-aware counterpart of base::substring()
.
It works exactly like the original, but keeps the colors in the
substrings. The ANSI escape sequences are ignored when
calculating the positions within the string.
ansi_substring(text, first, last = 1000000L)
ansi_substring(text, first, last = 1000000L)
text |
Character vector, potentially ANSI styled, or a vector to
coerced to character. It is recycled to the longest of |
first |
Starting index or indices, recycled to match the length
of |
last |
Ending index or indices, recycled to match the length
of |
Character vector of the same length as x
, containing
the requested substrings. ANSI styles are retained.
Other ANSI string operations:
ansi_align()
,
ansi_columns()
,
ansi_nchar()
,
ansi_strsplit()
,
ansi_strtrim()
,
ansi_strwrap()
,
ansi_substr()
,
ansi_toupper()
,
ansi_trimws()
str <- paste( col_red("red"), "default", col_green("green") ) cat(str, "\n") cat(ansi_substring(str, 1, 5), "\n") cat(ansi_substring(str, 1, 15), "\n") cat(ansi_substring(str, 3, 7), "\n") substring(ansi_strip(str), 1, 5) substring(ansi_strip(str), 1, 15) substring(ansi_strip(str), 3, 7) str2 <- paste( "another", col_red("multi-", style_underline("style")), "text" ) cat(str2, "\n") cat(ansi_substring(str2, c(3,5), c(7, 18)), sep = "\n") substring(ansi_strip(str2), c(3,5), c(7, 18))
str <- paste( col_red("red"), "default", col_green("green") ) cat(str, "\n") cat(ansi_substring(str, 1, 5), "\n") cat(ansi_substring(str, 1, 15), "\n") cat(ansi_substring(str, 3, 7), "\n") substring(ansi_strip(str), 1, 5) substring(ansi_strip(str), 1, 15) substring(ansi_strip(str), 3, 7) str2 <- paste( "another", col_red("multi-", style_underline("style")), "text" ) cat(str2, "\n") cat(ansi_substring(str2, c(3,5), c(7, 18)), sep = "\n") substring(ansi_strip(str2), c(3,5), c(7, 18))
There functions are similar to toupper()
, tolower()
and
chartr()
, but they keep the ANSI colors of the string.
ansi_toupper(x) ansi_tolower(x) ansi_chartr(old, new, x)
ansi_toupper(x) ansi_tolower(x) ansi_chartr(old, new, x)
x |
Input string. May have ANSI colors and styles. |
old |
a character string specifying the characters to be translated. If a character vector of length 2 or more is supplied, the first element is used with a warning. |
new |
a character string specifying the translations. If a character vector of length 2 or more is supplied, the first element is used with a warning. |
Character vector of the same length as x
, containing
the translated strings. ANSI styles are retained.
Other ANSI string operations:
ansi_align()
,
ansi_columns()
,
ansi_nchar()
,
ansi_strsplit()
,
ansi_strtrim()
,
ansi_strwrap()
,
ansi_substr()
,
ansi_substring()
,
ansi_trimws()
Other ANSI string operations:
ansi_align()
,
ansi_columns()
,
ansi_nchar()
,
ansi_strsplit()
,
ansi_strtrim()
,
ansi_strwrap()
,
ansi_substr()
,
ansi_substring()
,
ansi_trimws()
Other ANSI string operations:
ansi_align()
,
ansi_columns()
,
ansi_nchar()
,
ansi_strsplit()
,
ansi_strtrim()
,
ansi_strwrap()
,
ansi_substr()
,
ansi_substring()
,
ansi_trimws()
ansi_toupper(col_red("Uppercase")) ansi_tolower(col_red("LowerCase")) x <- paste0(col_green("MiXeD"), col_red(" cAsE 123")) ansi_chartr("iXs", "why", x)
ansi_toupper(col_red("Uppercase")) ansi_tolower(col_red("LowerCase")) x <- paste0(col_green("MiXeD"), col_red(" cAsE 123")) ansi_chartr("iXs", "why", x)
This function is similar to base::trimws()
but works on ANSI strings,
and keeps color and other styling.
ansi_trimws(x, which = c("both", "left", "right"))
ansi_trimws(x, which = c("both", "left", "right"))
x |
ANSI string vector. |
which |
Whether to remove leading or trailing whitespace or both. |
ANSI string, with the whitespace removed.
Other ANSI string operations:
ansi_align()
,
ansi_columns()
,
ansi_nchar()
,
ansi_strsplit()
,
ansi_strtrim()
,
ansi_strwrap()
,
ansi_substr()
,
ansi_substring()
,
ansi_toupper()
trimws(paste0(" ", col_red("I am red"), " ")) ansi_trimws(paste0(" ", col_red("I am red"), " ")) trimws(col_red(" I am red ")) ansi_trimws(col_red(" I am red "))
trimws(paste0(" ", col_red("I am red"), " ")) ansi_trimws(paste0(" ", col_red("I am red"), " ")) trimws(col_red(" I am red ")) ansi_trimws(col_red(" I am red "))
cli has a number of functions to color and style text at the command line. They provide a more modern interface than the crayon package.
bg_black(...) bg_blue(...) bg_cyan(...) bg_green(...) bg_magenta(...) bg_red(...) bg_white(...) bg_yellow(...) bg_none(...) bg_br_black(...) bg_br_blue(...) bg_br_cyan(...) bg_br_green(...) bg_br_magenta(...) bg_br_red(...) bg_br_white(...) bg_br_yellow(...) col_black(...) col_blue(...) col_cyan(...) col_green(...) col_magenta(...) col_red(...) col_white(...) col_yellow(...) col_grey(...) col_silver(...) col_none(...) col_br_black(...) col_br_blue(...) col_br_cyan(...) col_br_green(...) col_br_magenta(...) col_br_red(...) col_br_white(...) col_br_yellow(...) style_dim(...) style_blurred(...) style_bold(...) style_hidden(...) style_inverse(...) style_italic(...) style_reset(...) style_strikethrough(...) style_underline(...) style_no_bold(...) style_no_blurred(...) style_no_dim(...) style_no_italic(...) style_no_underline(...) style_no_inverse(...) style_no_hidden(...) style_no_strikethrough(...) style_no_color(...) style_no_bg_color(...)
bg_black(...) bg_blue(...) bg_cyan(...) bg_green(...) bg_magenta(...) bg_red(...) bg_white(...) bg_yellow(...) bg_none(...) bg_br_black(...) bg_br_blue(...) bg_br_cyan(...) bg_br_green(...) bg_br_magenta(...) bg_br_red(...) bg_br_white(...) bg_br_yellow(...) col_black(...) col_blue(...) col_cyan(...) col_green(...) col_magenta(...) col_red(...) col_white(...) col_yellow(...) col_grey(...) col_silver(...) col_none(...) col_br_black(...) col_br_blue(...) col_br_cyan(...) col_br_green(...) col_br_magenta(...) col_br_red(...) col_br_white(...) col_br_yellow(...) style_dim(...) style_blurred(...) style_bold(...) style_hidden(...) style_inverse(...) style_italic(...) style_reset(...) style_strikethrough(...) style_underline(...) style_no_bold(...) style_no_blurred(...) style_no_dim(...) style_no_italic(...) style_no_underline(...) style_no_inverse(...) style_no_hidden(...) style_no_strikethrough(...) style_no_color(...) style_no_bg_color(...)
... |
Character strings, they will be pasted together with
|
The col_*
functions change the (foreground) color to the text.
These are the eight original ANSI colors. Note that in some terminals,
they might actually look differently, as terminals have their own
settings for how to show them. col_none()
is the default color, this
is useful in a substring of a colored string.
The col_br_*
functions are bright versions of the eight ANSI colors.
Note that on some terminal configurations and themes they might be the
same as the non-bright colors.
The bg_*
functions change the background color of the text.
These are the eight original ANSI background colors. These, too, can
vary in appearance, depending on terminal settings. bg_none()
the
the default background color, this is useful in a substring of a
background-colored string.
The bg_br_*
functions are the bright versions of the eight ANSI
background colors. Note that on some terminal configurations and themes
they might be the same as the non-bright colors.
The style_*
functions apply other styling to the text. The currently
supported styling functions are:
style_reset()
to remove any style, including color,
style_bold()
for boldface / strong text, although some terminals
show a bright, high intensity text instead,
style_dim()
(or style_blurred()
reduced intensity text.
style_italic()
(not widely supported).
style_underline()
,
style_inverse()
,
style_hidden()
,
style_strikethrough()
(not widely supported).
The style functions take any number of character vectors as arguments,
and they concatenate them using paste0()
before adding the style.
Styles can also be nested, and then inner style takes precedence, see examples below.
Sometimes you want to revert back to the default text color, in the
middle of colored text, or you want to have a normal font in the middle
of italic text. You can use the style_no_*
functions for this. Every
style_*()
function has a style_no_*()
pair, which defends its
argument from taking on the style. See examples below.
An ANSI string (class cli_ansi_string
), that contains ANSI
sequences, if the current platform supports them. You can simply
use cat()
to print them to the terminal.
Other ANSI styling:
combine_ansi_styles()
,
make_ansi_style()
,
num_ansi_colors()
col_blue("Hello ", "world!") cat(col_blue("Hello ", "world!")) cat("... to highlight the", col_red("search term"), "in a block of text\n") ## Style stack properly cat(col_green( "I am a green line ", col_blue(style_underline(style_bold("with a blue substring"))), " that becomes green again!" )) error <- combine_ansi_styles("red", "bold") warn <- combine_ansi_styles("magenta", "underline") note <- col_cyan cat(error("Error: subscript out of bounds!\n")) cat(warn("Warning: shorter argument was recycled.\n")) cat(note("Note: no such directory.\n")) # style_no_* functions, note that the color is not removed style_italic(col_green(paste0( "italic before, ", style_no_italic("normal here, "), "italic after" ))) # avoiding color for substring style_italic(col_red(paste( "red before", col_none("not red between"), "red after" )))
col_blue("Hello ", "world!") cat(col_blue("Hello ", "world!")) cat("... to highlight the", col_red("search term"), "in a block of text\n") ## Style stack properly cat(col_green( "I am a green line ", col_blue(style_underline(style_bold("with a blue substring"))), " that becomes green again!" )) error <- combine_ansi_styles("red", "bold") warn <- combine_ansi_styles("magenta", "underline") note <- col_cyan cat(error("Error: subscript out of bounds!\n")) cat(warn("Warning: shorter argument was recycled.\n")) cat(note("Note: no such directory.\n")) # style_no_* functions, note that the color is not removed style_italic(col_green(paste0( "italic before, ", style_no_italic("normal here, "), "italic after" ))) # avoiding color for substring style_italic(col_red(paste( "red before", col_none("not red between"), "red after" )))
This theme is always active, and it is at the bottom of the theme stack. See themes.
builtin_theme(dark = getOption("cli.theme_dark", "auto"))
builtin_theme(dark = getOption("cli.theme_dark", "auto"))
dark |
Whether to use a dark theme. The |
A named list, a CLI theme.
cli_h1("Heading 1") cli_h2("Heading 2") cli_h3("Heading 3") cli_par() cli_alert_danger("Danger alert") cli_alert_warning("Warning alert") cli_alert_info("Info alert") cli_alert_success("Success alert") cli_alert("Alert for starting a process or computation", class = "alert-start") cli_end() cli_text("Packages and versions: {.pkg cli} {.version 1.0.0}.") cli_text("Time intervals: {.timestamp 3.4s}") cli_text("{.emph Emphasis} and {.strong strong emphasis}") cli_text("This is a piece of code: {.code sum(x) / length(x)}") cli_text("Function names: {.fn cli::simple_theme}") cli_text("Files: {.file /usr/bin/env}") cli_text("URLs: {.url https://r-project.org}") cli_h2("Longer code chunk") cli_par(class = "code R") cli_verbatim( '# window functions are useful for grouped mutates', 'mtcars %>%', ' group_by(cyl) %>%', ' mutate(rank = min_rank(desc(mpg)))')
#> ── Heading 1 ───────────────────────────────────────────────────────── #> #> ── Heading 2 ── #> #> ── Heading 3 #> ✖ Danger alert #> ! Warning alert #> ℹ Info alert #> ✔ Success alert #> → Alert for starting a process or computation #> #> Packages and versions: cli 1.0.0. #> Time intervals: [3.4s] #> Emphasis and strong emphasis #> This is a piece of code: `sum(x) / length(x)` #> Function names: `cli::simple_theme()` #> Files: /usr/bin/env #> URLs: <https://r-project.org> #> #> ── Longer code chunk ── #> #> # window functions are useful for grouped mutates #> mtcars %>% #> group_by(cyl) %>% #> mutate(rank = min_rank(desc(mpg)))
cat()
helpersThese helpers provide useful wrappers around cat()
: most importantly
they all set sep = ""
, and cat_line()
automatically adds a newline.
cat_line(..., col = NULL, background_col = NULL, file = stdout()) cat_bullet( ..., col = NULL, background_col = NULL, bullet = "bullet", bullet_col = NULL, file = stdout() ) cat_boxx(..., file = stdout()) cat_rule(..., file = stdout()) cat_print(x, file = "")
cat_line(..., col = NULL, background_col = NULL, file = stdout()) cat_bullet( ..., col = NULL, background_col = NULL, bullet = "bullet", bullet_col = NULL, file = stdout() ) cat_boxx(..., file = stdout()) cat_rule(..., file = stdout()) cat_print(x, file = "")
... |
For |
col , background_col , bullet_col
|
Colors for text, background, and bullets respectively. |
file |
Output destination. Defaults to standard output. |
bullet |
Name of bullet character. Indexes into symbol |
x |
An object to print. |
cat_line("This is ", "a ", "line of text.", col = "red") cat_bullet(letters[1:5]) cat_bullet(letters[1:5], bullet = "tick", bullet_col = "green") cat_rule()
cat_line("This is ", "a ", "line of text.", col = "red") cat_bullet(letters[1:5]) cat_bullet(letters[1:5], bullet = "tick", bullet_col = "green") cat_rule()
cli()
will record all cli_*
calls in expr
, and emit them together
in a single message. This is useful if you want to built a larger
piece of output from multiple cli_*
calls.
cli(expr)
cli(expr)
expr |
Expression that contains |
Use this function to build a more complex piece of CLI that would not make sense to show in pieces.
cli({ cli_h1("Title") cli_h2("Subtitle") cli_ul(c("this", "that", "end")) })
#> #> ── Title ───────────────────────────────────────────────────────────── #> #> ── Subtitle ── #> #> • this #> • that #> • end
Nothing.
These functions let you create error, warning or diagnostic messages with cli formatting, including inline styling, pluralization and glue substitutions.
cli_abort( message, ..., call = .envir, .envir = parent.frame(), .frame = .envir ) cli_warn(message, ..., .envir = parent.frame()) cli_inform(message, ..., .envir = parent.frame())
cli_abort( message, ..., call = .envir, .envir = parent.frame(), .frame = .envir ) cli_warn(message, ..., .envir = parent.frame()) cli_inform(message, ..., .envir = parent.frame())
message |
It is formatted via a call to |
... |
Passed to |
call |
The execution environment of a currently running
function, e.g. You only need to supply Can also be For more information about error calls, see Including function calls in error messages. |
.envir |
Environment to evaluate the glue expressions in. |
.frame |
The throwing context. Used as default for
|
n <- "boo" cli_abort(c( "{.var n} must be a numeric vector", "x" = "You've supplied a {.cls {class(n)}} vector." ))
#> Error: #> ! `n` must be a numeric vector #> ✖ You've supplied a <character> vector. #> Run `rlang::last_error()` to see where the error occurred.
len <- 26 idx <- 100 cli_abort(c( "Must index an existing element:", "i" = "There {?is/are} {len} element{?s}.", "x" = "You've tried to subset element {idx}." ))
#> Error: #> ! Must index an existing element: #> ℹ There are 26 elements. #> ✖ You've tried to subset element 100. #> Run `rlang::last_error()` to see where the error occurred.
These functions support inline markup.
Other functions supporting inline markup:
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
Alerts are typically short status messages.
cli_alert(text, id = NULL, class = NULL, wrap = FALSE, .envir = parent.frame()) cli_alert_success( text, id = NULL, class = NULL, wrap = FALSE, .envir = parent.frame() ) cli_alert_danger( text, id = NULL, class = NULL, wrap = FALSE, .envir = parent.frame() ) cli_alert_warning( text, id = NULL, class = NULL, wrap = FALSE, .envir = parent.frame() ) cli_alert_info( text, id = NULL, class = NULL, wrap = FALSE, .envir = parent.frame() )
cli_alert(text, id = NULL, class = NULL, wrap = FALSE, .envir = parent.frame()) cli_alert_success( text, id = NULL, class = NULL, wrap = FALSE, .envir = parent.frame() ) cli_alert_danger( text, id = NULL, class = NULL, wrap = FALSE, .envir = parent.frame() ) cli_alert_warning( text, id = NULL, class = NULL, wrap = FALSE, .envir = parent.frame() ) cli_alert_info( text, id = NULL, class = NULL, wrap = FALSE, .envir = parent.frame() )
text |
Text of the alert. |
id |
Id of the alert element. Can be used in themes. |
class |
Class of the alert element. Can be used in themes. |
wrap |
Whether to auto-wrap the text of the alert. |
.envir |
Environment to evaluate the glue expressions in. |
nbld <- 11 tbld <- prettyunits::pretty_sec(5.6) cli_alert_success("Built {.emph {nbld}} status report{?s} in {tbld}.")
#> ✔ Built 11 status reports in 5.6s.
cfl <- "~/.cache/files/latest.cache" cli_alert_info("Updating cache file {.path {cfl}}.")
#> ℹ Updating cache file ~/.cache/files/latest.cache.
cfl <- "~/.cache/files/latest.cache" cli_alert_warning("Failed to update cache file {.path {cfl}}.")
#> ! Failed to update cache file ~/.cache/files/latest.cache.
cfl <- "~/.config/report.yaml" cli_alert_danger("Cannot validate config file at {.path {cfl}}.")
#> ✖ Cannot validate config file at ~/.config/report.yaml.
Alerts are printed without wrapping, unless you set wrap = TRUE
:
cli_alert_info("Data columns: {.val {names(mtcars)}}.") cli_alert_info("Data columns: {.val {names(mtcars)}}.", wrap = TRUE)
#> ℹ Data columns: "mpg", "cyl", "disp", "hp", "drat", "wt", "qsec", "vs", "am", "g #> ear", and "carb". #> ℹ Data columns: "mpg", "cyl", "disp", "hp", "drat", "wt", "qsec", #> "vs", "am", "gear", and "carb".
These functions supports inline markup.
Other functions supporting inline markup:
cli_abort()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
A section that is quoted from another source. It is typically indented.
cli_blockquote( quote, citation = NULL, id = NULL, class = NULL, .envir = parent.frame() )
cli_blockquote( quote, citation = NULL, id = NULL, class = NULL, .envir = parent.frame() )
quote |
Text of the quotation. |
citation |
Source of the quotation, typically a link or the name of a person. |
id |
Element id, a string. If |
class |
Class name, sting. Can be used in themes. |
.envir |
Environment to evaluate the glue expressions in. It is
also used to auto-close the container if |
evil <- paste( "The real problem is that programmers have spent far too much time", "worrying about efficiency in the wrong places and at the wrong", "times; premature optimization is the root of all evil (or at least", "most of it) in programming.") cli_blockquote(evil, citation = "Donald Ervin Knuth")
#> #> “The real problem is that programmers have spent far #> too much time worrying about efficiency in the wrong #> places and at the wrong times; premature optimization #> is the root of all evil (or at least most of it) in #> programming.” #> — Donald Ervin Knuth #>
This function supports inline markup.
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
It is often useful to print out a list of items, tasks a function or package performs, or a list of notes.
cli_bullets(text, id = NULL, class = NULL, .envir = parent.frame())
cli_bullets(text, id = NULL, class = NULL, .envir = parent.frame())
text |
Character vector of items. See details below on how names are interpreted. |
id |
Optional id of the |
class |
Optional additional class(es) for the |
.envir |
Environment to evaluate the glue expressions in. |
Items may be formatted differently, e.g. they can have a prefix symbol.
Formatting is specified by the names of text
, and can be themed.
cli creates a div
element of class bullets
for the whole bullet list.
Each item is another div
element of class bullet-<name>
, where
<name>
is the name of the entry in text
. Entries in text
without
a name create a div
element of class bullet-empty
, and if the
name is a single space character, the class is bullet-space
.
The built-in theme defines the following item types:
No name: Item without a prefix.
: Indented item.
*
: Item with a bullet.
>
: Item with an arrow or pointer.
v
: Item with a green "tick" symbol, like cli_alert_success()
.
x
: Item with a ref cross, like cli_alert_danger()
.
!
: Item with a yellow exclamation mark, like cli_alert_warning()
.
i
: Info item, like cli_alert_info()
.
You can define new item type by simply defining theming for the
corresponding bullet-<name>
classes.
cli_bullets(c( "noindent", " " = "indent", "*" = "bullet", ">" = "arrow", "v" = "success", "x" = "danger", "!" = "warning", "i" = "info" ))
#> noindent #> indent #> • bullet #> → arrow #> ✔ success #> ✖ danger #> ! warning #> ℹ info
This function supports inline markup.
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
cli_format_bullets_raw()
is similar to cli_bullets()
, but it does
not perform any inline styling or glue substitutions in the input.
cli_bullets_raw(text, id = NULL, class = NULL) format_bullets_raw(text, id = NULL, class = NULL)
cli_bullets_raw(text, id = NULL, class = NULL) format_bullets_raw(text, id = NULL, class = NULL)
text |
Character vector of items. See details below on how names are interpreted. |
id |
Optional id of the |
class |
Optional additional class(es) for the |
format_bullets_raw()
returns the output instead of printing it.
These functions support inline markup.
See cli_bullets()
for examples.
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
A helper function that creates a div
with class code
and then calls
cli_verbatim()
to output code lines. The builtin theme formats these
containers specially. In particular, it adds syntax highlighting to
valid R code.
cli_code( lines = NULL, ..., language = "R", .auto_close = TRUE, .envir = environment() )
cli_code( lines = NULL, ..., language = "R", .auto_close = TRUE, .envir = environment() )
lines |
Character vector, each line will be a line of code, and newline characters also create new lines. Note that no glue substitution is performed on the code. |
... |
More character vectors, they are appended to |
language |
Programming language. This is also added as a class,
in addition to |
.auto_close |
Passed to |
.envir |
Passed to |
myfun <- function() { message("Just an example function") graphics::pairs(iris, col = 1:4) } cli_code(format(myfun))
#> function () #> { #> message("Just an example function") #> graphics::pairs(iris, col = 1:4) #> }
The id of the container that contains the code.
Return the current state of a cli app. It includes the currently open tags, their ids, classes and their computed styles.
cli_debug_doc(app = default_app() %||% start_app())
cli_debug_doc(app = default_app() %||% start_app())
app |
The cli app to debug. Defaults to the current app.
if there is no app, then it creates one by calling |
The returned data frame has a print method, and if you want to create
a plain data frame from it, index it with an empty bracket:
cli_debug_doc()[]
.
To see all currently active themes, use app$themes
, e.g. for the
default app: default_app()$themes
.
Data frame with columns: tag
, id
, class
(space separated),
theme (id of the theme the element added), styles
(computed styles
for the element).
cli_sitrep()
. To debug containers, you can set the
CLI-DEBUG_BAD_END
environment variable to true
, and then cli will
warn when it cannot find the specified container to close (or any
contained at all).
## Not run: cli_debug_doc() olid <- cli_ol() cli_li() cli_debug_doc() cli_debug_doc()[] cli_end(olid) cli_debug_doc() ## End(Not run)
## Not run: cli_debug_doc() olid <- cli_ol() cli_li() cli_debug_doc() cli_debug_doc()[] cli_end(olid) cli_debug_doc() ## End(Not run)
See containers. A cli_div
container is special, because it may
add new themes, that are valid within the container.
cli_div( id = NULL, class = NULL, theme = NULL, .auto_close = TRUE, .envir = parent.frame() )
cli_div( id = NULL, class = NULL, theme = NULL, .auto_close = TRUE, .envir = parent.frame() )
id |
Element id, a string. If |
class |
Class name, sting. Can be used in themes. |
theme |
A custom theme for the container. See themes. |
.auto_close |
Whether to close the container, when the calling
function finishes (or |
.envir |
Environment to evaluate the glue expressions in. It is
also used to auto-close the container if |
d <- cli_div(theme = list(h1 = list(color = "cyan", "font-weight" = "bold"))) cli_h1("Custom title") cli_end(d)
#>
#> Custom title
By default a cli_div()
is closed automatically when the calling
frame exits.
div <- function() { cli_div(class = "tmp", theme = list(.tmp = list(color = "yellow"))) cli_text("This is yellow") } div() cli_text("This is not yellow any more")
#> This is yellow
#> This is not yellow any more
The id of the new container element, invisibly.
A definition list is a container, see containers.
cli_dl( items = NULL, labels = names(items), id = NULL, class = NULL, .close = TRUE, .auto_close = TRUE, .envir = parent.frame() )
cli_dl( items = NULL, labels = names(items), id = NULL, class = NULL, .close = TRUE, .auto_close = TRUE, .envir = parent.frame() )
items |
Named character vector, or |
labels |
Item labels. Defaults the names in |
id |
Id of the list container. Can be used for closing it with
|
class |
Class of the list container. Can be used in themes. |
.close |
Whether to close the list container if the |
.auto_close |
Whether to close the container, when the calling
function finishes (or |
.envir |
Environment to evaluate the glue expressions in. It is
also used to auto-close the container if |
fun <- function() { cli_dl(c(foo = "one", bar = "two", baz = "three")) } fun()
#> foo: one #> bar: two #> baz: three
fun <- function() { cli_dl() cli_li(c(foo = "{.emph one}")) cli_li(c(bar = "two")) cli_li(c(baz = "three")) } fun()
#> foo: one
#> bar: two
#> baz: three
The id of the new container element, invisibly.
This function supports inline markup.
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
Containers aut0-close by default, but sometimes you need to explicitly close them. Closing a container also closes all of its nested containers.
cli_end(id = NULL)
cli_end(id = NULL)
id |
Id of the container to close. If missing, the current container is closed, if any. |
cnt <- cli_par() cli_text("First paragraph.") cli_end(cnt) cnt <- cli_par() cli_text("Second paragraph.") cli_end(cnt)
#> First paragraph. #> #> Second paragraph. #>
list <- cli_ul() cli_li("Item one:") cli_li("Item two:") cli_par() cli_text("Still item two.") cli_end(list) cli_text("Not in the list any more")
#> • Item one: #> • Item two: #> Still item two. #> #> Not in the list any more
id
If id
is omitted, the container that was opened last will be closed.
cli_par() cli_text("First paragraph") cli_end() cli_par() cli_text("Second paragraph") cli_end()
#> First paragraph #> #> Second paragraph #>
You can use the internal cli:::cli_debug_doc()
function to see the
currently open containers.
fun <- function() { cli_div(id = "mydiv") cli_par(class = "myclass") cli:::cli_debug_doc() } fun()
#> <cli document> #> <body id="body"> #> <div id="mydiv"> +theme #> <par id="cli-82040-64" class="myclass">
Capture the output of cli functions instead of printing it
cli_fmt(expr, collapse = FALSE, strip_newline = FALSE)
cli_fmt(expr, collapse = FALSE, strip_newline = FALSE)
expr |
Expression to evaluate, containing |
collapse |
Whether to collapse the output into a single character scalar, or return a character vector with one element for each line. |
strip_newline |
Whether to strip the trailing newline. |
cli_fmt({ cli_alert_info("Loading data file") cli_alert_success("Loaded data file") })
cli_fmt({ cli_alert_info("Loading data file") cli_alert_success("Loaded data file") })
This function can be used directly, or via the {.val ...}
inline
style. {.val {expr}}
calls cli_format()
automatically on the value
of expr
, before styling and collapsing it.
cli_format(x, style = NULL, ...) ## Default S3 method: cli_format(x, style = NULL, ...) ## S3 method for class 'character' cli_format(x, style = NULL, ...) ## S3 method for class 'numeric' cli_format(x, style = NULL, ...)
cli_format(x, style = NULL, ...) ## Default S3 method: cli_format(x, style = NULL, ...) ## S3 method for class 'character' cli_format(x, style = NULL, ...) ## S3 method for class 'numeric' cli_format(x, style = NULL, ...)
x |
The object to format. |
style |
List of formatting options, see the individual methods for the style options they support. |
... |
Additional arguments for methods. |
months <- month.name[1:3] cli_text("{.val {months}}")
#> "January", "February", and "March"
nums <- 1:5 / 7 cli_text("{.val {nums}}")
#> 0.142857142857143, 0.285714285714286, 0.428571428571429, #> 0.571428571428571, and 0.714285714285714
nums <- 1:5 / 7 divid <- cli_div(theme = list(.val = list(digits = 3))) cli_text("{.val {nums}}") cli_end(divid)
#> 0.143, 0.286, 0.429, 0.571, and 0.714
It is possible to define new S3 methods for cli_format
and then
these will be used automatically for {.val ...}
expressions.
cli_format.month <- function(x, style = NULL, ...) { x <- encodeString(substr(x, 1, 3), quote = "\"") NextMethod("cli_format") } registerS3method("cli_format", "month", cli_format.month) months <- structure(month.name[1:3], class = "month") cli_text("{.val {months}}")
#> "Jan", "Feb", and "Mar"
This method can be typically used in format()
S3 methods. Then the
print()
method of the class can be easily defined in terms of such a
format()
method. See examples below.
cli_format_method(expr, theme = getOption("cli.theme"))
cli_format_method(expr, theme = getOption("cli.theme"))
expr |
Expression that calls |
theme |
Theme to use for the formatting. |
Character vector, one element for each line of the printout.
# Let's create format and print methods for a new S3 class that # represents the an installed R package: `r_package` # An `r_package` will contain the DESCRIPTION metadata of the package # and also its installation path. new_r_package <- function(pkg) { tryCatch( desc <- packageDescription(pkg), warning = function(e) stop("Cannot find R package `", pkg, "`") ) file <- dirname(attr(desc, "file")) if (basename(file) != pkg) file <- dirname(file) structure( list(desc = unclass(desc), lib = dirname(file)), class = "r_package" ) } format.r_package <- function(x, ...) { cli_format_method({ cli_h1("{.pkg {x$desc$Package}} {cli::symbol$line} {x$desc$Title}") cli_text("{x$desc$Description}") cli_ul(c( "Version: {x$desc$Version}", if (!is.null(x$desc$Maintainer)) "Maintainer: {x$desc$Maintainer}", "License: {x$desc$License}" )) if (!is.na(x$desc$URL)) cli_text("See more at {.url {x$desc$URL}}") }) } # Now the print method is easy: print.r_package <- function(x, ...) { cat(format(x, ...), sep = "\n") } # Try it out new_r_package("cli") # The formatting of the output depends on the current theme: opt <- options(cli.theme = simple_theme()) print(new_r_package("cli")) options(opt) # <- restore theme
# Let's create format and print methods for a new S3 class that # represents the an installed R package: `r_package` # An `r_package` will contain the DESCRIPTION metadata of the package # and also its installation path. new_r_package <- function(pkg) { tryCatch( desc <- packageDescription(pkg), warning = function(e) stop("Cannot find R package `", pkg, "`") ) file <- dirname(attr(desc, "file")) if (basename(file) != pkg) file <- dirname(file) structure( list(desc = unclass(desc), lib = dirname(file)), class = "r_package" ) } format.r_package <- function(x, ...) { cli_format_method({ cli_h1("{.pkg {x$desc$Package}} {cli::symbol$line} {x$desc$Title}") cli_text("{x$desc$Description}") cli_ul(c( "Version: {x$desc$Version}", if (!is.null(x$desc$Maintainer)) "Maintainer: {x$desc$Maintainer}", "License: {x$desc$License}" )) if (!is.na(x$desc$URL)) cli_text("See more at {.url {x$desc$URL}}") }) } # Now the print method is easy: print.r_package <- function(x, ...) { cat(format(x, ...), sep = "\n") } # Try it out new_r_package("cli") # The formatting of the output depends on the current theme: opt <- options(cli.theme = simple_theme()) print(new_r_package("cli")) options(opt) # <- restore theme
cli has three levels of headings.
cli_h1(text, id = NULL, class = NULL, .envir = parent.frame()) cli_h2(text, id = NULL, class = NULL, .envir = parent.frame()) cli_h3(text, id = NULL, class = NULL, .envir = parent.frame())
cli_h1(text, id = NULL, class = NULL, .envir = parent.frame()) cli_h2(text, id = NULL, class = NULL, .envir = parent.frame()) cli_h3(text, id = NULL, class = NULL, .envir = parent.frame())
text |
Text of the heading. It can contain inline markup. |
id |
Id of the heading element, string. It can be used in themes. |
class |
Class of the heading element, string. It can be used in themes. |
.envir |
Environment to evaluate the glue expressions in. |
This is how the headings look with the default builtin theme.
cli_h1("Header {.emph 1}") cli_h2("Header {.emph 2}") cli_h3("Header {.emph 3}")
#> #> ── Header 1 ────────────────────────────────────────────────────────── #> #> ── Header 2 ── #> #> ── Header 3
These functions supports inline markup.
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
A list item is a container, see containers.
cli_li( items = NULL, labels = names(items), id = NULL, class = NULL, .auto_close = TRUE, .envir = parent.frame() )
cli_li( items = NULL, labels = names(items), id = NULL, class = NULL, .auto_close = TRUE, .envir = parent.frame() )
items |
Character vector of items, or |
labels |
For definition lists the item labels. |
id |
Id of the new container. Can be used for closing it with
|
class |
Class of the item container. Can be used in themes. |
.auto_close |
Whether to close the container, when the calling
function finishes (or |
.envir |
Environment to evaluate the glue expressions in. It is
also used to auto-close the container if |
fun <- function() { ul <- cli_ul() cli_li("one:") cli_ol(letters[1:3]) cli_li("two:") cli_li("three") cli_end(ul) } fun()
#> • one: #> 1. a #> 2. b #> 3. c #> • two: #> • three
The id of the new container element, invisibly.
This function supports inline markup.
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
If there is no active app, then it calls start_app()
.
cli_list_themes()
cli_list_themes()
A list of data frames with the active themes. Each data frame row is a style that applies to selected CLI tree nodes. Each data frame has columns:
selector
: The original CSS-like selector string. See themes.
parsed
: The parsed selector, as used by cli for matching to nodes.
style
: The original style.
cnt
: The id of the container the style is currently applied to, or
NA
if the style is not used.
An ordered list is a container, see containers.
cli_ol( items = NULL, id = NULL, class = NULL, .close = TRUE, .auto_close = TRUE, .envir = parent.frame() )
cli_ol( items = NULL, id = NULL, class = NULL, .close = TRUE, .auto_close = TRUE, .envir = parent.frame() )
items |
If not |
id |
Id of the list container. Can be used for closing it with
|
class |
Class of the list container. Can be used in themes. |
.close |
Whether to close the list container if the |
.auto_close |
Whether to close the container, when the calling
function finishes (or |
.envir |
Environment to evaluate the glue expressions in. It is
also used to auto-close the container if |
fun <- function() { cli_ol(c("one", "two", "three")) } fun()
#> 1. one #> 2. two #> 3. three
## Adding items one by one fun <- function() { cli_ol() cli_li("{.emph one}") cli_li("{.emph two}") cli_li("{.emph three}") cli_end() } fun()
#> 1. one #> 2. two #> 3. three
fun <- function() { cli_div(theme = list(ol = list("margin-left" = 2))) cli_ul() cli_li("one") cli_ol(c("foo", "bar", "foobar")) cli_li("two") cli_end() cli_end() } fun()
#> • one #> 1. foo #> 2. bar #> 3. foobar #> • two
The id of the new container element, invisibly.
This function supports inline markup.
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
Note that this only refers to the current R process. If the output is produced in another process, then it is not relevant.
cli_output_connection()
cli_output_connection()
In interactive sessions the standard output is chosen, otherwise the standard error is used. This is to avoid painting output messages red in the R GUIs.
Connection object.
The builtin theme leaves an empty line between paragraphs. See also containers.
cli_par(id = NULL, class = NULL, .auto_close = TRUE, .envir = parent.frame())
cli_par(id = NULL, class = NULL, .auto_close = TRUE, .envir = parent.frame())
id |
Element id, a string. If |
class |
Class name, sting. Can be used in themes. |
.auto_close |
Whether to close the container, when the calling
function finishes (or |
.envir |
Environment to evaluate the glue expressions in. It is
also used to auto-close the container if |
clifun <- function() { cli_par() cli_text(cli:::lorem_ipsum()) } clifun() clifun()
#> Sunt anim ullamco Lorem qui mollit anim est in deserunt adipisicing. #> Enim deserunt laborum ad qui qui. Anim esse non anim magna Lorem #> consequat dolore labore cupidatat magna et. Esse nulla eiusmod Lorem #> exercitation cupidatat velit enim exercitation excepteur non officia #> incididunt. Id laborum dolore commodo Lorem esse ea sint proident. #> #> Fugiat mollit in Lorem velit qui exercitation ipsum consectetur ad #> nisi ut eu do ullamco. Mollit officia reprehenderit culpa Lorem est #> reprehenderit excepteur enim magna incididunt ea. Irure nisi ad #> exercitation deserunt enim anim excepteur quis minim laboris veniam #> nulla pariatur. Enim irure aute nulla irure qui non. Minim velit #> proident sunt sint. Proident sit occaecat ex aute. #>
The id of the new container element, invisibly.
The cli_process_*()
functions are superseded by
the cli_progress_message()
and cli_progress_step()
functions,
because they have a better default behavior.
Typically you call cli_process_start()
to start the process, and then
cli_process_done()
when it is done. If an error happens before
cli_process_done()
is called, then cli automatically shows the message
for unsuccessful termination.
cli_process_start( msg, msg_done = paste(msg, "... done"), msg_failed = paste(msg, "... failed"), on_exit = c("auto", "failed", "done"), msg_class = "alert-info", done_class = "alert-success", failed_class = "alert-danger", .auto_close = TRUE, .envir = parent.frame() ) cli_process_done( id = NULL, msg_done = NULL, .envir = parent.frame(), done_class = "alert-success" ) cli_process_failed( id = NULL, msg = NULL, msg_failed = NULL, .envir = parent.frame(), failed_class = "alert-danger" )
cli_process_start( msg, msg_done = paste(msg, "... done"), msg_failed = paste(msg, "... failed"), on_exit = c("auto", "failed", "done"), msg_class = "alert-info", done_class = "alert-success", failed_class = "alert-danger", .auto_close = TRUE, .envir = parent.frame() ) cli_process_done( id = NULL, msg_done = NULL, .envir = parent.frame(), done_class = "alert-success" ) cli_process_failed( id = NULL, msg = NULL, msg_failed = NULL, .envir = parent.frame(), failed_class = "alert-danger" )
msg |
The message to show to indicate the start of the process or
computation. It will be collapsed into a single string, and the first
line is kept and cut to |
msg_done |
The message to use for successful termination. |
msg_failed |
The message to use for unsuccessful termination. |
on_exit |
Whether this process should fail or terminate
successfully when the calling function (or the environment in |
msg_class |
The style class to add to the message. Use an empty string to suppress styling. |
done_class |
The style class to add to the successful termination message. Use an empty string to suppress styling.a |
failed_class |
The style class to add to the unsuccessful termination message. Use an empty string to suppress styling.a |
.auto_close |
Whether to clear the status bar when the calling
function finishes (or |
.envir |
Environment to evaluate the glue expressions in. It is
also used to auto-clear the status bar if |
id |
Id of the status bar container to clear. If |
If you handle the errors of the process or computation, then you can do
the opposite: call cli_process_start()
with on_exit = "done"
, and
in the error handler call cli_process_failed()
. cli will automatically
call cli_process_done()
on successful termination, when the calling
function finishes.
See examples below.
Id of the status bar container.
This function supports inline markup.
The cli_progress_message()
and cli_progress_step()
functions, for a superior API.
Other status bar:
cli_status()
,
cli_status_clear()
,
cli_status_update()
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
## Failure by default fun <- function() { cli_process_start("Calculating") if (interactive()) Sys.sleep(1) if (runif(1) < 0.5) stop("Failed") cli_process_done() } tryCatch(fun(), error = function(err) err) ## Success by default fun2 <- function() { cli_process_start("Calculating", on_exit = "done") tryCatch({ if (interactive()) Sys.sleep(1) if (runif(1) < 0.5) stop("Failed") }, error = function(err) cli_process_failed()) } fun2()
## Failure by default fun <- function() { cli_process_start("Calculating") if (interactive()) Sys.sleep(1) if (runif(1) < 0.5) stop("Failed") cli_process_done() } tryCatch(fun(), error = function(err) err) ## Success by default fun2 <- function() { cli_process_start("Calculating", on_exit = "done") tryCatch({ if (interactive()) Sys.sleep(1) if (runif(1) < 0.5) stop("Failed") }, error = function(err) cli_process_failed()) } fun2()
Note that this function is currently experimental!
Use cli_progress_along()
in a mapping function or in a for loop, to add a
progress bar. It uses cli_progress_bar()
internally.
cli_progress_along( x, name = NULL, total = length(x), ..., .envir = parent.frame() )
cli_progress_along( x, name = NULL, total = length(x), ..., .envir = parent.frame() )
x |
Sequence to add the progress bar to. |
name |
Name of the progress bar, a label, passed to
|
total |
Passed to |
... |
Passed to |
.envir |
Passed to |
for
loopA for
loop with cli_progress_along()
looks like this:
for (i in cli_progress_along(seq)) { ... }
A complete example:
clifun <- function() { for (i in cli_progress_along(1:100, "Downloading")) { Sys.sleep(4/100) } } clifun()
lapply()
and other mapping functionsThey will look like this:
lapply(cli_progress_along(X), function(i) ...)
A complete example:
res <- lapply(cli_progress_along(1:100, "Downloading"), function(i) { Sys.sleep(4/100) })
clifun <- function() { for (i in cli_progress_along(1:100, format = "Downloading data file {cli::pb_current}")) { Sys.sleep(4/100) } } clifun()
Note that if you use break
in the for
loop, you probably want to
terminate the progress bar explicitly when breaking out of the loop,
or right after the loop:
for (i in cli_progress_along(seq)) { ... if (cond) cli_progress_done() && break ... }
An index vector from 1 to length(x)
that triggers progress
updates as you iterate over it.
This function supports inline markup.
cli_progress_bar()
and the traditional progress bar API.
Other progress bar functions:
cli_progress_bar()
,
cli_progress_builtin_handlers()
,
cli_progress_message()
,
cli_progress_num()
,
cli_progress_output()
,
cli_progress_step()
,
cli_progress_styles()
,
progress-variables
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
This is the reference manual of the three functions that create, update and terminate progress bars. For a tutorial see the cli progress bars.
cli_progress_bar()
creates a new progress bar.
cli_progress_update()
updates the state of a progress bar, and
potentially the display as well.
cli_progress_done()
terminates a progress bar.
cli_progress_bar( name = NULL, status = NULL, type = c("iterator", "tasks", "download", "custom"), total = NA, format = NULL, format_done = NULL, format_failed = NULL, clear = getOption("cli.progress_clear", TRUE), current = TRUE, auto_terminate = type != "download", extra = NULL, .auto_close = TRUE, .envir = parent.frame() ) cli_progress_update( inc = NULL, set = NULL, total = NULL, status = NULL, extra = NULL, id = NULL, force = FALSE, .envir = parent.frame() ) cli_progress_done(id = NULL, .envir = parent.frame(), result = "done")
cli_progress_bar( name = NULL, status = NULL, type = c("iterator", "tasks", "download", "custom"), total = NA, format = NULL, format_done = NULL, format_failed = NULL, clear = getOption("cli.progress_clear", TRUE), current = TRUE, auto_terminate = type != "download", extra = NULL, .auto_close = TRUE, .envir = parent.frame() ) cli_progress_update( inc = NULL, set = NULL, total = NULL, status = NULL, extra = NULL, id = NULL, force = FALSE, .envir = parent.frame() ) cli_progress_done(id = NULL, .envir = parent.frame(), result = "done")
name |
This is typically used as a label, and should be short, at most 20 characters. |
status |
New status string of the progress bar, if not |
type |
Type of the progress bar. It is used to select a default
display if
|
total |
Total number of progress units, or |
format |
Format string. It has to be specified for custom progress bars, otherwise it is optional, and a default display is selected based on the progress bat type and whether the number of total units is known. Format strings may contain glue substitution, the support pluralization and cli styling. See progress-variables for special variables that you can use in the custom format. |
format_done |
Format string for successful termination. By default
the same as |
format_failed |
Format string for unsuccessful termination. By
default the same as |
clear |
Whether to remove the progress bar from the screen after
it has terminated. Defaults to the |
current |
Whether to use this progress bar as the current progress bar of the calling function. See more at 'The current progress bar' below. |
auto_terminate |
Whether to terminate the progress bar if the number of current units reaches the number of total units. |
extra |
Extra data to add to the progress bar. This can be
used in custom format strings for example. It should be a named list.
|
.auto_close |
Whether to terminate the progress bar when the
calling function (or the one with execution environment in |
.envir |
The environment to use for auto-termination and for glue substitution. It is also used to find and set the current progress bar. |
inc |
Increment in progress units. This is ignored if |
set |
Set the current number of progress units to this value.
Ignored if |
id |
Progress bar to update or terminate. If |
force |
Whether to force a display update, even if no update is due. |
result |
String to select successful or unsuccessful termination.
It is only used if the progress bar is not cleared from the screen.
It can be one of |
cli_progress_bar()
creates a progress bar, cli_progress_update()
updates an existing progress bar, and cli_progress_done()
terminates
it.
It is good practice to always set the name
argument, to make the
progress bar more informative.
clean <- function() { cli_progress_bar("Cleaning data", total = 100) for (i in 1:100) { Sys.sleep(5/100) cli_progress_update() } cli_progress_done() } clean()
There are three builtin types of progress bars, and a custom type.
tasks <- function() { cli_progress_bar("Tasks", total = 3, type = "tasks") for (i in 1:3) { Sys.sleep(1) cli_progress_update() } cli_progress_done() } tasks()
total
If total
is not known, then cli shows a different progress bar.
Note that you can also set total
in cli_progress_update()
, if it
not known when the progress bar is created, but you learn it later.
nototal <- function() { cli_progress_bar("Parameter tuning") for (i in 1:100) { Sys.sleep(3/100) cli_progress_update() } cli_progress_done() } nototal()
By default cli removes terminated progress bars from the screen, if
the terminal supports this. If you want to change this, use the
clear
argument of cli_progress_bar()
, or the cli.progress_clear
global option (see cli-config) to change this.
(In the cli documentation we usually set cli.progress_clear
to FALSE
,
so users can see how finished progress bars look.)
In this example the first progress bar is cleared, the second is not.
fun <- function() { cli_progress_bar("Data cleaning", total = 100, clear = TRUE) for (i in 1:100) { Sys.sleep(3/100) cli_progress_update() } cli_progress_bar("Parameter tuning", total = 100, clear = FALSE) for (i in 1:100) { Sys.sleep(3/100) cli_progress_update() } } fun()
Updating a progress bar on the screen is costly, so cli tries to avoid
it for quick loops. By default a progress bar is only shown after two
seconds, or after half of that if less than 50% of the iterations are
complete. You can change the two second default with the
cli.progress_show_after
global option (see cli-config).
(In the cli documentation we usually set cli.progress_show_after
to
0
(zero seconds), so progress bars are shown immediately.)
In this example we only show the progress bar after one second, because more than 50% of the iterations remain after one second.
fun <- function() { cli_alert("Starting now, at {Sys.time()}") cli_progress_bar( total = 100, format = "{cli::pb_bar} {pb_percent} @ {Sys.time()}" ) for (i in 1:100) { Sys.sleep(4/100) cli_progress_update() } } options(cli.progress_show_after = 2) fun()
By default cli sets the new progress bar as the current progress bar
of the calling function. The current progress bar is the default one
in cli progress bar operations. E.g. if no progress bar id is supplied
in cli_progress_update()
, then the current progress bar is updated.
Every function can only have a single current progress bar, and if a
new one is created, then the previous one (if any) is automatically
terminated. The current progress bar is also terminated when the function
that created it exits. Thanks to these rules, most often you don't need
to explicitly deal with progress bar ids, and you don't need to
explicitly call cli_progress_done()
:
fun <- function() { cli_progress_bar("First step ", total = 100) for (i in 1:100) { Sys.sleep(2/100) cli_progress_update() } cli_progress_bar("Second step", total = 100) for (i in 1:100) { Sys.sleep(2/100) cli_progress_update() } } fun()
cli allows emitting regular cli output (alerts, headers, lists, etc.) while a progress bar is active. On terminals that support this, cli will remove the progress bar temporarily, emit the output, and then restores the progress bar.
fun <- function() { cli_alert_info("Before the progress bar") cli_progress_bar("Calculating", total = 100) for (i in 1:50) { Sys.sleep(4/100) cli_progress_update() } cli_alert_info("Already half way!") for (i in 1:50) { Sys.sleep(4/100) cli_progress_update() } cli_alert_info("All done") } fun()
See also cli_progress_output()
, which sends text for the current
progress handler. E.g. in a Shiny app it will send the output to the
Shiny progress bar, as opposed to the cli_alert()
etc. cli functions
which will print the text to the console.
In addition to the builtin types, you can also specify a custom format string. In this case progress variables are probably useful to avoid calculating some progress bar quantities like the elapsed time, of the ETA manually. You can also use your own variables in the calling function:
fun <- function(urls) { cli_progress_bar( format = paste0( "{pb_spin} Downloading {.path {basename(url)}} ", "[{pb_current}/{pb_total}] ETA:{pb_eta}" ), format_done = paste0( "{col_green(symbol$tick)} Downloaded {pb_total} files ", "in {pb_elapsed}." ),, total = length(urls) ) for (url in urls) { cli_progress_update() Sys.sleep(5/10) } } fun(paste0("https://acme.com/data-", 1:10, ".zip"))
cli_progress_bar()
returns the id of the new progress bar.
The id is a string constant.
cli_progress_update()
returns the id of the progress bar,
invisibly.
cli_progress_done()
returns TRUE
, invisibly, always.
These functions support inline markup.
cli_progress_message()
and cli_progress_step()
for simpler
progress messages.
Other progress bar functions:
cli_progress_along()
,
cli_progress_builtin_handlers()
,
cli_progress_message()
,
cli_progress_num()
,
cli_progress_output()
,
cli_progress_step()
,
cli_progress_styles()
,
progress-variables
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
The progress handler(s) to use can be selected with global options.
cli_progress_builtin_handlers()
cli_progress_builtin_handlers()
There are three options that specify which handlers will be selected, but most of the time you only need to use one of them. You can set these options to a character vector, the names of the built-in cli handlers you want to use:
If cli.progress_handlers_only
is set, then these handlers are used,
without considering others and without checking if they are able to
handle a progress bar. This option is mainly intended for testing
purposes.
The handlers named in cli.progress_handlers
are checked if they are
able to handle the progress bar, and from the ones that are, the first
one is selected. This is usually the option that the end use would want
to set.
The handlers named in cli.progress_handlers_force
are always appended
to the ones selected via cli.progress_handlers
. This option is useful
to add an additional handler, e.g. a logger that writes to a file.
cli_progress_builtin_handlers()
returns the names of the
currently supported progress handlers.
cli
Use cli's internal status bar, the last line of the screen, to show the progress bar. This handler is always able to handle all progress bars.
logger
Log progress updates to the screen, with one line for each update and with time stamps. This handler is always able to handle all progress bars.
progressr
Use the progressr package to create progress bars. This handler is always able to handle all progress bars. (The progressr package needs to be installed.)
rstudio
Use RStudio's job panel to show the progress bars. This handler is available at the RStudio console, in recent versions of RStudio.
say
Use the macOS say
command to announce progress events in speech (type
man say
on a terminal for more info). Set the cli.progress_say_frequency
option to set the minimum delay between say
invocations, the default is
three seconds. This handler is available on macOS, if the say
command is
on the path.
The external command and its arguments can be configured with options:
cli_progress_say_args
: command line arguments, e.g. you can use this
to select a voice on macOS,
cli_progress_say_command
: external command to run,
cli_progress_say_frequency
: wait at least this many seconds between
calling the external command.
shiny
Use shiny's progress bars. This handler is available if a shiny app is running.
Other progress bar functions:
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_num()
,
cli_progress_output()
,
cli_progress_step()
,
cli_progress_styles()
,
progress-variables
Useful for experimenting with format strings and for documentation. It creates a progress bar, iterates it until it terminates and saves the progress updates.
cli_progress_demo( name = NULL, status = NULL, type = c("iterator", "tasks", "download", "custom"), total = NA, .envir = parent.frame(), ..., at = if (is_interactive()) NULL else 50, show_after = 0, live = NULL, delay = 0, start = as.difftime(5, units = "secs") )
cli_progress_demo( name = NULL, status = NULL, type = c("iterator", "tasks", "download", "custom"), total = NA, .envir = parent.frame(), ..., at = if (is_interactive()) NULL else 50, show_after = 0, live = NULL, delay = 0, start = as.difftime(5, units = "secs") )
name |
Passed to |
status |
Passed to |
type |
Passed to |
total |
Passed to |
.envir |
Passed to |
... |
Passed to |
at |
The number of progress units to show and capture the progress
bar at. If |
show_after |
Delay to show the progress bar. Overrides the
|
live |
Whether to show the progress bat on the screen, or just
return the recorded updates. Defaults to the value of the
|
delay |
Delay between progress bar updates. |
start |
Time to subtract from the start time, to simulate a progress bar that takes longer to run. |
List with class cli_progress_demo
, which has a print and a
format method for pretty printing. The lines
entry contains the
output lines, each corresponding to one update.
This is a simplified progress bar, a single (dynamic) message, without progress units.
cli_progress_message( msg, current = TRUE, .auto_close = TRUE, .envir = parent.frame(), ... )
cli_progress_message( msg, current = TRUE, .auto_close = TRUE, .envir = parent.frame(), ... )
msg |
Message to show. It may contain glue substitution and cli
styling. It can be updated via |
current |
Passed to |
.auto_close |
Passed to |
.envir |
Passed to |
... |
Passed to |
cli_progress_message()
always shows the message, even if no
update is due. When the progress message is terminated, it is removed
from the screen by default.
Note that the message can be dynamic: if you update it with
cli_progress_update()
, then cli uses the current values in the string
substitutions.
fun <- function() { cli_progress_message("Task one is running...") Sys.sleep(2) cli_progress_message("Task two is running...") Sys.sleep(2) step <- 1L cli_progress_message("Task three is underway: step {step}") for (step in 1:5) { Sys.sleep(0.5) cli_progress_update() } } fun()
The id of the new progress bar.
This function supports inline markup.
cli_progress_bar()
for the complete progress bar API.
cli_progress_step()
for a similar display that is styled by default.
Other progress bar functions:
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_builtin_handlers()
,
cli_progress_num()
,
cli_progress_output()
,
cli_progress_step()
,
cli_progress_styles()
,
progress-variables
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
Progress bar utility functions.
cli_progress_num() cli_progress_cleanup()
cli_progress_num() cli_progress_cleanup()
cli_progress_num()
returns the number of currently
active progress bars. (These do not currently include the progress
bars created in C/C++ code.)
cli_progress_cleanup()
terminates all active progress bars.
(It currently ignores progress bars created in the C/C++ code.)
cli_progress_num()
returns an integer scalar.
'cli_progress_cleanup() does not return anything.
Other progress bar functions:
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_builtin_handlers()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_progress_styles()
,
progress-variables
The text is calculated via cli_text()
, so all cli features can be
used here, including progress variables.
cli_progress_output(text, id = NULL, .envir = parent.frame())
cli_progress_output(text, id = NULL, .envir = parent.frame())
text |
Text to output. It is formatted via |
id |
Progress bar id. The default is the current progress bar. |
.envir |
Environment to use for glue interpolation of |
The text is passed to the progress handler(s), that may or may not be able to print it.
fun <- function() { cli_alert_info("Before the progress bar") cli_progress_bar("Calculating", total = 100) for (i in 1:50) { Sys.sleep(4/100) cli_progress_update() } cli_progress_output("Already half way!") for (i in 1:50) { Sys.sleep(4/100) cli_progress_update() } cli_alert_info("All done") } fun()
TRUE
, always.
This function supports inline markup.
Other progress bar functions:
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_builtin_handlers()
,
cli_progress_message()
,
cli_progress_num()
,
cli_progress_step()
,
cli_progress_styles()
,
progress-variables
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
This is a simplified progress bar, a single (dynamic) message, without progress units.
cli_progress_step( msg, msg_done = msg, msg_failed = msg, spinner = FALSE, class = if (!spinner) ".alert-info", current = TRUE, .auto_close = TRUE, .envir = parent.frame(), ... )
cli_progress_step( msg, msg_done = msg, msg_failed = msg, spinner = FALSE, class = if (!spinner) ".alert-info", current = TRUE, .auto_close = TRUE, .envir = parent.frame(), ... )
msg |
Message to show. It may contain glue substitution and cli
styling. It can be updated via |
msg_done |
Message to show on successful termination. By default
this it is the same as |
msg_failed |
Message to show on unsuccessful termination. By
default it is the same as |
spinner |
Whether to show a spinner at the beginning of the line.
To make the spinner spin, you'll need to call |
class |
cli class to add to the message. By default there is no class for steps with a spinner. |
current |
Passed to |
.auto_close |
Passed to |
.envir |
Passed to |
... |
Passed to |
cli_progress_step()
always shows the progress message,
even if no update is due.
f <- function() { cli_progress_step("Downloading data") Sys.sleep(2) cli_progress_step("Importing data") Sys.sleep(1) cli_progress_step("Cleaning data") Sys.sleep(2) cli_progress_step("Fitting model") Sys.sleep(3) } f()
You can add a spinner to some or all steps with spinner = TRUE
,
but note that this will only work if you call cli_progress_update()
regularly.
f <- function() { cli_progress_step("Downloading data", spinner = TRUE) for (i in 1:100) { Sys.sleep(2/100); cli_progress_update() } cli_progress_step("Importing data") Sys.sleep(1) cli_progress_step("Cleaning data") Sys.sleep(2) cli_progress_step("Fitting model", spinner = TRUE) for (i in 1:100) { Sys.sleep(3/100); cli_progress_update() } } f()
You can make the step messages dynamic, using glue templates.
Since cli_progress_step()
show that message immediately, we need
to initialize msg
first.
f <- function() { msg <- "" cli_progress_step("Downloading data{msg}", spinner = TRUE) for (i in 1:100) { Sys.sleep(2/100) msg <- glue::glue(", got file {i}/100") cli_progress_update() } cli_progress_step("Importing data") Sys.sleep(1) cli_progress_step("Cleaning data") Sys.sleep(2) cli_progress_step("Fitting model", spinner = TRUE) for (i in 1:100) { Sys.sleep(3/100); cli_progress_update() } } f()
You can specify a different message for successful and/or unsuccessful termination:
f <- function() { size <- 0L cli_progress_step( "Downloading data.", msg_done = "Downloaded {prettyunits::pretty_bytes(size)}.", spinner = TRUE ) for (i in 1:100) { Sys.sleep(3/100) size <- size + 8192 cli_progress_update() } } f()
This function supports inline markup.
Other progress bar functions:
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_builtin_handlers()
,
cli_progress_message()
,
cli_progress_num()
,
cli_progress_output()
,
cli_progress_styles()
,
progress-variables
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
The following options are used to select a style:
cli_progress_bar_style
cli_progress_bar_style_ascii
cli_progress_bar_style_unicode
cli_progress_styles()
cli_progress_styles()
On Unicode terminals (if is_utf8_output()
is TRUE
), the
cli_progress_bar_style_unicode
and cli_progress_bar_style
options are used.
On ASCII terminals (if is_utf8_output()
is FALSE
), the
cli_pgoress_bar_style_ascii
and cli_progress_bar_style
options
are are used.
for (style in names(cli_progress_styles())) { options(cli.progress_bar_style = style) label <- ansi_align(paste0("Style '", style, "'"), 20) print(cli_progress_demo(label, live = FALSE, at = 66, total = 100)) } options(cli.progress_var_style = NULL)
#> Style 'classic' ##################### 66% | ETA: 3s #> Style 'squares' ■■■■■■■■■■■■■■■■■■■■■ 66% | ETA: 3s #> Style 'dot' ────────────────────●────────── 66% | ETA: 3s #> Style 'fillsquares' ■■■■■■■■■■■■■■■■■■■■■□□□□□□□□□□ 66% | ETA: 3s #> Style 'bar' ███████████████████████████████ 66% | ETA: 3s
A named list with sublists containing elements
complete
, incomplete
and potentially current
.
Other progress bar functions:
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_builtin_handlers()
,
cli_progress_message()
,
cli_progress_num()
,
cli_progress_output()
,
cli_progress_step()
,
progress-variables
It can be used to separate parts of the output.
cli_rule( left = "", center = "", right = "", id = NULL, .envir = parent.frame() )
cli_rule( left = "", center = "", right = "", id = NULL, .envir = parent.frame() )
left |
Label to show on the left. It interferes with the |
center |
Label to show at the center. It interferes with the
|
right |
Label to show on the right. It interferes with the |
id |
Element id, a string. If |
.envir |
Environment to evaluate the glue expressions in. |
pkg <- "mypackage" cli_rule(left = "{.pkg {pkg}} results")
#> ── mypackage results ─────────────────────────────────────────────────
The line style of the rule can be changed via the the line-type
property. Possible values are:
"single"
: (same as 1
), a single line,
"double"
: (same as 2
), a double line,
"bar1"
, "bar2"
, "bar3"
, etc., "bar8"
uses varying height bars.
Colors and background colors can similarly changed via a theme.
d <- cli_div(theme = list(rule = list( color = "cyan", "line-type" = "double"))) cli_rule("Summary", right = "{.pkg mypackage}") cli_end(d)
#> ══ Summary ══════════════════════════════════════════════ mypackage ══
This function supports inline markup.
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
Contains currently:
cli_unicode_option
: whether the cli.unicode
option is set and its
value. See is_utf8_output()
.
symbol_charset
: the selected character set for symbol, UTF-8,
Windows, or ASCII.
console_utf8
: whether the console supports UTF-8. See
base::l10n_info()
.
latex_active
: whether we are inside knitr, creating a LaTeX
document.
num_colors
: number of ANSI colors. See num_ansi_colors()
.
console_with
: detected console width.
cli_sitrep()
cli_sitrep()
Named list with entries listed above. It has a cli_sitrep
class, with a print()
and format()
method.
cli_sitrep()
cli_sitrep()
The cli_status_*()
functions are superseded by
the cli_progress_message()
and cli_progress_step()
functions,
because they have a better default behavior.
The status bar is the last line of the terminal. cli apps can use this to show status information, progress bars, etc. The status bar is kept intact by all semantic cli output.
cli_status( msg, msg_done = paste(msg, "... done"), msg_failed = paste(msg, "... failed"), .keep = FALSE, .auto_close = TRUE, .envir = parent.frame(), .auto_result = c("clear", "done", "failed", "auto") )
cli_status( msg, msg_done = paste(msg, "... done"), msg_failed = paste(msg, "... failed"), .keep = FALSE, .auto_close = TRUE, .envir = parent.frame(), .auto_result = c("clear", "done", "failed", "auto") )
msg |
The text to show, a character vector. It will be
collapsed into a single string, and the first line is kept and cut to
|
msg_done |
The message to use when the message is cleared, when
the calculation finishes successfully. If |
msg_failed |
The message to use when the message is cleared, when
the calculation finishes unsuccessfully. If |
.keep |
What to do when this status bar is cleared. If |
.auto_close |
Whether to clear the status bar when the calling
function finishes (or |
.envir |
Environment to evaluate the glue expressions in. It is
also used to auto-clear the status bar if |
.auto_result |
What to do when auto-closing the status bar. |
Use cli_status_clear()
to clear the status bar.
Often status messages are associated with processes. E.g. the app starts
downloading a large file, so it sets the status bar accordingly. Once the
download is done (or has failed), the app typically updates the status bar
again. cli automates much of this, via the msg_done
, msg_failed
, and
.auto_result
arguments. See examples below.
The id of the new status bar container element, invisibly.
Status bars support inline markup.
The cli_progress_message()
and cli_progress_step()
functions, for a superior API.
Other status bar:
cli_process_start()
,
cli_status_clear()
,
cli_status_update()
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
The cli_status_*()
functions are superseded by
the cli_progress_message()
and cli_progress_step()
functions,
because they have a better default behavior.
Clear the status bar
cli_status_clear( id = NULL, result = c("clear", "done", "failed"), msg_done = NULL, msg_failed = NULL, .envir = parent.frame() )
cli_status_clear( id = NULL, result = c("clear", "done", "failed"), msg_done = NULL, msg_failed = NULL, .envir = parent.frame() )
id |
Id of the status bar container to clear. If |
result |
Whether to show a message for success or failure or just clear the status bar. |
msg_done |
If not |
msg_failed |
If not |
.envir |
Environment to evaluate the glue expressions in. It is
also used to auto-clear the status bar if |
The cli_progress_message()
and cli_progress_step()
functions, for a superior API.
Other status bar:
cli_process_start()
,
cli_status()
,
cli_status_update()
The cli_status_*()
functions are superseded by
the cli_progress_message()
and cli_progress_step()
functions,
because they have a better default behavior.
Update the status bar
cli_status_update( id = NULL, msg = NULL, msg_done = NULL, msg_failed = NULL, .envir = parent.frame() )
cli_status_update( id = NULL, msg = NULL, msg_done = NULL, msg_failed = NULL, .envir = parent.frame() )
id |
Id of the status bar to update. Defaults to the current status bar container. |
msg |
Text to update the status bar with. |
msg_done |
Updated "done" message. |
msg_failed |
Updated "failed" message. |
.envir |
Environment to evaluate the glue expressions in. |
Id of the status bar container.
This function supports inline markup.
The cli_progress_message()
and cli_progress_step()
functions, for a superior API.
Other status bar:
cli_process_start()
,
cli_status()
,
cli_status_clear()
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_text()
,
cli_ul()
,
format_error()
,
format_inline()
Write some text to the screen. This function is most appropriate for
longer paragraphs. See cli_alert()
for shorter status messages.
cli_text(..., .envir = parent.frame())
cli_text(..., .envir = parent.frame())
... |
The text to show, in character vectors. They will be concatenated into a single string. Newlines are not preserved. |
.envir |
Environment to evaluate the glue expressions in. |
Text is wrapped to the console width, see console_width()
.
cli_text(cli:::lorem_ipsum())
#> Lorem ad ipsum veniam esse nisi deserunt duis. Qui incididunt elit #> elit mollit sint nulla consectetur aute commodo do elit laboris minim #> et. Laboris ipsum mollit voluptate et non do incididunt eiusmod. Anim #> consectetur mollit laborum occaecat eiusmod excepteur. Ullamco non #> tempor esse anim tempor magna non.
A cli_text()
call always appends a newline character to the end.
cli_text("First line.") cli_text("Second line.")
#> First line. #> Second line.
You can use inline markup, as usual.
cli_text("The {.fn cli_text} function in the {.pkg cli} package.")
#> The `cli_text()` function in the cli package.
String interpolation via glue works as usual. Interpolated vectors are collapsed.
pos <- c(5, 14, 25, 26) cli_text("We have {length(pos)} missing measurements: {pos}.")
#> We have 4 missing measurements: 5, 14, 25, and 26.
Use double braces to combine styling and string interpolation.
fun <- "cli-text" pkg <- "cli" cli_text("The {.fn {fun}} function in the {.pkg {pkg}} package.")
#> The `cli-text()` function in the cli package.
Arguments are concatenated.
cli_text(c("This ", "will ", "all "), "be ", "one ", "sentence.")
#> This will all be one sentence.
You can use cli_text()
within cli containers.
ul <- cli_ul() cli_li("First item.") cli_text("Still the {.emph first} item") cli_li("Second item.") cli_text("Still the {.emph second} item") cli_end(ul)
#> • First item. #> Still the first item #> • Second item. #> Still the second item
This function supports inline markup.
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_ul()
,
format_error()
,
format_inline()
An unordered list is a container, see containers.
cli_ul( items = NULL, id = NULL, class = NULL, .close = TRUE, .auto_close = TRUE, .envir = parent.frame() )
cli_ul( items = NULL, id = NULL, class = NULL, .close = TRUE, .auto_close = TRUE, .envir = parent.frame() )
items |
If not |
id |
Id of the list container. Can be used for closing it with
|
class |
Class of the list container. Can be used in themes. |
.close |
Whether to close the list container if the |
.auto_close |
Whether to close the container, when the calling
function finishes (or |
.envir |
Environment to evaluate the glue expressions in. It is
also used to auto-close the container if |
fun <- function() { cli_ul(c("one", "two", "three")) } fun()
#> • one #> • two #> • three
fun <- function() { cli_ul() cli_li("{.emph one}") cli_li("{.emph two}") cli_li("{.emph three}") cli_end() } fun()
#> • one #> • two #> • three
The id of the new container element, invisibly.
This function supports inline markup.
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
format_error()
,
format_inline()
Add custom cli style to a vector
cli_vec(x, style = list())
cli_vec(x, style = list())
x |
Vector that will be collapsed by cli. |
style |
Style to apply to the vector. It is used as a theme on
a |
You can use this function to change the default parameters of collapsing the vector into a string, see an example below.
The style is added as an attribute, so operations that remove attributes will remove the style as well.
v <- cli_vec( c("foo", "bar", "foobar"), style = list("vec-sep" = " & ", "vec-last" = " & ") ) cli_text("My list: {v}.")
#> My list: foo & bar & foobar.
x <- cli_vec(names(mtcars), list("vec-trunc" = 3)) cli_text("Column names: {x}.")
#> Column names: mpg, cyl, disp, …, gear, and carb.
It is not wrapped, but printed as is. Long lines will overflow. No glue substitution is performed on verbatim text.
cli_verbatim(..., .envir = parent.frame())
cli_verbatim(..., .envir = parent.frame())
... |
The text to show, in character vectors. Each element is printed on a new line. |
.envir |
Environment to evaluate the glue expressions in. |
cli_verbatim("This has\nthree\nlines,")
#> This has #> three #> lines,
No glue substitution happens here.
cli_verbatim("No string {interpolation} or {.emph styling} here")
#> No string {interpolation} or {.emph styling} here
cli_code()
for printing R or other source code.
cli environment variables and options
These are environment variables and options that uses may set, to modify the behavior of cli.
R_CLI_HYPERLINK_MODE
Set to posix
to force generating POSIX compatible ANSI hyperlinks.
If not set, then RStudio compatible links are generated. This is a
temporary crutch until RStudio handles POSIX hyperlinks correctly, and
after that it will be removed.
NO_COLOR
Set to a nonempty value to turn off ANSI colors.
See num_ansi_colors()
.
ESS_BACKGROUND_MODE
Set this environment variable to light
or dark
to indicate dark mode
in Emacs. Once https://github.com/emacs-ess/ESS/pull/1178 is merged, ESS
will set this automatically.
R_CLI_DYNAMIC
Set to true
, TRUE
or True
to assume a dynamic terminal, that supports \r
.
Set to anything else to assume a non-dynamic terminal.
See is_dynamic_tty()
.
R_CLI_NUM_COLORS
Set to a positive integer to assume a given number of colors.
See num_ansi_colors()
.
R_CLI_HYPERLINKS
Set to true
, TRUE
or True
to tell cli that the terminal supports
ANSI hyperlinks.
Set to anything else to assume no hyperlink support.
See style_hyperlink()
.
cli.ansi
Set to true
, TRUE
or True
to assume a terminal that supports ANSI
control sequences.
Set to anything else to assume a non-ANSI terminal.
See is_ansi_tty()
.
cli.condition_unicode_bullets
TRUE
or FALSE
to force turn on or off the Unicode symbols when printing
conditions. E.g. in format_error()
, format_warning()
, format_message()
and
also in cli_abort()
, cli_warn()
and cli_inform()
.
cli.condition_width
Integer scalar (or Inf
) to set the console width when cli is formatting
errors, warnings or messages in format_error()
, format_warning()
and
format_message()
. When formatting conditions this option takes precedence
over cli.width
.
cli.default_handler
General handler function for all cli conditions. See https://cli.r-lib.org/articles/semantic-cli.html#cli-messages-1
cli.default_num_colors
Default number of ANSI colors. This value is used if the number of colors is not already set by
the cli.num_colors
option,
the R_CLI_NUM_COLORS
environment variable,
the crayon.enabled
and crayon.colors
options,
the NO_COLOR
environment variable,
the knitr.in.progress
option,
a sink()
call for the stream.
You can also use this option if color support is detected correctly, but you want to adjust the number of colors. E.g.
if crayon.enabled
is TRUE
, but crayon.colors
is not,
in Emacs on Windows,
in terminals.
See num_ansi_colors()
. See also the cli.num_colors
option.
cli.dynamic
Set to TRUE
to assume a dynamic terminal, that supports \r
.
Set to anything else to assume a non-dynamic terminal.
See is_dynamic_tty()
.
cli.hide_cursor
Whether the cli status bar should try to hide the cursor on terminals.
Set the FALSE
if the hidden cursor causes issues.
cli.hyperlink
Set to true
, TRUE
or True
to tell cli that the terminal supports
ANSI hyperlinks.
Set to anything else to assume no hyperlink support.
See style_hyperlink()
.
cli.ignore_unknown_rstudio_theme
Set to TRUE
to omit a warning for an unknown RStudio theme in
code_highlight()
.
cli.num_colors
Number of ANSI colors. See num_ansi_colors()
. See also the
cli.default_num_colors
option.
cli.message_class
Character vector of classes to add to cli's conditions.
cli.progress_bar_style
Progress bar style.
See cli_progress_styles()
.
cli.progress_bar_style_ascii
Progress bar style on ASCII consoles.
See cli_progress_styles()
.
cli.progress_bar_style_unicode
Progress bar style on Unicode (UTF-8) consoles;
See cli_progress_styles()
.
cli.progress_clear
Whether to clear terminated progress bar from the screen on dynamic terminals.
See cli_progress_bar()
.
cli.progress_demo_live
Whether cli_progress_demo()
should show a live demo, or just record the
progress bar frames.
cli.progress_format_download
Default format string for download
progress bars.
cli.progress_format_download_nototal
Default format string for download
progress bars with unknown totals.
cli.progress_format_iterator
Default format string for iterator
progress bars.
cli.progress_format_iterator_nototal
Default format string for iterator
progress bars with unknown total number
of progress units.
cli.progress_format_tasks
Default format string for tasks
progress bars.
cli.progress_format_tasks_nototal
Default format string for tasks
progress bars with unknown totals.
cli.progress_handlers
Progress handlers to try.
See cli_progress_builtin_handlers()
.
cli.progress_handlers_force
Progress handlers that will always be used, even if another handler
was already selected.
See cli_progress_builtin_handlers()
.
cli.progress_handlers_only
Progress handlers to force, ignoring handlers set in
cli.progress_handlers
and cli.progress_handlers_force
.
See cli_progress_builtin_handlers()
.
cli.progress_say_args
Command line arguments for the say
progress handlers.
See cli_progress_builtin_handlers()
.
cli.progress_say_command
External command to use in the say
progress handler.
See cli_progress_builtin_handlers()
.
cli.progress_say_frequency
Minimum delay between say
calls in the say
progress handler.
say
ignores very frequent updates, to keep the speech comprehensible.
See cli_progress_builtin_handlers()
.
cli.progress_show_after
Delay before showing a progress bar, in seconds. Progress bars that finish before this delay are not shown at all. cli also shows progress bars that have more than 50% to go after half of this delay has passed.
cli.spinner
Default spinner to use, see get_spinner()
.
cli.spinner_ascii
Default spinner to use on ASCII terminals, see get_spinner()
.
cli.spinner_unicode
Default spinner to use on Unicode terminals, see get_spinner()
.
cli.theme
Default cli theme, in addition to the built-in theme.
This option in intended for the package developers.
See themes and start_app()
.
cli.theme_dark
Whether cli should assume a dark theme for the builtin theme.
See builtin_theme()
.
cli.unicode
Whether to assume a Unicode terminal.
If not set, then it is auto-detected.
See is_utf8_output()
.
cli.user_theme
cli user theme. This option is intended for end users. See themes.
cli.warn_inline_newlines
Whether to emit a warning when cli replaces newline characters with
spaces within a {.class }
inline style.
Defaults to FALSE
.
cli.width
Terminal width to assume.
If not set, then it is auto-detected.
See console_width()
.
rlib_interactive
Whether to assume an interactive R session. If not set, then it is auto-detected.
width
Terminal width.
This is used on some platforms, if cli.width
is not set.
These are environment variables and options are for cli developers, users should not rely on them as they may change between cli releases.
ASCIICAST
Used to detect an asciicast sub-process in RStudio.
ANSICON
Used to detect ANSICON when detecting the number of ANSI colors.
CI
Used to detect if the code is running on a CI. If yes, we avoid ANSI hyperlinks.
CLI_DEBUG_BAD_END
Whether to warn about cli_end()
calls when there is no container to close.
CLI_NO_BUILTIN_THEME
Set it to true
to omit the builtin theme.
CLI_SPEED_TIME
Can be used to speed up cli's timer. It is a factor, e.g. setting it to 2 makes cli's time go twice as fast.
CLI_TICK_TIME
How often the cli timer should alert, in milliseconds.
CMDER_ROOT
Used to detect cmder when detecting the number of ANSI colors.
COLORTERM
Used when detecting ANSI color support.
ConEmuANSI
Used to detect ConEmu when detecting the number of ANSI colors.
EMACS
Used to detect Emacs.
INSIDE_EMACS
Used to detect Emacs.
NOT_CRAN
Set to true
to run tests / examples / checks, that do not run on CRAN.
_R_CHECK_PACKAGE_NAME_
Used to detect R CMD check
.
R_BROWSER
Used to detect the RStudio build pane.
R_GUI_APP_VERSION
Used to detect R.app on macOS, to decide if the console has ANSI control sequences.
R_PACKAGE_DIR
Used to detect if the code is running under R CMD INSTALL
.
R_PDFVIEWER
Used to detect the RStudio build pane.
R_PROGRESS_NO_EXAMPLES
Set to true
to avoid running examples, outside of R CMD check
.
RSTUDIO
Used to detect RStudio, in various functions.
RSTUDIO_CONSOLE_COLOR
Used to detect the number of colors in RStudio.
See num_ansi_colors()
.
RSTUDIO_CONSOLE_WIDTH
Used to auto-detect console width in RStudio.
RSTUDIO_TERM
Used to detect the RStudio build pane.
TEAMCITY_VERSION
Used to detect the TeamCity CI, to turn off ANSI hyperlinks.
TERM
Used to detect if the console has ANSI control sequences, in a terminal.
TERM_PROGRAM
Used to detect iTerm for the dark theme detection and the ANSI hyperlink support detection.
TERM_PROGRAM_VERSION
Used to detect a suitable iTerm version for ANSI hyperlink support.
TESTTHAT
Used to detect running in testthat tests.
VTE_VERSION
Used to detect a suitable VTE version for ANSI hyperlinks.
cli__pb
This option is set to the progress bar that is being updated, when interpolating the format string.
cli.record
Internal option to mark the state that cli is recording messages.
crayon.colors
Deprecated option for the number of ANSI colors, that is still supported
by cli, when the new options are not set.
See num_ansi_colors()
.
crayon.enabled
Deprecated option to turn ANSI colors on/off.
This is still supported by cli when the new options are not set.
See num_ansi_colors()
.
crayon.hyperlink
Whether to assume ANSI hyperlink support.
See ansi_has_hyperlink_support()
.
knitr.in.progress
Used to detect knitr when detecting interactive sessions and ANSI color support.
rstudio.notebook.executing
Used to detect knitr when detecting interactive sessions.
Syntax highlight R code
code_highlight(code, code_theme = NULL, envir = NULL)
code_highlight(code, code_theme = NULL, envir = NULL)
code |
Character vector, each element is one line of code. |
code_theme |
Theme see |
envir |
Environment to look up function calls for hyperlinks.
If |
See code_theme_list()
for the default syntax highlighting theme and
how to change it.
If code
does not parse, then it is returned unchanged and a
cli_parse_failure
condition is thrown. Note that this is not an error,
and the condition is ignored, unless explicitly caught.
Character vector, the highlighted code.
Other syntax highlighting:
code_theme_list()
code_highlight(deparse(ls)) cat(code_highlight(deparse(ls)), sep = "\n")
code_highlight(deparse(ls)) cat(code_highlight(deparse(ls)), sep = "\n")
code_theme_list()
lists the built-in code themes.
code_theme_list()
code_theme_list()
Character vector of the built-in code theme names.
A theme is a list of character vectors, except for bracket
, see below.
Each character vector must contain RGB colors (e.g. "#a9a9a9"
),
and cli styles, e.g. "bold"
. Entries in the list:
reserved
: reserved words
number
: numeric literals
null
: the NULL
constant
operator
: operators, including assignment
call
: function calls
string
: character literals
comment
: comments
bracket
: brackets: (){}[]
This is a list of character vectors,
to create "rainbow" brackets. It is recycled for deeply nested lists.
In RStudio, it matches the current theme of the IDE.
You can use three options to customize the code theme:
If cli.code_theme
is set, it is used.
Otherwise if R is running in RStudio and cli.code_theme_rstudio
is
set, then it is used.
Otherwise if T is not running in RStudio and cli.code_theme_terminal
is set, then it is used.
You can set these options to the name of a built-in theme, or to list
that specifies a custom theme. See code_theme_list()
for the list
of the built-in themes.
Other syntax highlighting:
code_highlight()
code_theme_list() code_highlight(deparse(get), code_theme = "Solarized Dark")
code_theme_list() code_highlight(deparse(get), code_theme = "Solarized Dark")
Combine two or more styles or style functions into a new style function that can be called on strings to style them.
combine_ansi_styles(...)
combine_ansi_styles(...)
... |
The styles to combine. For character strings, the
|
It does not usually make sense to combine two foreground colors (or two background colors), because only the first one applied will be used.
It does make sense to combine different kind of styles, e.g. background color, foreground color, bold font.
The combined style function.
Other ANSI styling:
ansi-styles
,
make_ansi_style()
,
num_ansi_colors()
## Use style names alert <- combine_ansi_styles("bold", "red4") cat(alert("Warning!"), "\n") ## Or style functions alert <- combine_ansi_styles(style_bold, col_red, bg_cyan) cat(alert("Warning!"), "\n") ## Combine a composite style alert <- combine_ansi_styles( "bold", combine_ansi_styles("red", bg_cyan)) cat(alert("Warning!"), "\n")
## Use style names alert <- combine_ansi_styles("bold", "red4") cat(alert("Warning!"), "\n") ## Or style functions alert <- combine_ansi_styles(style_bold, col_red, bg_cyan) cat(alert("Warning!"), "\n") ## Combine a composite style alert <- combine_ansi_styles( "bold", combine_ansi_styles("red", bg_cyan)) cat(alert("Warning!"), "\n")
It uses the cli.width
option, if set. Otherwise it tries to
determine the size of the terminal or console window.
console_width()
console_width()
These are the exact rules:
If the cli.width
option is set to a positive integer, it is used.
If the cli.width
option is set, but it is not a positive integer,
and error is thrown.
Then we try to determine the size of the terminal or console window:
If we are not in RStudio, or we are in an RStudio terminal,
then we try to use the tty_size()
function to query the
terminal size. This might fail if R is not running in a terminal,
but failures are ignored.
If we are in the RStudio build pane, then the RSTUDIO_CONSOLE_WIDTH
environment variable is used. If the build pane is resized, then this
environment variable is not accurate any more, and the output might
get garbled.
We are not using the RSTUDIO_CONSOLE_WIDTH
environment variable
if we are in the RStudio console.
If we cannot determine the size of the terminal or console window, then
we use the width
option. If the width
option is not set, then
we return 80L.
Integer scalar, the console with, in number of characters.
console_width()
console_width()
Container elements may contain other elements. Currently the following
commands create container elements: cli_div()
, cli_par()
, the list
elements: cli_ul()
, cli_ol()
, cli_dl()
, and list items are
containers as well: cli_li()
.
A container can add a new theme, which is removed when the container exits.
d <- cli_div(theme = list(h1 = list(color = "blue", "font-weight" = "bold"))) cli_h1("Custom title") cli_end(d)
#>
#> Custom title
Container elements are closed with cli_end()
. For convenience,
by default they are closed automatically when the function that created
them terminated (either regularly or with an error). The default
behavior can be changed with the .auto_close
argument.
div <- function() { cli_div(class = "tmp", theme = list(.tmp = list(color = "yellow"))) cli_text("This is yellow") } div() cli_text("This is not yellow any more")
#> This is yellow
#> This is not yellow any more
You can use the internal cli:::cli_debug_doc()
function to see the
currently open containers.
fun <- function() { cli_div(id = "mydiv") cli_par(class = "myclass") cli:::cli_debug_doc() } fun()
#> #> <cli document> #> <body id="body"> #> <div id="mydiv"> +theme #> <par id="cli-82040-226" class="myclass">
Each spinner is shown for about 2-3 seconds.
demo_spinners(which = NULL)
demo_spinners(which = NULL)
which |
Character vector, which spinners to demo. |
demo_spinners("clock")
Other spinners:
get_spinner()
,
list_spinners()
,
make_spinner()
Its printed output is similar to calling diff -u
at the command
line.
diff_chr(old, new, max_dist = Inf)
diff_chr(old, new, max_dist = Inf)
old |
First character vector. |
new |
Second character vector. |
max_dist |
Maximum distance to consider, or |
A list that is a cli_diff_chr
object, with a format()
and a
print()
method. You can also access its members:
old
and new
are the original inputs,
lcs
is a data frame of LCS edit that transform old
into new
.
The lcs
data frame has the following columns:
operation
: one of "match"
, "delete"
or "insert"
.
offset
: offset in old
for matches and deletions, offset in new
for insertions.
length
: length of the operation, i.e. number of matching, deleted
or inserted elements.
old_offset
: offset in old
after the operation.
new_offset
: offset in new
after the operation.
The diffobj package for a much more comprehensive set of
diff
-like tools.
Other diff functions in cli:
diff_str()
letters2 <- c("P", "R", "E", letters, "P", "O", "S", "T") letters2[11:16] <- c("M", "I", "D", "D", "L", "E") diff_chr(letters, letters2)
letters2 <- c("P", "R", "E", letters, "P", "O", "S", "T") letters2[11:16] <- c("M", "I", "D", "D", "L", "E") diff_chr(letters, letters2)
Characters are defined by UTF-8 graphemes.
diff_str(old, new, max_dist = Inf)
diff_str(old, new, max_dist = Inf)
old |
First string, must not be |
new |
Second string, must not be |
max_dist |
Maximum distance to consider, or |
A list that is a cli_diff_str
object and also a
cli_diff_chr
object, see diff_str for the details about its
structure.
The diffobj package for a much more comprehensive set of
diff
-like tools.
Other diff functions in cli:
diff_chr()
str1 <- "abcdefghijklmnopqrstuvwxyz" str2 <- "PREabcdefgMIDDLEnopqrstuvwxyzPOST" diff_str(str1, str2)
str1 <- "abcdefghijklmnopqrstuvwxyz" str2 <- "PREabcdefgMIDDLEnopqrstuvwxyzPOST" diff_str(str1, str2)
Frequently Asked Questions
It is probably a mistake in the ANSI support detection algorithm. Please open an issue at https://github.com/r-lib/cli/issues and do not forget to tell us the details of your platform and terminal or GUI.
Set the NO_COLOR
environment variable to a non-empty value. You can do
this in your .Renviron
file (use usethis::edit_r_environ()
).
If you want to do this for testthat tests, then consider using the 3rd
edition on testthat, which does turn off ANSI styling automatically
inside test_that()
.
file.choose()
Try calling flush.console()
to flush the console, before
file.choose()
. If flushing does not work and you are in RStudio, then
it is probably this RStudio bug:
https://github.com/rstudio/rstudio/issues/8040 See more details at
https://github.com/r-lib/cli/issues/151
The display width of some Unicode characters ambiguous in the Unicode standard. Some software treats them as narrow (one column on the screen), other as wide (two columns). In some terminal emulators (for example iTerm2), you can configure the preferred behavior.
Unfortunately the box drawing characters that cli uses also have ambiguous width.
In RStudio the behavior depends on the font. In particular, Consolas, Courier and Inconsolata treats them as wide characters, so cli output will not look great with these. Some good, modern fonts that look good include Menlo, Fira Code and Source Code Pro.
If you do not want to change your font, you can also turn off Unicode
output, by setting the cli.unicode
option:
options(cli.unicode = FALSE)
A related issue: https://github.com/r-lib/cli/issues/320
In modern terminals, cli output usually looks good.
If you see too wide heading separators in RStudio, then see the previous question: Why are heading separators wider than my screen in RStudio?.
If some output is garbled, then cli probably misdetected Unicode support for your terminal or font. You can try choosing a different font. In our experience output looks good with Menlo, Fira Code and Source Code Pro. Alternatively you can turn off Unicode output:
options(cli.unicode = FALSE)
If you think this is our fault, then please also file an issue at https://github.com/r-lib/cli/issues
You can then throw this message with stop()
or rlang::abort()
.
format_error(message, .envir = parent.frame()) format_warning(message, .envir = parent.frame()) format_message(message, .envir = parent.frame())
format_error(message, .envir = parent.frame()) format_warning(message, .envir = parent.frame()) format_message(message, .envir = parent.frame())
message |
It is formatted via a call to |
.envir |
Environment to evaluate the glue expressions in. |
The messages can use inline styling, pluralization and glue substitutions.
n <- "boo" stop(format_error(c( "{.var n} must be a numeric vector", "x" = "You've supplied a {.cls {class(n)}} vector." )))
#> Error: `n` must be a numeric vector #> ✖ You've supplied a <character> vector.
len <- 26 idx <- 100 stop(format_error(c( "Must index an existing element:", "i" = "There {?is/are} {len} element{?s}.", "x" = "You've tried to subset element {idx}." )))
#> Error: Must index an existing element: #> ℹ There are 26 elements. #> ✖ You've tried to subset element 100.
These functions support inline markup.
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_inline()
You can use this function to format a line of cli text, without emitting
it to the screen. It uses cli_text()
internally.
format_inline( ..., .envir = parent.frame(), collapse = TRUE, keep_whitespace = TRUE )
format_inline( ..., .envir = parent.frame(), collapse = TRUE, keep_whitespace = TRUE )
... |
Passed to |
.envir |
Environment to evaluate the expressions in. |
collapse |
Whether to collapse the result if it has multiple
lines, e.g. because of |
keep_whitespace |
Whether to keep all whitepace (spaces, newlines and form feeds) as is in the input. |
format_inline()
performs no width-wrapping.
Character scalar, the formatted string.
This function supports inline markup.
Other functions supporting inline markup:
cli_abort()
,
cli_alert()
,
cli_blockquote()
,
cli_bullets()
,
cli_bullets_raw()
,
cli_dl()
,
cli_h1()
,
cli_li()
,
cli_ol()
,
cli_process_start()
,
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_message()
,
cli_progress_output()
,
cli_progress_step()
,
cli_rule
,
cli_status()
,
cli_status_update()
,
cli_text()
,
cli_ul()
,
format_error()
format_inline("A message for {.emph later}, thanks {.fn format_inline}.")
format_inline("A message for {.emph later}, thanks {.fn format_inline}.")
cli
contains many different spinners, you choose one according to your
taste.
get_spinner(which = NULL)
get_spinner(which = NULL)
which |
The name of the chosen spinner. If |
options(cli.spinner = "hearts") fun <- function() { cli_progress_bar("Spinning") for (i in 1:100) { Sys.sleep(4/100) cli_progress_update() } } fun() options(cli.spinner = NULL)
A list with entries: name
, interval
: the suggested update
interval in milliseconds and frames
: the character vector of the
spinner's frames.
Other spinners:
demo_spinners()
,
list_spinners()
,
make_spinner()
Check if the current platform/terminal supports reading single keys.
has_keypress_support()
has_keypress_support()
Supported platforms:
Terminals in Windows and Unix.
RStudio terminal.
Not supported:
RStudio (if not in the RStudio terminal).
R.app on macOS.
Rgui on Windows.
Emacs ESS.
Others.
Whether there is support for waiting for individual keypressses.
Other keypress function:
keypress()
has_keypress_support()
has_keypress_support()
Adjective-animal hash
hash_animal(x, n_adj = 2) hash_raw_animal(x, n_adj = 2) hash_obj_animal(x, n_adj = 2, serialize_version = 2)
hash_animal(x, n_adj = 2) hash_raw_animal(x, n_adj = 2) hash_obj_animal(x, n_adj = 2, serialize_version = 2)
x |
Character vector. |
n_adj |
Number of adjectives to use. It must be from 0 through 3. |
serialize_version |
Workspace format version to use, see
|
It uses the first 13 hexadecimal characters (out of the 32) of the MD5 hash of the input, and converts them into an adjective-animal form to create a human readable hash.
hash_animal()
uses 1748 animal names and
8946 different adjectives. The number of
different hashes you can get for different values of n_adj
:
n_adj |
size of the hash table space |
0 | 1,748 |
1 | 15,637,608 |
2 | 139,894,041,168 |
3 | 1,251,492,092,288,928 |
The list of adjectives and animals comes from the ids package,
and in turn from
https://github.com/a-type/adjective-adjective-animal, and
from https://gfycat.com
(now gone).
hash_raw_animal()
calculates the adjective-animal hash of
the bytes of a raw vector.
hash_obj_animal()
calculates the adjective-animal hash of
an R object. The object is serialized into a binary vector first.
A data frame with columns
hash
: the hash value, a string.
words
: list column with the adjectives and the animal name in a
character vector.
hash_raw_animal()
and hash_obj_animal()
return a list
with entries:
hash
: the hash value, a string,
'words: the adjectives and the animal name in a character vector.
the ids package for generating random adjective-animal ids
Other hash functions:
hash_emoji()
,
hash_md5()
,
hash_sha1()
,
hash_sha256()
,
hash_xxhash()
hash_animal(c("foo", "bar")) # if you increase `n_adj`, the shorter hash is a suffix of the longer: hash_animal("cli package", 0)$hash hash_animal("cli package", 1)$hash hash_animal("cli package", 2)$hash hash_animal("cli package", 3)$hash
hash_animal(c("foo", "bar")) # if you increase `n_adj`, the shorter hash is a suffix of the longer: hash_animal("cli package", 0)$hash hash_animal("cli package", 1)$hash hash_animal("cli package", 2)$hash hash_animal("cli package", 3)$hash
Emoji hash
hash_emoji(x, size = 3) hash_raw_emoji(x, size = 3) hash_obj_emoji(x, size = 3, serialize_version = 2)
hash_emoji(x, size = 3) hash_raw_emoji(x, size = 3) hash_obj_emoji(x, size = 3, serialize_version = 2)
x |
Character vector. |
size |
Number of emojis to use in a hash. Currently it has to be from 1 through 4. |
serialize_version |
Workspace format version to use, see
|
It uses the first 13 hexadecimal characters (out of the 32) of the MD5 hash of the input, and converts them into an emoji representation. It uses a manually selected subset of all emojis, that tend to be displayed correctly.
cli uses 2280 possible emojis. This is the number of
different hashes you can get for different values of size
:
size |
size of hash table space |
1 | 2,280 |
2 | 5,198,400 |
3 | 11,852,352,000 |
4 | 27,023,362,560,000 |
hash_raw_emoji()
calculates the emoji hash of the bytes
of a raw vector.
hash_obj_emoji()
calculates the emoji hash of an R
object. The object is serialized into a binary vector first.
hash_emoji()
returns a data frame with columns
hash
: the emoji hash, a string of the requested size.
emojis
: list column with the emoji characters in character
vectors. Note that an emoji might have multiple code points.
text
: text representation of hash
, comma separated.
names
: list column with the text representations of emojis
, in
character vectors.
hash_raw_emoji()
and hash_obj_emoji()
return a list with
entries:
hash
: the emoji hash, a string of requested size,
emojis
: the individual emoji characters in a character vector,
text
: text representation of hash
, comma separated,
names
: names of the emojis, in a character vector.
the emoji package for a comprehensive list of emojis
Other hash functions:
hash_animal()
,
hash_md5()
,
hash_sha1()
,
hash_sha256()
,
hash_xxhash()
hash_emoji(c("foo", NA, "bar", ""))$text # if you increase `size`, the shorter hash is a prefix of the longer: hash_emoji("foobar", 1)$text hash_emoji("foobar", 2)$text hash_emoji("foobar", 3)$text hash_emoji("foobar", 4)$text
hash_emoji(c("foo", NA, "bar", ""))$text # if you increase `size`, the shorter hash is a prefix of the longer: hash_emoji("foobar", 1)$text hash_emoji("foobar", 2)$text hash_emoji("foobar", 3)$text hash_emoji("foobar", 4)$text
Calculate the MD5 hash of each element of a character vector.
hash_md5(x) hash_raw_md5(x) hash_obj_md5(x, serialize_version = 2) hash_file_md5(paths)
hash_md5(x) hash_raw_md5(x) hash_obj_md5(x, serialize_version = 2) hash_file_md5(paths)
x |
Character vector. If not a character vector, then
|
serialize_version |
Workspace format version to use, see
|
paths |
Character vector of file names. |
hash_raw_md5()
calculates the MD5 hash of the bytes
of a raw vector.
hash_obj_md5()
calculates the MD5 hash of an R
object. The object is serialized into a binary vector first.
hash_file_md5()
calculates the MD5 hash of one or more
files.
hash_md5()
returns a character vector of hexadecimal MD5
hashes.
hash_raw_md5()
returns a character scalar.
hash_obj_md5()
returns a character scalar.
tools::md5sum()
for a base R MD5 function that works on
files.
Other hash functions:
hash_animal()
,
hash_emoji()
,
hash_sha1()
,
hash_sha256()
,
hash_xxhash()
hash_md5(c("foo", NA, "bar", ""))
hash_md5(c("foo", NA, "bar", ""))
Calculate the SHA-1 hash of each element of a character vector.
hash_sha1(x) hash_raw_sha1(x) hash_obj_sha1(x, serialize_version = 2) hash_file_sha1(paths)
hash_sha1(x) hash_raw_sha1(x) hash_obj_sha1(x, serialize_version = 2) hash_file_sha1(paths)
x |
Character vector. If not a character vector, then
|
serialize_version |
Workspace format version to use, see
|
paths |
Character vector of file names. |
hash_raw_sha1()
calculates the SHA-1 hash of the bytes
of a raw vector.
hash_obj_sha1()
calculates the SHA-1 hash of an R
object. The object is serialized into a binary vector first.
hash_file_sha1()
calculates the SHA-1 hash of one or
more files.
hash_sha1()
returns a character vector of hexadecimal
SHA-1 hashes.
hash_raw_sha1()
returns a character scalar.
hash_obj_sha1()
returns a character scalar.
hash_file_sha1()
returns a character vector of SHA-1
hashes.
Other hash functions:
hash_animal()
,
hash_emoji()
,
hash_md5()
,
hash_sha256()
,
hash_xxhash()
hash_sha1(c("foo", NA, "bar", ""))
hash_sha1(c("foo", NA, "bar", ""))
Calculate the SHA-256 hash of each element of a character vector.
hash_sha256(x) hash_raw_sha256(x) hash_obj_sha256(x, serialize_version = 2) hash_file_sha256(paths)
hash_sha256(x) hash_raw_sha256(x) hash_obj_sha256(x, serialize_version = 2) hash_file_sha256(paths)
x |
Character vector. If not a character vector, then
|
serialize_version |
Workspace format version to use, see
|
paths |
Character vector of file names. |
hash_raw_sha256()
calculates the SHA-256 hash of the bytes
of a raw vector.
hash_obj_sha256()
calculates the SHA-256 hash of an R
object. The object is serialized into a binary vector first.
hash_file_sha256()
calculates the SHA-256 hash of one or
more files.
hash_sha256()
returns a character vector of hexadecimal
SHA-256 hashes.
hash_raw_sha256()
returns a character scalar.
hash_obj_sha256()
returns a character scalar.
hash_file_sha256()
returns a character vector of SHA-256
hashes.
Other hash functions:
hash_animal()
,
hash_emoji()
,
hash_md5()
,
hash_sha1()
,
hash_xxhash()
hash_sha256(c("foo", NA, "bar", ""))
hash_sha256(c("foo", NA, "bar", ""))
Extremely fast hash algorithm.
hash_xxhash(x) hash_raw_xxhash(x) hash_obj_xxhash(x, serialize_version = 2) hash_file_xxhash(paths) hash_xxhash64(x) hash_raw_xxhash64(x) hash_obj_xxhash64(x, serialize_version = 2) hash_file_xxhash64(paths)
hash_xxhash(x) hash_raw_xxhash(x) hash_obj_xxhash(x, serialize_version = 2) hash_file_xxhash(paths) hash_xxhash64(x) hash_raw_xxhash64(x) hash_obj_xxhash64(x, serialize_version = 2) hash_file_xxhash64(paths)
x |
Character vector. If not a character vector, then
|
serialize_version |
Workspace format version to use, see
|
paths |
Character vector of file names. |
hash_raw_xxhash()
calculates the xxHash hash of the bytes
of a raw vector.
hash_obj_xxhash()
calculates the xxHash hash of an R
object. The object is serialized into a binary vector first.
hash_file_xxhash()
calculates the xxHash hash of one or
more files.
The 64
functions caculate the 64 bit variant
of xxHash. Otherwise they work the same.
hash_xxhash()
returns a character vector of hexadecimal
xxHash hashes.
hash_raw_xxhash()
returns a character scalar.
hash_obj_xxhash()
returns a character scalar.
hash_file_xxhash()
returns a character vector of xxHash
hashes.
Other hash functions:
hash_animal()
,
hash_emoji()
,
hash_md5()
,
hash_sha1()
,
hash_sha256()
hash_xxhash(c("foo", NA, "bar", ""))
hash_xxhash(c("foo", NA, "bar", ""))
To learn how to use cli’s semantic markup, start with the ‘Building a semantic CLI’ article at https://cli.r-lib.org.
All text emitted by cli supports glue interpolation. Expressions
enclosed by braces will be evaluated as R code. See glue::glue()
for
details.
In addition to regular glue interpolation, cli can also add classes to parts of the text, and these classes can be used in themes. For example
cli_text("This is {.emph important}.")
#> This is important.
adds a class to the "important" word, class "emph"
. Note that in this
case the string within the braces is usually not a valid R expression.
If you want to mix classes with interpolation, add another pair of
braces:
adjective <- "great" cli_text("This is {.emph {adjective}}.")
#> This is great.
An inline class will always create a span
element internally. So in
themes, you can use the span.emph
CSS selector to change how inline
text is emphasized:
cli_div(theme = list(span.emph = list(color = "red"))) adjective <- "nice and red" cli_text("This is {.emph {adjective}}.")
#> This is nice and red.
The default theme defines the following inline classes:
arg
for a function argument.
cls
for an S3, S4, R6 or other class name.
code
for a piece of code.
dt
is used for the terms in a definition list (cli_dl()
).
dd
is used for the descriptions in a definition list (cli_dl()
).
email
for an email address.
If the terminal supports ANSI hyperlinks (e.g. RStudio, iTerm2, etc.),
then cli creates a clickable link.
See links for more information about cli hyperlinks.
emph
for emphasized text.
envvar
for the name of an environment variable.
field
for a generic field, e.g. in a named list.
file
for a file name. If the terminal supports ANSI hyperlinks (e.g.
RStudio, iTerm2, etc.), then cli creates a clickable link that opens
the file in RStudio or with the default app for the file type.
See links for more information about cli hyperlinks.
fn
for a function name. If it is in the package::function_name
form, and the terminal supports ANSI hyperlinks (e.g. RStudio,
iTerm2, etc.), then cli creates a clickable link.
See links for more information about cli hyperlinks.
fun
same as fn
.
help
is a help page of a function.
If the terminal supports ANSI hyperlinks to help pages (e.g. RStudio),
then cli creates a clickable link. It supports link text.
See links for more information about cli hyperlinks.
href
creates a hyperlink, potentially with a link text.
If the terminal supports ANSI hyperlinks (e.g. RStudio, iTerm2, etc.),
then cli creates a clickable link.
See links for more information about cli hyperlinks.
kbd
for a keyboard key.
key
same as kbd
.
obj_type_friendly
formats the type of an R object in a readable way,
and it should be used with {}
, see an example below.
or
changes the string that separates the last two elements of
collapsed vectors (see below) from "and" to "or".
path
for a path (the same as file
in the default theme).
pkg
for a package name.
run
is an R expression, that is potentially clickable if the terminal
supports ANSI hyperlinks to runnable code (e.g. RStudio).
It supports link text. See links for more information about cli hyperlinks.
str
for a double quoted string escaped by base::encodeString()
.
strong
for strong importance.
topic
is a help page of a topic.
If the terminal supports ANSI hyperlinks to help pages (e.g. RStudio),
then cli creates a clickable link. It supports link text.
See links for more information about cli hyperlinks.
type
formats the type of an R object in a readable way, and it
should be used with {}
, see an example below.
url
for a URL. If the terminal supports ANSI hyperlinks (e.g.
RStudio, iTerm2, etc.), then cli creates a clickable link.
See links for more information about cli hyperlinks.
var
for a variable name.
val
for a generic "value".
vignette
is a vignette.
If the terminal supports ANSI hyperlinks to help pages (e.g. RStudio),
then cli creates a clickable link. It supports link text.
See links for more information about cli hyperlinks.
ul <- cli_ul() cli_li("{.emph Emphasized} text.") cli_li("{.strong Strong} importance.") cli_li("A piece of code: {.code sum(a) / length(a)}.") cli_li("A package name: {.pkg cli}.") cli_li("A function name: {.fn cli_text}.") cli_li("A keyboard key: press {.kbd ENTER}.") cli_li("A file name: {.file /usr/bin/env}.") cli_li("An email address: {.email [email protected]}.") cli_li("A URL: {.url https://example.com}.") cli_li("An environment variable: {.envvar R_LIBS}.") cli_li("`mtcars` is {.obj_type_friendly {mtcars}}") cli_end(ul)
#> • Emphasized text. #> • Strong importance. #> • A piece of code: `sum(a) / length(a)`. #> • A package name: cli. #> • A function name: `cli_text()`. #> • A keyboard key: press [ENTER]. #> • A file name: /usr/bin/env. #> • An email address: [email protected]. #> • A URL: <https://example.com>. #> • An environment variable: `R_LIBS`. #> • `mtcars` is a data frame
You can add new classes by defining them in the theme, and then using them.
cli_div(theme = list( span.myclass = list(color = "lightgrey"), "span.myclass" = list(before = "<<"), "span.myclass" = list(after = ">>"))) cli_text("This is {.myclass in angle brackets}.") cli_end()
#> This is <<in angle brackets>>.
Often it is useful to highlight a weird file or path name, e.g. one
that starts or ends with space characters. The built-in theme does this
for .file
, .path
and .email
by default. You can highlight
any string inline by adding the .q
class to it.
The current highlighting algorithm
adds single quotes to the string if it does not start or end with an alphanumeric character, underscore, dot or forward slash.
Highlights the background colors of leading and trailing spaces on terminals that support ANSI colors.
When cli performs inline text formatting, it automatically collapses glue substitutions, after formatting. This is handy to create lists of files, packages, etc.
pkgs <- c("pkg1", "pkg2", "pkg3") cli_text("Packages: {pkgs}.") cli_text("Packages: {.pkg {pkgs}}.")
#> Packages: pkg1, pkg2, and pkg3. #> Packages: pkg1, pkg2, and pkg3.
Class names are collapsed differently by default
x <- Sys.time() cli_text("Hey, {.var x} has class {.cls {class(x)}}.")
#> Hey, `x` has class <POSIXct/POSIXt>.
By default cli truncates long vectors. The truncation limit is by default
twenty elements, but you can change it with the vec-trunc
style.
nms <- cli_vec(names(mtcars), list("vec-trunc" = 5)) cli_text("Column names: {nms}.")
#> Column names: mpg, cyl, disp, …, gear, and carb.
The val
inline class formats values. By default (c.f. the built-in
theme), it calls the cli_format()
generic function, with the current
style as the argument. See cli_format()
for examples.
str
is for formatting strings, it uses base::encodeString()
with
double quotes.
{
and }
It might happen that you want to pass a string to cli_*
functions,
and you do not want command substitution in that string, because it
might contain {
and }
characters. The simplest solution for this is
to refer to the string from a template:
msg <- "Error in if (ncol(dat$y)) {: argument is of length zero" cli_alert_warning("{msg}")
#> ! Error in if (ncol(dat$y)) {: argument is of length zero
If you want to explicitly escape {
and }
characters, just double
them:
cli_alert_warning("A warning with {{ braces }}.")
#> ! A warning with { braces }.
See also examples below.
All cli commands that emit text support pluralization. Some examples:
ndirs <- 1 nfiles <- 13 pkgs <- c("pkg1", "pkg2", "pkg3") cli_alert_info("Found {ndirs} director{?y/ies} and {nfiles} file{?s}.") cli_text("Will install {length(pkgs)} package{?s}: {.pkg {pkgs}}")
#> ℹ Found 1 directory and 13 files. #> Will install 3 packages: pkg1, pkg2, and pkg3
See pluralization for details.
Most cli containers wrap the text to width the container's width, while observing margins requested by the theme.
To avoid a line break, you can use the UTF_8 non-breaking space
character: \u00a0
. cli will not break a line here.
To force a line break, insert a form feed character: \f
or
\u000c
. cli will insert a line break there.
We check that all of the following hold:
The stream is a terminal.
The platform is Unix.
R is not running inside R.app (the macOS GUI).
R is not running inside RStudio.
R is not running inside Emacs.
The terminal is not "dumb".
stream
is either the standard output or the standard error stream.
is_ansi_tty(stream = "auto")
is_ansi_tty(stream = "auto")
stream |
The stream to inspect or manipulate, an R connection
object. It can also be a string, one of |
TRUE
or FALSE
.
Other terminal capabilities:
ansi_hide_cursor()
,
is_dynamic_tty()
is_ansi_tty()
is_ansi_tty()
\\r
(Carriage return)In a terminal, \\r
moves the cursor to the first position of the
same line. It is also supported by most R IDEs. \\r
is typically
used to achieve a more dynamic, less cluttered user interface, e.g.
to create progress bars.
is_dynamic_tty(stream = "auto")
is_dynamic_tty(stream = "auto")
stream |
The stream to inspect or manipulate, an R connection
object. It can also be a string, one of |
If the output is directed to a file, then \\r
characters are typically
unwanted. This function detects if \\r
can be used for the given
stream or not.
The detection mechanism is as follows:
If the cli.dynamic
option is set to TRUE
, TRUE
is returned.
If the cli.dynamic
option is set to anything else, FALSE
is
returned.
If the R_CLI_DYNAMIC
environment variable is not empty and set to
the string "true"
, "TRUE"
or "True"
, TRUE
is returned.
If R_CLI_DYNAMIC
is not empty and set to anything else, FALSE
is
returned.
If the stream is a terminal, then TRUE
is returned.
If the stream is the standard output or error within RStudio,
the macOS R app, or RKWard IDE, TRUE
is returned.
Otherwise FALSE
is returned.
Other terminal capabilities:
ansi_hide_cursor()
,
is_ansi_tty()
is_dynamic_tty() is_dynamic_tty(stdout())
is_dynamic_tty() is_dynamic_tty(stdout())
UTF-8 cli characters can be turned on by setting the cli.unicode
option to TRUE
. They can be turned off by setting if to FALSE
.
If this option is not set, then base::l10n_info()
is used to detect
UTF-8 support.
is_utf8_output()
is_utf8_output()
Flag, whether cli uses UTF-8 characters.
It currently only works at Linux/Unix and OSX terminals,
and at the Windows command line. see has_keypress_support
.
keypress(block = TRUE)
keypress(block = TRUE)
block |
Whether to wait for a key press, if there is none available now. |
The following special keys are supported:
Arrow keys: 'up', 'down', 'right', 'left'.
Function keys: from 'f1' to 'f12'.
Others: 'home', 'end', 'insert', 'delete', 'pageup', 'pagedown', 'tab', 'enter', 'backspace' (same as 'delete' on OSX keyboards), 'escape'.
Control with one of the following keys: 'a', 'b', 'c', 'd', 'e', 'f', 'h', 'k', 'l', 'n', 'p', 't', 'u', 'w'.
The key pressed, a character scalar. For non-blocking reads
NA
is returned if no keys are available.
Other keypress function:
has_keypress_support()
x <- keypress() cat("You pressed key", x, "\n")
x <- keypress() cat("You pressed key", x, "\n")
Certain cli styles create clickable links, if your IDE or terminal supports them.
The details of the styles that create hyperlinks will prrobably change in the near future, based on user feedback.
The hyperlinks that are included in this manual are demonstrative
only, except for the https:
links. They look like a hyperlink, and
you can click on them, but they do nothing. I.e. a .run
link will
not run the linked expression if you click on it.
As of today, the latest release of RStudio (version v2022.07.0+548)
supports all hyperlink types discussed here. Certain terminals, e.g.
iTerm on macOS, Linux terminals based on VTE (GNOME terminal) support
.href
, .email
and .file
links.
You can use ansi_has_hyperlink_support()
to check if your terminal or
IDE has hyperlink support in general, and ansi_hyperlink_types()
to
check if various types of hyperlinks are supported.
If your hyperlink support is not detected properly in your IDE or terminal, please open a cli issue at https://github.com/r-lib/cli/issues.
Before we delve into the various types of hyperlinks, a general comment about link texts. Some link styles support a custom link text:
.href
.help
.topic
.vignette
.run
Others, i.e. .email
, .file
, .fun
and .url
do not support custom
link text.
The generic syntax for link text is the same as for Markdown hyperlinks:
{.style [link text](url)}
Note that it is not possible to add link text to a vector of URLs. E.g. this will create a list of three URLs, all clickable:
urls <- paste0("https://httpbin.org/status/", c(200, 403, 404)) cli::cli_text("Some httpbin URLs: {.url {urls}}.")
#> Some httpbin URLs: <https://httpbin.org/status/200>, #> <https://httpbin.org/status/403>, and #> <https://httpbin.org/status/404>.
If ANSI hyperlinks are not available, then the link text for of these styles outputs both the link text and the URL in a (hopefully) helpful way. See examples below.
There are two cli styles to link to generic URLs. .url
does not
allow custom link text, but \href
does.
cli_text( "See the cli homepage at {.url https://cli.r-lib.org} for details." )
#> See the cli homepage at <https://cli.r-lib.org> for details.
cli_text( "See the {.href [cli homepage](https://cli.r-lib.org)} for details." )
#> See the cli homepage for details.
This is how these links look without hyperlink support:
local({ withr::local_options(cli.hyperlink = FALSE) cli_text( "See the cli homepage at {.url https://cli.r-lib.org} for details." ) cli_text( "See the {.href [cli homepage](https://cli.r-lib.org)} for details." ) })
#> See the cli homepage at <https://cli.r-lib.org> for details. #> See the cli homepage (<https://cli.r-lib.org>) for details.
Note that cli does not encode the url, so you might need to call
utils::URLencode()
on it, especially, if it is substituted in
via {}
.
weirdurl <- utils::URLencode("https://example.com/has some spaces") cli_text("See more at {.url {weirdurl}}.")
#> See more at <https://example.com/has%20some%20spaces>.
The .file
style now automatically creates a file:
hyperlink.
Because file:
hyperlinks must contain an absolute path, cli tries to
convert relative paths, and paths starting with ~
to aboslute path.
cli_text("... edit your {.file ~/.Rprofile} file.}")
#> ... edit your ~/.Rprofile file.}
.file
cannot use a custom link text. If you custom link text, then
you can use .href
with a file:
URL.
prof <- path.expand("~/.Rprofile") cli_text("... edit your {.href [R profile](file://{prof})}.")
#> ... edit your R profile.
You may add a line number to a file name, separated by :
. Handlers
typically place the cursor at that line after opening the file.
You may also add a column number, after the line number, separated by
another :
.
cli_text("... see line 5 in {.file ~/.Rprofile:5}.")
#> ... see line 5 in ~/.Rprofile:5.
In RStudio file:
URLs open within RStudio. If you click on a file
link outside of RStudio, typically the operating system is consulted
for the application to open it.
One issue with using .href
file files is that it does not look great
if hyperlinks are not available. This will be improved in the future:
local({ withr::local_options(cli.hyperlink = FALSE) prof <- path.expand("~/.Rprofile") cli_text("... edit your {.href [R profile](file://{prof})}.") })
#> ... edit your R profile (<file:///Users/gaborcsardi/.Rprofile>).
.fun
automatically creates links to the manual page of the function,
provided the function name is in the packagename::functionname
form:
cli::cli_text("... see {.fun stats::lm} to learn more.")
#> ... see `stats::lm()` to learn more.
For a custom link text, use .help
instead of .fun
.
cli::cli_text("... see {.help [{.fun lm}](stats::lm)} to learn more.")
#> ... see `lm()` to learn more.
The same message without hyperlink support looks like this:
local({ withr::local_options(cli.hyperlink = FALSE) cli::cli_text("... see {.help [{.fun lm}](stats::lm)} to learn more.") })
#> ... see `lm()` (`?stats::lm()`) to learn more.
To link to a help topic that is not a function, use .topic
:
cli::cli_text("... the tibble options at {.topic tibble::tibble_options}.")
#> ... the tibble options at tibble::tibble_options.
.topic
support link text.
To link to a vignette, use .vignette
:
cli::cli_text("... see the {.vignette tibble::types} vignette.")
#> ... see the tibble::types vignette.
RStudio also supports a special link type that runs R code in the current R session upon clicking.
You can create these links with .run
:
cli::cli_text("Run {.run testthat::snapshot_review()} to review")
#> Run testthat::snapshot_review() to review
Sometimes you want to show a slightly different expression in the link,
than the one that is evaluated. E.g. the evaluated expression probably
needs to qualify packages with ::
, but you might not want to show this:
cli::cli_text( "Run {.run [snapshot_review()](testthat::snapshot_review())} to review" )
#> Run snapshot_review() to review
To make .run
hyperlinks more secure, RStudio will not run code
that is not in the pkg::fun(args)
form,
if args
contains (
, )
or ;
,
if it calls a core package (base, stats, etc.),
if it calls a package that is not loaded, and it is not one of testthat, devtools, usethis, rlang, pkgload, or pkgdown which are explicitly allowed.
When RStudio does not run a .run
hyperlink, then it shows the code
and the user can copy and paste it to the console, if they consider
it safe to run.
Note that depending on your version of RStudio, the behavior can change.
Draw a banner-like box in the console
list_border_styles() boxx( label, header = "", footer = "", border_style = "single", padding = 1, margin = 0, float = c("left", "center", "right"), col = NULL, background_col = NULL, border_col = col, align = c("left", "center", "right"), width = console_width() )
list_border_styles() boxx( label, header = "", footer = "", border_style = "single", padding = 1, margin = 0, float = c("left", "center", "right"), col = NULL, background_col = NULL, border_col = col, align = c("left", "center", "right"), width = console_width() )
label |
Label to show, a character vector. Each element will be
in a new line. You can color it using the |
header |
Text to show on top border of the box. If too long, it will be cut. |
footer |
Text to show on the bottom border of the box. If too long, it will be cut. |
border_style |
String that specifies the border style.
|
padding |
Padding within the box. Either an integer vector of
four numbers (bottom, left, top, right), or a single number |
margin |
Margin around the box. Either an integer vector of four
numbers (bottom, left, top, right), or a single number |
float |
Whether to display the box on the |
col |
Color of text, and default border color. Either a style
function (see ANSI styles) or a color name that is
passed to |
background_col |
Background color of the inside of the box.
Either a style function (see ANSI styles), or a color
name which will be used in |
border_col |
Color of the border. Either a style function
(see ANSI styles) or a color name that is passed to
|
align |
Alignment of the label within the box: |
width |
Width of the screen, defaults to |
boxx("Hello there!")
#> ┌──────────────────┐ #> │ │ #> │ Hello there! │ #> │ │ #> └──────────────────┘
boxx("Hello there!", border_style = "double")
#> ╔══════════════════╗ #> ║ ║ #> ║ Hello there! ║ #> ║ ║ #> ╚══════════════════╝
boxx(c("Hello", "there!"), padding = 1)
#> ┌────────────┐ #> │ │ #> │ Hello │ #> │ there! │ #> │ │ #> └────────────┘
boxx("Hello there!", padding = 1) boxx("Hello there!", padding = c(1, 5, 1, 5))
#> ┌──────────────────┐ #> │ │ #> │ Hello there! │ #> │ │ #> └──────────────────┘ #> ┌──────────────────────┐ #> │ │ #> │ Hello there! │ #> │ │ #> └──────────────────────┘
boxx("Hello there!", padding = 1, float = "center") boxx("Hello there!", padding = 1, float = "right")
#> ┌──────────────────┐ #> │ │ #> │ Hello there! │ #> │ │ #> └──────────────────┘ #> ┌──────────────────┐ #> │ │ #> │ Hello there! │ #> │ │ #> └──────────────────┘
boxx(col_cyan("Hello there!"), padding = 1, float = "center")
#> ┌──────────────────┐
#> │ │
#> │ Hello there! │
#> │ │
#> └──────────────────┘
boxx("Hello there!", padding = 1, background_col = "brown") boxx("Hello there!", padding = 1, background_col = bg_red)
#> ┌──────────────────┐ #> │ │ #> │ Hello there! │ #> │ │ #> └──────────────────┘ #> ┌──────────────────┐ #> │ │ #> │ Hello there! │ #> │ │ #> └──────────────────┘
boxx("Hello there!", padding = 1, border_col = "green") boxx("Hello there!", padding = 1, border_col = col_red)
#> ┌──────────────────┐ #> │ │ #> │ Hello there! │ #> │ │ #> └──────────────────┘ #> ┌──────────────────┐ #> │ │ #> │ Hello there! │ #> │ │ #> └──────────────────┘
boxx(c("Hi", "there", "you!"), padding = 1, align = "left") boxx(c("Hi", "there", "you!"), padding = 1, align = "center") boxx(c("Hi", "there", "you!"), padding = 1, align = "right")
#> ┌───────────┐ #> │ │ #> │ Hi │ #> │ there │ #> │ you! │ #> │ │ #> └───────────┘ #> ┌───────────┐ #> │ │ #> │ Hi │ #> │ there │ #> │ you! │ #> │ │ #> └───────────┘ #> ┌───────────┐ #> │ │ #> │ Hi │ #> │ there │ #> │ you! │ #> │ │ #> └───────────┘
star <- symbol$star label <- c(paste(star, "Hello", star), " there!") boxx( col_white(label), border_style="round", padding = 1, float = "center", border_col = "tomato3", background_col="darkolivegreen" )
#> ╭───────────────╮ #> │ │ #> │ ★ Hello ★ │ #> │ there! │ #> │ │ #> ╰───────────────╯
The boxes might or might not look great in your terminal, depending on the box style you use and the font the terminal uses. We found that the Menlo font looks nice in most terminals an also in Emacs.
RStudio currently has a line height greater than one for console output, which makes the boxes ugly.
List all available spinners
list_spinners()
list_spinners()
Character vector of all available spinner names.
Other spinners:
demo_spinners()
,
get_spinner()
,
make_spinner()
list_spinners() get_spinner(list_spinners()[1])
list_spinners() get_spinner(list_spinners()[1])
Create a function that can be used to add ANSI styles to text.
make_ansi_style(..., bg = FALSE, grey = FALSE, colors = num_ansi_colors())
make_ansi_style(..., bg = FALSE, grey = FALSE, colors = num_ansi_colors())
... |
The style to create. See details and examples below. |
bg |
Whether the color applies to the background. |
grey |
Whether to specifically create a grey color. This flag is included, because ANSI 256 has a finer color scale for greys, then the usual 0:5 scale for red, green and blue components. It is only used for RGB color specifications (either numerically or via a hexadecimal string), and it is ignored on eight color ANSI terminals. |
colors |
Number of colors, detected automatically by default. |
The ...
style argument can be any of the following:
A cli ANSI style function of class cli_ansi_style
. This is returned
as is, without looking at the other arguments.
An R color name, see grDevices::colors()
.
A 6- or 8-digit hexadecimal color string, e.g. #ff0000
means
red. Transparency (alpha channel) values are ignored.
A one-column matrix with three rows for the red, green
and blue channels, as returned by grDevices::col2rgb()
.
make_ansi_style()
detects the number of colors to use
automatically (this can be overridden using the colors
argument). If the number of colors is less than 256 (detected or given),
then it falls back to the color in the ANSI eight color mode that
is closest to the specified (RGB or R) color.
A function that can be used to color (style) strings.
Other ANSI styling:
ansi-styles
,
combine_ansi_styles()
,
num_ansi_colors()
make_ansi_style("orange") make_ansi_style("#123456") make_ansi_style("orange", bg = TRUE) orange <- make_ansi_style("orange") orange("foobar") cat(orange("foobar"))
make_ansi_style("orange") make_ansi_style("#123456") make_ansi_style("orange", bg = TRUE) orange <- make_ansi_style("orange") orange("foobar") cat(orange("foobar"))
Create a spinner
make_spinner( which = NULL, stream = "auto", template = "{spin}", static = c("dots", "print", "print_line", "silent") )
make_spinner( which = NULL, stream = "auto", template = "{spin}", static = c("dots", "print", "print_line", "silent") )
which |
The name of the chosen spinner. If |
stream |
The stream to use for the spinner. Typically this is
standard error, or maybe the standard output stream.
It can also be a string, one of |
template |
A template string, that will contain the spinner. The
spinner itself will be substituted for |
static |
What to do if the terminal does not support dynamic displays:
|
A cli_spinner
object, which is a list of functions. See
its methods below.
cli_spinner
methods:
$spin()
: output the next frame of the spinner.
$finish()
: terminate the spinner. Depending on terminal capabilities
this removes the spinner from the screen. Spinners can be reused,
you can start calling the $spin()
method again.
All methods return the spinner object itself, invisibly.
The spinner is automatically throttled to its ideal update frequency.
sp1 <- make_spinner() fun_with_spinner <- function() { lapply(1:100, function(x) { sp1$spin(); Sys.sleep(0.05) }) sp1$finish() } ansi_with_hidden_cursor(fun_with_spinner())
sp2 <- make_spinner(template = "Computing {spin}") fun_with_spinner2 <- function() { lapply(1:100, function(x) { sp2$spin(); Sys.sleep(0.05) }) sp2$finish() } ansi_with_hidden_cursor(fun_with_spinner2())
sp3 <- make_spinner("simpleDotsScrolling", template = "Downloading {spin}") fun_with_spinner3 <- function() { lapply(1:100, function(x) { sp3$spin(); Sys.sleep(0.05) }) sp3$finish() } ansi_with_hidden_cursor(fun_with_spinner3())
Other spinners:
demo_spinners()
,
get_spinner()
,
list_spinners()
Pluralization helper functions
no(expr) qty(expr)
no(expr) qty(expr)
expr |
For |
Other pluralization:
pluralization
,
pluralize()
nfile <- 0; cli_text("Found {no(nfile)} file{?s}.") #> Found no files. nfile <- 1; cli_text("Found {no(nfile)} file{?s}.") #> Found 1 file. nfile <- 2; cli_text("Found {no(nfile)} file{?s}.") #> Found 2 files.
nfile <- 0; cli_text("Found {no(nfile)} file{?s}.") #> Found no files. nfile <- 1; cli_text("Found {no(nfile)} file{?s}.") #> Found 1 file. nfile <- 2; cli_text("Found {no(nfile)} file{?s}.") #> Found 2 files.
Certain Unix and Windows terminals, and also certain R GUIs, e.g. RStudio, support styling terminal output using special control sequences (ANSI sequences).
num_ansi_colors()
detects if the current R session supports ANSI
sequences, and if it does how many colors are supported.
num_ansi_colors(stream = "auto") detect_tty_colors()
num_ansi_colors(stream = "auto") detect_tty_colors()
stream |
The stream that will be used for output, an R connection
object. It can also be a string, one of |
The detection mechanism is quite involved and it is designed to work out of the box on most systems. If it does not work on your system, please report a bug. Setting options and environment variables to turn on ANSI support is error prone, because they are inherited in other environments, e.g. knitr, that might not have ANSI support.
If you want to turn off ANSI colors, set the NO_COLOR
environment
variable to a non-empty value.
The exact detection mechanism is as follows:
If the cli.num_colors
options is set, that is returned.
If the R_CLI_NUM_COLORS
environment variable is set to a
non-empty value, then it is used.
If the crayon.enabled
option is set to FALSE
, 1L is returned.
(This is for compatibility with code that uses the crayon package.)
If the crayon.enabled
option is set to TRUE
and the
crayon.colors
option is not set, then the value of the
cli.default_num_colors
option, or if it is unset, then 8L is
returned.
If the crayon.enabled
option is set to TRUE
and the
crayon.colors
option is also set, then the latter is returned.
(This is for compatibility with code that uses the crayon package.)
If the NO_COLOR
environment variable is set, then 1L is returned.
If we are in knitr, then 1L is returned, to turn off colors in
.Rmd
chunks.
If stream
is "auto"
(the default) and there is an active
sink (either for "output"
or "message"
), then we return 1L.
(In theory we would only need to check the stream that will be
be actually used, but there is no easy way to tell that.)
If stream
is not "auto"
, but it is stderr()
and there is an
active sink for it, then 1L is returned.
(If a sink is active for "output", then R changes the stdout()
stream, so this check is not needed.)
If the cli.default_num_colors
option is set, then we use that.
If R is running inside RGui on Windows, or R.app on macOS, then we return 1L.
If R is running inside RStudio, with color support, then the appropriate number of colors is returned, usually 256L.
If R is running on Windows, inside an Emacs version that is recent
enough to support ANSI colors, then the value of the
cli.default_num_colors
option, or if unset 8L is returned.
(On Windows, Emacs has isatty(stdout()) == FALSE
, so we need to
check for this here before dealing with terminals.)
If stream
is not the standard output or standard error in a
terminal, then 1L is returned.
Otherwise we use and cache the result of the terminal color detection (see below).
The terminal color detection algorithm:
If the COLORTERM
environment variable is set to truecolor
or
24bit
, then we return 16 million colors.
If the COLORTERM
environment variable is set to anything else,
then we return the value of the cli.num_default_colors
option,
8L if unset.
If R is running on Unix, inside an Emacs version that is recent
enough to support ANSI colors, then the value of the
cli.default_num_colors
option is returned, or 8L if unset.
If we are on Windows in an RStudio terminal, then apparently
we only have eight colors, but the cli.default_num_colors
option
can be used to override this.
If we are in a recent enough Windows 10 terminal, then there
is either true color (from build 14931) or 256 color (from
build 10586) support. You can also use the cli.default_num_colors
option to override these.
If we are on Windows, under ConEmu or cmder, or ANSICON is loaded,
then the value of cli.default_num_colors
, or 8L if unset, is
returned.
Otherwise if we are on Windows, return 1L.
Otherwise we are on Unix and try to run tput colors
to determine
the number of colors. If this succeeds, we return its return value.
If the TERM
environment variable is xterm
and tput
returned 8L, we return 256L, because xterm compatible terminals
tend to support 256 colors
(https://github.com/r-lib/crayon/issues/17)
You can override this with the cli.default_num_colors
option.
If TERM
is set to dumb
, we return 1L.
If TERM
starts with screen
, xterm
, or vt100
, we return 8L.
If TERM
contains color
, ansi
, cygwin
or linux
, we return 8L.
Otherwise we return 1L.
Integer, the number of ANSI colors the current R session
supports for stream
.
Other ANSI styling:
ansi-styles
,
combine_ansi_styles()
,
make_ansi_style()
num_ansi_colors()
num_ansi_colors()
About cli pluralization
cli has tools to create messages that are printed correctly in singular and plural forms. This usually requires minimal extra work, and increases the quality of the messages greatly. In this document we first show some pluralization examples that you can use as guidelines. Hopefully these are intuitive enough, so that they can be used without knowing the exact cli pluralization rules.
If you need pluralization without the semantic cli functions, see the
pluralize()
function.
In the simplest case the message contains a single {}
glue
substitution, which specifies the quantity that is used to select
between the singular and plural forms. Pluralization uses markup that is
similar to glue, but uses the {?
and }
delimiters:
library(cli) nfile <- 0; cli_text("Found {nfile} file{?s}.")
#> Found 0 files.
nfile <- 1; cli_text("Found {nfile} file{?s}.")
#> Found 1 file.
nfile <- 2; cli_text("Found {nfile} file{?s}.")
#> Found 2 files.
Here the value of nfile
is used to decide whether the singular or
plural form of file
is used. This is the most common case for English
messages.
If the plural form is more difficult than a simple s
suffix, then the
singular and plural forms can be given, separated with a forward slash:
ndir <- 1; cli_text("Found {ndir} director{?y/ies}.")
#> Found 1 directory.
ndir <- 5; cli_text("Found {ndir} director{?y/ies}.")
#> Found 5 directories.
"no"
instead of zeroFor readability, it is better to use the no()
helper function to
include a count in a message. no()
prints the word "no"
if the count
is zero, and prints the numeric count otherwise:
nfile <- 0; cli_text("Found {no(nfile)} file{?s}.")
#> Found no files.
nfile <- 1; cli_text("Found {no(nfile)} file{?s}.")
#> Found 1 file.
nfile <- 2; cli_text("Found {no(nfile)} file{?s}.")
#> Found 2 files.
With the auto-collapsing feature of cli it is easy to include a list of objects in a message. When cli interprets a character vector as a pluralization quantity, it takes the length of the vector:
pkgs <- "pkg1" cli_text("Will remove the {.pkg {pkgs}} package{?s}.")
#> Will remove the pkg1 package.
pkgs <- c("pkg1", "pkg2", "pkg3") cli_text("Will remove the {.pkg {pkgs}} package{?s}.")
#> Will remove the pkg1, pkg2, and pkg3 packages.
Note that the length is only used for non-numeric vectors (when
is.numeric(x)
return FALSE
). If you want to use the length of a
numeric vector, convert it to character via as.character()
.
You can combine collapsed vectors with "no"
, like this:
pkgs <- character() cli_text("Will remove {?no/the/the} {.pkg {pkgs}} package{?s}.")
#> Will remove no packages.
pkgs <- c("pkg1", "pkg2", "pkg3") cli_text("Will remove {?no/the/the} {.pkg {pkgs}} package{?s}.")
#> Will remove the pkg1, pkg2, and pkg3 packages.
When the pluralization markup contains three alternatives, like above, the first one is used for zero, the second for one, and the third one for larger quantities.
When the text contains multiple glue {}
substitutions, the one right
before the pluralization markup is used. For example:
nfiles <- 3; ndirs <- 1 cli_text("Found {nfiles} file{?s} and {ndirs} director{?y/ies}")
#> Found 3 files and 1 directory
This is sometimes not the the correct one. You can explicitly specify
the correct quantity using the qty()
function. This sets that quantity
without printing anything:
nupd <- 3; ntotal <- 10 cli_text("{nupd}/{ntotal} {qty(nupd)} file{?s} {?needs/need} updates")
#> 3/10 files need updates
Note that if the message only contains a single {}
substitution, then
this may appear before or after the pluralization markup. If the message
contains multiple {}
substitutions after pluralization markup, an
error is thrown.
Similarly, if the message contains no {}
substitutions at all, but has
pluralization markup, an error is thrown.
The exact rules of cli pluralization. There are two sets of rules. The
first set specifies how a quantity is associated with a {?}
pluralization markup. The second set describes how the {?}
is parsed
and interpreted.
{}
substitutions define quantities. If the value of a {}
substitution is numeric (when is.numeric(x)
holds), then it has to
have length one to define a quantity. This is only enforced if the
{}
substitution is used for pluralization. The quantity is defined
as the value of {}
then, rounded with as.integer()
. If the value
of {}
is not numeric, then its quantity is defined as its length.
If a message has {?}
markup but no {}
substitution, an error is
thrown.
If a message has exactly one {}
substitution, its value is used as
the pluralization quantity for all {?}
markup in the message.
If a message has multiple {}
substitutions, then for each {?}
markup cli uses the quantity of the {}
substitution that precedes
it.
If a message has multiple {}
substitutions and has pluralization
markup without a preceding {}
substitution, an error is thrown.
Pluralization markup starts with {?
and ends with }
. It may not
contain {
and }
characters, so it may not contain {}
substitutions either.
Alternative words or suffixes are separated by /
.
If there is a single alternative, then nothing is used if
quantity == 1
and this single alternative is used if
quantity != 1
.
If there are two alternatives, the first one is used for
quantity == 1
, the second one for quantity != 1
(including
'quantity == 0
).
If there are three alternatives, the first one is used for
quantity == 0
, the second one for quantity == 1
, and the third
one otherwise.
Other pluralization:
no()
,
pluralize()
pluralize()
is similar to glue::glue()
, with two differences:
It supports cli's pluralization syntax, using {?}
markers.
It collapses substituted vectors into a comma separated string.
pluralize( ..., .envir = parent.frame(), .transformer = glue::identity_transformer )
pluralize( ..., .envir = parent.frame(), .transformer = glue::identity_transformer )
... , .envir , .transformer
|
All arguments are passed to |
See pluralization and some examples below.
You need to install the glue package to use this function.
Other pluralization:
no()
,
pluralization
# Regular plurals nfile <- 0; pluralize("Found {nfile} file{?s}.") nfile <- 1; pluralize("Found {nfile} file{?s}.") nfile <- 2; pluralize("Found {nfile} file{?s}.") # Irregular plurals ndir <- 1; pluralize("Found {ndir} director{?y/ies}.") ndir <- 5; pluralize("Found {ndir} director{?y/ies}.") # Use 'no' instead of zero nfile <- 0; pluralize("Found {no(nfile)} file{?s}.") nfile <- 1; pluralize("Found {no(nfile)} file{?s}.") nfile <- 2; pluralize("Found {no(nfile)} file{?s}.") # Use the length of character vectors pkgs <- "pkg1" pluralize("Will remove the {pkgs} package{?s}.") pkgs <- c("pkg1", "pkg2", "pkg3") pluralize("Will remove the {pkgs} package{?s}.") pkgs <- character() pluralize("Will remove {?no/the/the} {pkgs} package{?s}.") pkgs <- c("pkg1", "pkg2", "pkg3") pluralize("Will remove {?no/the/the} {pkgs} package{?s}.") # Multiple quantities nfiles <- 3; ndirs <- 1 pluralize("Found {nfiles} file{?s} and {ndirs} director{?y/ies}") # Explicit quantities nupd <- 3; ntotal <- 10 cli_text("{nupd}/{ntotal} {qty(nupd)} file{?s} {?needs/need} updates")
# Regular plurals nfile <- 0; pluralize("Found {nfile} file{?s}.") nfile <- 1; pluralize("Found {nfile} file{?s}.") nfile <- 2; pluralize("Found {nfile} file{?s}.") # Irregular plurals ndir <- 1; pluralize("Found {ndir} director{?y/ies}.") ndir <- 5; pluralize("Found {ndir} director{?y/ies}.") # Use 'no' instead of zero nfile <- 0; pluralize("Found {no(nfile)} file{?s}.") nfile <- 1; pluralize("Found {no(nfile)} file{?s}.") nfile <- 2; pluralize("Found {no(nfile)} file{?s}.") # Use the length of character vectors pkgs <- "pkg1" pluralize("Will remove the {pkgs} package{?s}.") pkgs <- c("pkg1", "pkg2", "pkg3") pluralize("Will remove the {pkgs} package{?s}.") pkgs <- character() pluralize("Will remove {?no/the/the} {pkgs} package{?s}.") pkgs <- c("pkg1", "pkg2", "pkg3") pluralize("Will remove {?no/the/the} {pkgs} package{?s}.") # Multiple quantities nfiles <- 3; ndirs <- 1 pluralize("Found {nfiles} file{?s} and {ndirs} director{?y/ies}") # Explicit quantities nupd <- 3; ntotal <- 10 cli_text("{nupd}/{ntotal} {qty(nupd)} file{?s} {?needs/need} updates")
Defines a print method for functions, in the current session, that supports syntax highlighting.
pretty_print_code()
pretty_print_code()
The new print method takes priority over the built-in one. Use
base::suppressMessages()
to suppress the alert message.
The cli progress C API
CLI_SHOULD_TICK
A macro that evaluates to (int) 1 if a cli progress bar update is due,
and to (int) 0 otherwise. If the timer hasn't been initialized in this
compilation unit yet, then it is always 0. To initialize the timer,
call cli_progress_init_timer()
or create a progress bar with
cli_progress_bar()
.
cli_progress_add()
void cli_progress_add(SEXP bar, double inc);
Add a number of progress units to the progress bar. It will also trigger an update if an update is due.
bar
: progress bar object.
inc
: progress increment.
cli_progress_bar()
SEXP cli_progress_bar(double total, SEXP config);
Create a new progress bar object. The returned progress bar object
must be PROTECT()
-ed.
total
: Total number of progress units. Use NA_REAL
if it is not
known.
config
: R named list object of additional parameters. May be NULL
(the C NULL~) or
R_NilValue(the R
NULL') for the defaults.
config
may contain the following entries:
name
: progress bar name.
status
: (initial) progress bar status.
type
: progress bar type.
total
: total number of progress units.
show_after
: show the progress bar after the specified number of
seconds. This overrides the global show_after
option.
format
: format string, must be specified for custom progress bars.
format_done
: format string for successful termination.
format_failed
: format string for unsuccessful termination.
clear
: whether to remove the progress bar from the screen after
termination.
auto_terminate
: whether to terminate the progress bar when the
number of current units equals the number of total progress units.
#include <cli/progress.h> SEXP progress_test1() { int i; SEXP bar = PROTECT(cli_progress_bar(1000, NULL)); for (i = 0; i < 1000; i++) { cli_progress_sleep(0, 4 * 1000 * 1000); if (CLI_SHOULD_TICK) cli_progress_set(bar, i); } cli_progress_done(bar); UNPROTECT(1); return Rf_ScalarInteger(i); }
cli_progress_done()
void cli_progress_done(SEXP bar);
Terminate the progress bar.
bar
: progress bar object.
cli_progress_init_timer()
void cli_progress_init_timer();
Initialize the cli timer without creating a progress bar.
cli_progress_num()
int cli_progress_num();
Returns the number of currently active progress bars.
cli_progress_set()
void cli_progress_set(SEXP bar, double set);
Set the progress bar to the specified number of progress units.
bar
: progress bar object.
set
: number of current progress progress units.
cli_progress_set_clear()
void cli_progress_set_clear(SEXP bar, int clear);
Set whether to remove the progress bar from the screen. You can call
this any time before cli_progress_done()
is called.
bar
: progress bar object.
clear
: whether to remove the progress bar from the screen, zero or
one.
cli_progress_set_format()
void cli_progress_set_format(SEXP bar, const char *format, ...);
Set a custom format string for the progress bar. This call does not
try to update the progress bar. If you want to request an update,
call cli_progress_add()
, cli_progress_set()
or
cli_progress_update()
.
bar
: progress bar object.
format
: format string.
...
: values to substitute into format
.
format
and ...
are passed to vsnprintf()
to create a format
string.
Format strings may contain glue substitutions, referring to progress variables, pluralization, and cli styling.
cli_progress_set_name()
void cli_progress_set_name(SEXP bar, const char *name);
Set the name of the progress bar.
bar
; progress bar object.
name
: progress bar name.
cli_progress_set_status()
void cli_progress_set_status(SEXP bar, const char *status);
Set the status of the progress bar.
bar
: progress bar object.
status
: progress bar status.
cli_progress_set_type()
void cli_progress_set_type(SEXP bar, const char *type);
Set the progress bar type. Call this function right after creating
the progress bar with cli_progress_bar()
. Otherwise the behavior is
undefined.
bar
: progress bar object.
type
: progress bar type. Possible progress bar types:
iterator
, tasks
, download
and custom
.
cli_progress_update()
void cli_progress_update(SEXP bar, double set, double inc, int force);
Update the progress bar. Unlike the simpler cli_progress_add()
and
cli_progress_set()
function, it can force an update if force
is
set to 1.
bar
: progress bar object.
set
: the number of current progress units. It is ignored if
negative.
inc
: increment to add to the current number of progress units.
It is ignored if set
is not negative.
force
: whether to force an update, even if no update is due.
To force an update without changing the current number of progress units,
supply set = -1
, inc = 0
and force = 1
.
Progress bar variables
These variables can be used in cli progress bar format
strings. They are calculated on demand. To use a variable, e.g. pb_bar
in a package, you either need to to import pb_bar
from cli, or use
the qualified form in the format string: cli::pb_bar
.
Similarly, in R scripts, you can use pb_bar
after library(cli)
,
or cli::pb_bar
if you do not attach the cli package.
pb_bar
Creates a visual progress bar. If the number of total units is unknown, then it will return an empty string.
cli_progress_bar( total = 100, format = "Fitting model {cli::pb_bar} {cli::pb_percent}" )
#> Fitting model ███████████████████████████████ 66%
pb_current
The number of current progress units.
cli_progress_bar( total = 100, format = "{cli::pb_spin} Reading file {cli::pb_current}/{cli::pb_total}" )
#> ⠙ Reading file 66/100
pb_current_bytes
The number of current progress units formatted as bytes. The output has a constant width of six characters.
cli_progress_bar( format = "Got {cli::pb_current_bytes} in {cli::pb_elapsed}" )
#> Got 524 kB in 5s
pb_elapsed
The elapsed time since the start of the progress bar. The time is
measured since the progress bar was created with cli_progress_bar()
or similar.
cli_progress_bar( total = 100, format = "{cli::pb_bar} {cli::pb_percent} [{cli::pb_elapsed}]" )
#> ███████████████████████████████ 66% [5s]
pb_elapsed_clock
The elapsed time, in hh::mm::ss
format.
cli_progress_bar( total = 100, format = "{cli::pb_bar} {cli::pb_percent} [{cli::pb_elapsed_clock}]" )
#> ███████████████████████████████ 66% [00:00:05]
pb_elapsed_raw
The number of seconds since the start of the progress bar.
cli_progress_bar( total = 100, format = "{cli::pb_bar} {cli::pb_percent} [{round(cli::pb_elapsed_raw)}s]" )
#> ███████████████████████████████ 66% [5s]
pb_eta
The estimated time until the end of the progress bar, in human readable form.
cli_progress_bar( total = 100, format = "{cli::pb_bar} {cli::pb_percent} | ETA: {cli::pb_eta}" )
#> ███████████████████████████████ 66% | ETA: 3s
pb_eta_raw
The estimated time until the end of the progress
bar, in seconds. This is useful if you want to adjust the default
pb_eta
display.
cli_progress_bar( total = 100, format = "{cli::pb_bar} {cli::pb_percent} | ETA: {round(cli::pb_eta_raw)}s" )
#> ███████████████████████████████ 66% | ETA: 3s
pb_eta_str
The estimated time until the end of the progress bar.
It includes the "ETA:"
prefix. It is only shown if the time can be
estimated, otherwise it is the empty string.
cli_progress_bar( total = 100, format = "{cli::pb_bar} {cli::pb_percent} | {cli::pb_eta_str}" )
#> ███████████████████████████████ 66% | ETA: 3s
pb_extra
pb_extra
can be used to access extra data, see the extra
argument
of cli_progress_bar()
and cli_progress_update()
.
cli_progress_bar( total = 100, extra = list(user = whoami::username()), format = "Cleaning cache for user '{cli::pb_extra$user}': {cli::pb_current_bytes}" )
#> Cleaning cache for user 'gaborcsardi': 161 MB
pb_id
The id of the progress bar. The id has the format
cli-<pid>-<counter>
where <pid>
is the process id, and
<counter>
is an integer counter that is incremented every time
cli needs a new unique id.
This is useful for debugging progress bars.
cli_progress_bar( format = "Progress bar '{cli::pb_id}' is at {cli::pb_current}" )
#> Progress bar 'cli-82040-1814' is at 64
pb_name
The name of the progress bar. This is supplied by the developer, and it is by default the empty string. A space character is added to non-empty names.
cli_progress_bar( name = "Loading training data", total = 100, format = "{cli::pb_name} {cli::pb_bar} {cli::pb_percent}" )
#> Loading training data ███████████████████████████████ 66%
pb_percent
The percentage of the progress bar, always formatted
in three characters plus the percentage sign. If the total number of
units is unknown, then it is " NA%"
.
cli_progress_bar( total = 100, format = "{cli::pb_bar} {cli::pb_percent}" )
#> ███████████████████████████████ 66%
pb_pid
The integer process id of the progress bar. This is useful if you are aggregating logging output or progress results from multiple processes.
pb_rate
The progress rate, in number of units per second, formatted in a string.
cli_progress_bar( total = 156, format = "Reading input files {pb_current}/{pb_total} [{pb_rate}]" )
#> Reading input files 68/156 [14/s]
pb_rate_raw
The raw progress rate, in number of units per second.
cli_progress_bar( total = 156, format = "Reading input files {pb_current}/{pb_total} [{round(pb_rate_raw)}/s]" )
#> Reading input files 68/156 [14/s]
pb_rate_bytes
The progress rate, formatted as bytes per second, in human readable form.
cli_progress_bar( total = 256 * 1024 * 1014, format = paste0( "Reading data {pb_current_bytes}/{pb_total_bytes} ", "[{ansi_trimws(pb_rate_bytes)}]" )
#> Reading data 70 MB/266 MB [14 MB/s]
pb_spin
A spinner. The default spinner is selected via a get_spinner()
call.
cli_progress_bar( total = 100, format = "{cli::pb_spin} Reading file {cli::pb_current}/{cli::pb_total}" )
#> ⠙ Reading file 66/100
pb_status
The status string of the progress bar. By default this is an empty
string, but it is possible to set it in cli_progress_bar()
and 'cli_progress_update()].
cli_progress_bar(status = "Connecting...")
#> ⠙ Connecting... 0 done (0/s) | 1s
pb_timestamp
A time stamp for the current time in ISO 8601 format.
cli_progress_bar( "Loading training data files", format = "{pb_timestamp} {pb_current} ({pb_rate})"
#> 2022-09-07T11:27:50+00:00 125 (25/s)
pb_total
The total number of progress units, or NA
if the number of units is
unknown.
cli_progress_bar( total = 100, format = "{cli::pb_spin} Reading file {cli::pb_current}/{cli::pb_total}" )
#> ⠙ Reading file 66/100
pb_total_bytes
The total number of progress units, formatted as bytes, in a human readable format.
cli_progress_bar( total = 256 * 1024 * 1014, format = paste0( "Reading data {pb_current_bytes}/{pb_total_bytes} ", "[{ansi_trimws(pb_rate_bytes)}]" )
#> Reading data 70 MB/266 MB [14 MB/s]
Other progress bar functions:
cli_progress_along()
,
cli_progress_bar()
,
cli_progress_builtin_handlers()
,
cli_progress_message()
,
cli_progress_num()
,
cli_progress_output()
,
cli_progress_step()
,
cli_progress_styles()
The rule can include either a centered text label, or labels on the left and right side.
To color the labels, use the functions col_*
, bg_*
and style_*
functions, see ANSI styles, and the examples below.
To color the line, either these functions directly, or the line_col
option.
rule( left = "", center = "", right = "", line = 1, col = NULL, line_col = col, background_col = NULL, width = console_width() )
rule( left = "", center = "", right = "", line = 1, col = NULL, line_col = col, background_col = NULL, width = console_width() )
left |
Label to show on the left. It interferes with the |
center |
Label to show at the center. It interferes with the
|
right |
Label to show on the right. It interferes with the |
line |
The character or string that is used to draw the line.
It can also |
col |
Color of text, and default line color. Either an ANSI style
function (see ANSI styles), or a color name that is
passed to |
line_col , background_col
|
Either a color name (used in
|
width |
Width of the rule. Defaults to the |
rule()
#> ──────────────────────────────────────────────────────────────────────
Some strings for the line
argument are interpreted specially:
"single"
: (same as 1
), a single line,
"double"
: (same as 2
), a double line,
"bar1"
, "bar2"
, "bar3"
, etc., "bar8"
uses varying height bars.
rule(line = 2)
#> ══════════════════════════════════════════════════════════════════════
rule(line = "bar2") rule(line = "bar5")
#> ▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂ #> ▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅▅
rule(center = "TITLE", line = "~")
#> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ TITLE ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rule(center = "TITLE", line = col_blue("~-"))
#> ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- TITLE ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
rule(center = bg_red(" ", symbol$star, "TITLE", symbol$star, " "), line = "\u2582", line_col = "orange")
#> ▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂ ★TITLE★ ▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂
rule(left = "Results")
#> ── Results ───────────────────────────────────────────────────────────
rule(center = " * RESULTS * ")
#> ──────────────────────────── * RESULTS * ───────────────────────────
rule(center = col_red(" * RESULTS * "))
#> ──────────────────────────── * RESULTS * ───────────────────────────
rule(center = col_red(" * RESULTS * "), line_col = "red")
#> ──────────────────────────── * RESULTS * ───────────────────────────
Character scalar, the rule.
Print the helpful ruler to the screen
ruler(width = console_width())
ruler(width = console_width())
width |
Ruler width. |
ruler()
ruler()
To use this theme, you can set it as the cli.theme
option.
Note that this is in addition to the builtin theme, which is still in
effect.
simple_theme(dark = getOption("cli.theme_dark", "auto"))
simple_theme(dark = getOption("cli.theme_dark", "auto"))
dark |
Whether the theme should be optimized for a dark
background. If |
options(cli.theme = cli::simple_theme())
and then CLI apps started after this will use it as the default theme. You can also use it temporarily, in a div element:
cli_div(theme = cli::simple_theme())
show <- cli_div(theme = cli::simple_theme()) cli_h1("Heading 1") cli_h2("Heading 2") cli_h3("Heading 3") cli_par() cli_alert_danger("Danger alert") cli_alert_warning("Warning alert") cli_alert_info("Info alert") cli_alert_success("Success alert") cli_alert("Alert for starting a process or computation", class = "alert-start") cli_end() cli_text("Packages and versions: {.pkg cli} {.version 1.0.0}.") cli_text("Time intervals: {.timestamp 3.4s}") cli_text("{.emph Emphasis} and {.strong strong emphasis}") cli_text("This is a piece of code: {.code sum(x) / length(x)}") cli_text("Function names: {.fn cli::simple_theme}") cli_text("Files: {.file /usr/bin/env}") cli_text("URLs: {.url https://r-project.org}") cli_h2("Longer code chunk") cli_par(class = "code R") cli_verbatim( '# window functions are useful for grouped mutates', 'mtcars %>%', ' group_by(cyl) %>%', ' mutate(rank = min_rank(desc(mpg)))') cli_end(show)
#> #> ── Heading 1 ───────────────────────────────────────────────────────── #> #> ─ Heading 2 ── #> #> Heading 3 #> ✖ Danger alert #> ! Warning alert #> ℹ Info alert #> ✔ Success alert #> → Alert for starting a process or computation #> #> Packages and versions: cli 1.0.0. #> Time intervals: [3.4s] #> Emphasis and strong emphasis #> This is a piece of code: `sum(x) / length(x)` #> Function names: `cli::simple_theme()`() #> Files: /usr/bin/env #> URLs: <https://r-project.org> #> #> ─ Longer code chunk ── #> # window functions are useful for grouped mutates #> mtcars %>% #> group_by(cyl) %>% #> mutate(rank = min_rank(desc(mpg))) #>
Rendered using block elements. In most common fixed width fonts these are rendered wider than regular characters which means they are not suitable if you need precise alignment.
You might want to avoid sparklines on non-UTF-8 systems, because they
do not look good. You can use is_utf8_output()
to test for support
for them.
spark_bar(x)
spark_bar(x)
x |
A numeric vector between 0 and 1 |
x <- seq(0, 1, length = 6) spark_bar(x)
#> ▁▂▄▅▇█
x <- seq(0, 1, length = 6) spark_bar(sample(x))
#> ▅▁█▄▇▂
spark_bar(seq(0, 1, length = 8))
#> ▁▂▃▄▅▆▇█
NA
s are left out:
spark_bar(c(0, NA, 0.5, NA, 1))
#> ▁ ▄ █
You might want to avoid sparklines on non-UTF-8 systems, because they
do not look good. You can use is_utf8_output()
to test for support
for them.
spark_line(x)
spark_line(x)
x |
A numeric vector between 0 and 1 |
x <- seq(0, 1, length = 10) spark_line(x)
#> ⣀⡠⠔⠊⠉
start_app
creates an app, and places it on the top of the app stack.
start_app( theme = getOption("cli.theme"), output = c("auto", "message", "stdout", "stderr"), .auto_close = TRUE, .envir = parent.frame() ) stop_app(app = NULL) default_app()
start_app( theme = getOption("cli.theme"), output = c("auto", "message", "stdout", "stderr"), .auto_close = TRUE, .envir = parent.frame() ) stop_app(app = NULL) default_app()
theme |
Theme to use. |
output |
How to print the output. |
.auto_close |
Whether to stop the app, when the calling frame is destroyed. |
.envir |
The environment to use, instead of the calling frame, to trigger the stop of the app. |
app |
App to stop. If |
stop_app
removes the top app, or multiple apps from the app stack.
default_app
returns the default app, the one on the top of the stack.
start_app
returns the new app, default_app
returns the default app.
stop_app
does not return anything.
ansi_hyperlink()
creates an ANSI hyperlink.
style_hyperlink(text, url, params = NULL) ansi_has_hyperlink_support() ansi_hyperlink_types()
style_hyperlink(text, url, params = NULL) ansi_has_hyperlink_support() ansi_hyperlink_types()
text |
Text to show. |
url |
URL to link to. |
params |
A named character vector of additional parameters, or |
This function is currently experimental. In particular, many of the
ansi_*()
functions do not support it properly.
ansi_has_hyperlink_support()
checks if the current stdout()
supports hyperlinks.
See also https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda.
ansi_hyperlink_types()
checks if current stdout()
supports various
types of hyperlinks. It returns a list with entries href
, run
,
help
and vignettes
.
Styled cli_ansi_string
for style_hyperlink()
.
Logical scalar for ansi_has_hyperlink_support()
.
cat("This is an", style_hyperlink("R", "https://r-project.org"), "link.\n") ansi_has_hyperlink_support()
cat("This is an", style_hyperlink("R", "https://r-project.org"), "link.\n") ansi_has_hyperlink_support()
Various handy symbols to use in a command line UI
symbol list_symbols()
symbol list_symbols()
A named list, see names(symbol)
for all sign names.
On Windows they have a fallback to less fancy symbols.
list_symbols()
prints a table with all symbols to the screen.
cat(symbol$tick, " SUCCESS\n", symbol$cross, " FAILURE\n", sep = "") ## All symbols cat(paste(format(names(symbol), width = 20), unlist(symbol)), sep = "\n")
cat(symbol$tick, " SUCCESS\n", symbol$cross, " FAILURE\n", sep = "") ## All symbols cat(paste(format(names(symbol), width = 20), unlist(symbol)), sep = "\n")
Use this function in your testthat test files, to test cli output. It requires testthat edition 3, and works best with snapshot tests.
test_that_cli( desc, code, configs = c("plain", "ansi", "unicode", "fancy"), links = NULL )
test_that_cli( desc, code, configs = c("plain", "ansi", "unicode", "fancy"), links = NULL )
desc |
Test description, passed to |
code |
Test code, it is modified to set up the cli config, and
then passed to |
configs |
cli configurations to test |
links |
Whether to run the code with various hyperlinks allowed.
If
|
test_that_cli()
calls testthat::test_that()
multiple times, with
different cli configurations. This makes it simple to test cli output
with and without ANSI colors, with and without Unicode characters.
Currently available configurations:
plain
: no ANSI colors, ASCII characters only.
ansi
: ANSI colors, ASCII characters only.
unicode
: no ANSI colors, Unicode characters.
fancy
; ANSI colors, Unicode characters.
See examples below and in cli's own tests, e.g. in https://github.com/r-lib/cli/tree/main/tests/testthat and the corresponding snapshots at https://github.com/r-lib/cli/tree/main/tests/testthat/_snaps
Because of base R's limitation to record Unicode characters on Windows, we suggest that you record your snapshots on Unix, or you restrict your tests to ASCII configurations.
Unicode tests on Windows are automatically skipped by testthat currently.
# testthat cannot record or compare snapshots when you run these # examples interactively, so you might want to copy them into a test # file # Default configurations cli::test_that_cli("success", { testthat::local_edition(3) testthat::expect_snapshot({ cli::cli_alert_success("wow") }) }) # Only use two configurations, because this output does not have colors cli::test_that_cli(configs = c("plain", "unicode"), "cat_bullet", { testthat::local_edition(3) testthat::expect_snapshot({ cli::cat_bullet(letters[1:5]) }) }) # You often need to evaluate all cli calls of a test case in the same # environment. Use `local()` to do that: cli::test_that_cli("theming", { testthat::local_edition(3) testthat::expect_snapshot(local({ cli::cli_div(theme = list(".alert" = list(before = "!!! "))) cli::cli_alert("wow") })) })
# testthat cannot record or compare snapshots when you run these # examples interactively, so you might want to copy them into a test # file # Default configurations cli::test_that_cli("success", { testthat::local_edition(3) testthat::expect_snapshot({ cli::cli_alert_success("wow") }) }) # Only use two configurations, because this output does not have colors cli::test_that_cli(configs = c("plain", "unicode"), "cat_bullet", { testthat::local_edition(3) testthat::expect_snapshot({ cli::cat_bullet(letters[1:5]) }) }) # You often need to evaluate all cli calls of a test case in the same # environment. Use `local()` to do that: cli::test_that_cli("theming", { testthat::local_edition(3) testthat::expect_snapshot(local({ cli::cli_div(theme = list(".alert" = list(before = "!!! "))) cli::cli_alert("wow") })) })
CLI elements can be styled via a CSS-like language of selectors and properties. Only a small subset of CSS3 is supported, and a lot visual properties cannot be implemented on a terminal, so these will be ignored as well.
The style of an element is calculated from themes from four sources. These form a stack, and the themes on the top of the stack take precedence, over themes in the bottom.
The cli package has a built-in theme. This is always active.
See builtin_theme()
.
When an app object is created via start_app()
, the caller can
specify a theme, that is added to theme stack. If no theme is
specified for start_app()
, the content of the cli.theme
option
is used. Removed when the corresponding app stops.
The user may specify a theme in the cli.user_theme
option. This
is added to the stack after the app's theme (step 2.), so it can
override its settings. Removed when the app that added it stops.
Themes specified explicitly in cli_div()
elements. These are
removed from the theme stack, when the corresponding cli_div()
elements are closed.
A theme is a named list of lists. The name of each entry is a CSS selector. Only a subset of CSS is supported:
Type selectors, e.g. input
selects all <input>
elements.
Class selectors, e.g. .index
selects any element that has a class
of "index".
ID selector. #toc
will match the element that has the ID "toc".
The descendant combinator, i.e. the space, that selects nodes
that are descendants of the first element. E.g. div span
will match
all <span>
elements that are inside a <div>
element.
The content of a theme list entry is another named list, where the
names are CSS properties, e.g. color
, or font-weight
or
margin-left
, and the list entries themselves define the values of
the properties. See builtin_theme()
and simple_theme()
for examples.
For flexibility, themes may also define formatter functions, with
property name fmt
. These will be called once the other styles are
applied to an element. They are only called on elements that produce
output, i.e. not on container elements.
Right now only a limited set of properties are supported. These include
left, right, top and bottom margins, background and foreground colors,
bold and italic fonts, underlined text. The before
and after
properties are supported to insert text before and after the
content of the element.
The current list of properties:
after
: A string literal to insert after the element. It can also be
a function that returns a string literal. Supported by all inline
elements, list items, alerts and rules.
background-color
: An R color name, or HTML hexadecimal color.
It can be applied to most elements (inline elements, rules, text,
etc.), but the background of containers is not colored properly
currently.
before
: A string literal to insert before the element. It can also be
a function that returns a string literal. Supported by all inline
elements, list items, alerts and rules.
class-map
: Its value can be a named list, and it specifies how
R (S3) class names are mapped to cli class names. E.g.
list(fs_path = "file")
specifies that fs_path
objects (from the fs
package) should always print as .file
objects in cli.
color
: Text color, an R color name or a HTML hexadecimal color. It
can be applied to most elements that are printed.
collapse
: Specifies how to collapse a vector, before applying
styling. If a character string, then that is used as the separator.
If a function, then it is called, with the vector as the only
argument.
digits
: Number of digits after the decimal point for numeric inline
element of class .val
.
fmt
: Generic formatter function that takes an input text and returns
formatted text. Can be applied to most elements. If colors are in use,
the input text provided to fmt
already includes ANSI sequences.
font-style
: If "italic"
then the text is printed as cursive.
font-weight
: If "bold"
, then the text is printed in boldface.
line-type
: Line type for cli_rule()
.
list-style-type
: String literal or functions that returns a string
literal, to be used as a list item marker in un-ordered lists.
margin-bottom
, margin-left
, margin-right
, margin-top
: Margins.
padding-left
, padding-right
: This is currently used the same way
as the margins, but this might change later.
start
: Integer number, the first element in an ordered list.
string-quote
: Quoting character for inline elements of class .val
.
text-decoration
: If "underline"
, then underlined text is created.
text-exdent
: Amount of indentation from the second line of wrapped
text.
transform
: A function to call on glue substitutions, before
collapsing them. Note that transform
is applied prior to
implementing color via ANSI sequences.
vec-last
: The last separator when collapsing vectors.
vec-sep
: The separator to use when collapsing vectors.
vec-sep2
: The separator to use for two elements when collapsing
vectors. If not set, then vec-sep
is used for these as well.
vec-trunc
: Vectors longer than this will be truncated. Defaults to
100.
vec-trunc-style
: Select between two ways of collapsing vectors:
"both-ends"
is the current default and it shows the beginning and
the end of the vector.
"head"
only shows the beginning of the vector.
More properties might be added later. If you think that a property is not applied properly to an element, please open an issue about it in the cli issue tracker.
Color of headings, that are only active in paragraphs with an 'output' class:
list( "par.output h1" = list("background-color" = "red", color = "#e0e0e0"), "par.output h2" = list("background-color" = "orange", color = "#e0e0e0"), "par.output h3" = list("background-color" = "blue", color = "#e0e0e0") )
Create a custom alert type:
list( ".alert-start" = list(before = symbol$play), ".alert-stop" = list(before = symbol$stop) )
Draw a tree using box drawing characters. Unicode characters are
used if available. (Set the cli.unicode
option if auto-detection
fails.)
tree( data, root = data[[1]][[1]], style = NULL, width = console_width(), trim = FALSE )
tree( data, root = data[[1]][[1]], style = NULL, width = console_width(), trim = FALSE )
data |
Data frame that contains the tree structure. The first column is an id, and the second column is a list column, that contains the ids of the child nodes. The optional third column may contain the text to print to annotate the node. |
root |
The name of the root node. |
style |
Optional box style list. |
width |
Maximum width of the output. Defaults to the |
trim |
Whether to avoid traversing the same nodes multiple times.
If |
A node might appear multiple times in the tree, or might not appear at all.
data <- data.frame( stringsAsFactors = FALSE, package = c("processx", "backports", "assertthat", "Matrix", "magrittr", "rprojroot", "clisymbols", "prettyunits", "withr", "desc", "igraph", "R6", "crayon", "debugme", "digest", "irlba", "rcmdcheck", "callr", "pkgconfig", "lattice"), dependencies = I(list( c("assertthat", "crayon", "debugme", "R6"), character(0), character(0), "lattice", character(0), "backports", character(0), c("magrittr", "assertthat"), character(0), c("assertthat", "R6", "crayon", "rprojroot"), c("irlba", "magrittr", "Matrix", "pkgconfig"), character(0), character(0), "crayon", character(0), "Matrix", c("callr", "clisymbols", "crayon", "desc", "digest", "prettyunits", "R6", "rprojroot", "withr"), c("processx", "R6"), character(0), character(0) )) ) tree(data)
#> processx #> ├─assertthat #> ├─crayon #> ├─debugme #> │ └─crayon #> └─R6
tree(data, root = "rcmdcheck")
#> rcmdcheck #> ├─callr #> │ ├─processx #> │ │ ├─assertthat #> │ │ ├─crayon #> │ │ ├─debugme #> │ │ │ └─crayon #> │ │ └─R6 #> │ └─R6 #> ├─clisymbols #> ├─crayon #> ├─desc #> │ ├─assertthat #> │ ├─R6 #> │ ├─crayon #> │ └─rprojroot #> │ └─backports #> ├─digest #> ├─prettyunits #> │ ├─magrittr #> │ └─assertthat #> ├─R6 #> ├─rprojroot #> │ └─backports #> └─withr
data$label <- paste(data$package, style_dim(paste0("(", c("2.0.0.1", "1.1.1", "0.2.0", "1.2-11", "1.5", "1.2", "1.2.0", "1.0.2", "2.0.0", "1.1.1.9000", "1.1.2", "2.2.2", "1.3.4", "1.0.2", "0.6.12", "2.2.1", "1.2.1.9002", "1.0.0.9000", "2.0.1", "0.20-35"), ")")) ) roots <- ! data$package %in% unlist(data$dependencies) data$label[roots] <- col_cyan(style_italic(data$label[roots])) tree(data, root = "rcmdcheck")
#> rcmdcheck (1.2.1.9002)
#> ├─callr (1.0.0.9000)
#> │ ├─processx (2.0.0.1)
#> │ │ ├─assertthat (0.2.0)
#> │ │ ├─crayon (1.3.4)
#> │ │ ├─debugme (1.0.2)
#> │ │ │ └─crayon (1.3.4)
#> │ │ └─R6 (2.2.2)
#> │ └─R6 (2.2.2)
#> ├─clisymbols (1.2.0)
#> ├─crayon (1.3.4)
#> ├─desc (1.1.1.9000)
#> │ ├─assertthat (0.2.0)
#> │ ├─R6 (2.2.2)
#> │ ├─crayon (1.3.4)
#> │ └─rprojroot (1.2)
#> │ └─backports (1.1.1)
#> ├─digest (0.6.12)
#> ├─prettyunits (1.0.2)
#> │ ├─magrittr (1.5)
#> │ └─assertthat (0.2.0)
#> ├─R6 (2.2.2)
#> ├─rprojroot (1.2)
#> │ └─backports (1.1.1)
#> └─withr (2.0.0)
pkgdeps <- list( "[email protected]" = c("[email protected]", "[email protected]", "[email protected]", "[email protected]", "[email protected]", "[email protected]", "[email protected]", "[email protected]"), "[email protected]" = character(), "[email protected]" = character(), "[email protected]" = character(), "[email protected]" = character(), "[email protected]" = character(), "[email protected]" = character(), "[email protected]" = character(), "[email protected]" = c("[email protected]", "[email protected]", "[email protected]", "[email protected]", "[email protected]", "[email protected]"), "[email protected]" = c("[email protected]", "[email protected]"), "[email protected]" = character(), "[email protected]" = character(), "[email protected]" = c("[email protected]", "[email protected]", "[email protected]", "[email protected]", "[email protected]", "[email protected]"), "[email protected]" = character(), "[email protected]" = c("[email protected]", "[email protected]", "[email protected]", "[email protected]", "[email protected]", "[email protected]"), "[email protected]" = character(), "[email protected]" = c("[email protected]"), "[email protected]" = character(), "[email protected]" = character(), "[email protected]" = character(), "[email protected]" = c("[email protected]", "[email protected]", "[email protected]", "[email protected]"), "[email protected]" = c("[email protected]", "[email protected]") ) pkgs <- data.frame( stringsAsFactors = FALSE, name = names(pkgdeps), deps = I(unname(pkgdeps)) ) tree(pkgs, trim = TRUE)
#> [email protected] #> ├─[email protected] #> ├─[email protected] #> ├─[email protected] #> ├─[email protected] #> ├─[email protected] #> ├─[email protected] #> ├─[email protected] #> │ ├─[email protected] #> │ │ ├─[email protected] #> │ │ └─[email protected] #> │ ├─[email protected] #> │ ├─[email protected] #> │ ├─[email protected] #> │ │ ├─[email protected] #> │ │ ├─[email protected] #> │ │ ├─[email protected] #> │ │ ├─[email protected] #> │ │ ├─[email protected] #> │ │ └─[email protected] #> │ │ ├─[email protected] #> │ │ ├─[email protected] #> │ │ │ └─[email protected] #> │ │ ├─[email protected] #> │ │ ├─[email protected] #> │ │ ├─[email protected] #> │ │ └─[email protected] #> │ ├─[email protected] #> │ └─[email protected] #> └─[email protected] #> ├─[email protected] #> ├─[email protected] #> └─[email protected]
# Mark the trimmed nodes pkgs$label <- pkgs$name pkgs$trimmed <- paste(pkgs$name, " (trimmed)") tree(pkgs, trim = TRUE)
#> [email protected] #> ├─[email protected] #> ├─[email protected] #> ├─[email protected] #> ├─[email protected] #> ├─[email protected] #> ├─[email protected] #> ├─[email protected] #> │ ├─[email protected] #> │ │ ├─[email protected] (trimmed) #> │ │ └─[email protected] #> │ ├─[email protected] (trimmed) #> │ ├─[email protected] #> │ ├─[email protected] #> │ │ ├─[email protected] (trimmed) #> │ │ ├─[email protected] (trimmed) #> │ │ ├─[email protected] (trimmed) #> │ │ ├─[email protected] (trimmed) #> │ │ ├─[email protected] #> │ │ └─[email protected] #> │ │ ├─[email protected] #> │ │ ├─[email protected] #> │ │ │ └─[email protected] (trimmed) #> │ │ ├─[email protected] #> │ │ ├─[email protected] (trimmed) #> │ │ ├─[email protected] (trimmed) #> │ │ └─[email protected] #> │ ├─[email protected] #> │ └─[email protected] (trimmed) #> └─[email protected] #> ├─[email protected] (trimmed) #> ├─[email protected] (trimmed) #> └─[email protected] (trimmed)
Character vector, the lines of the tree drawing.
If your platform supports at least 256 colors, then you can configure
the colors that cli uses for the eight base and the eight bright colors.
(I.e. the colors of col_black()
, col_red()
, and col_br_black()
,
col_br_red()
, etc.
truecolor ansi_palettes ansi_palette_show(palette = NULL, colors = num_ansi_colors(), rows = 4)
truecolor ansi_palettes ansi_palette_show(palette = NULL, colors = num_ansi_colors(), rows = 4)
palette |
The palette to show, in the same format as for the
|
colors |
Number of ANSI colors to use the show the palette. If the platform does not have sufficient support, the output might have a lower color resolution. Without color support it will have no color at all. |
rows |
The number of colored rows to print. |
truecolor
is an integer scalar.
ansi_palettes
is a data frame with one row for each palette,
and one column for each base ANSI color. attr(ansi_palettes, "info")
contains a list with information about each palette.
truecolor
is an integer constant for the number of 24 bit ANSI colors.
To customize the default palette, set the cli.palette
option to the
name of a built-in palette (see ansi_palettes()
), or the list of
16 colors. Colors can be specified with RGB colors strings:
#rrggbb
or R color names (see the output of grDevices::colors()
).
For example, you can put this in your R profile:
options(cli.palette = "vscode")
It is currently not possible to configure the background colors separately, these will be always the same as the foreground colors.
If your platform only has 256 colors, then the colors specified in the palette have to be interpolated. On true color platforms they RGB values are used as-is.
ansi_palettes
is a data frame of the built-in palettes, each row
is one palette.
ansi_palette_show()
shows the colors of an ANSI palette on the screen.
ansi_palette_show
returns a character vector, the rows that
are printed to the screen, invisibly.
ansi_palettes ansi_palette_show("dichro", colors = truecolor)
ansi_palettes ansi_palette_show("dichro", colors = truecolor)
Break an UTF-8 character vector into grapheme clusters
utf8_graphemes(x)
utf8_graphemes(x)
x |
Character vector. |
List of characters vectors, the grapheme clusters of the input string.
Other UTF-8 string manipulation:
utf8_nchar()
,
utf8_substr()
# Five grapheme clusters str <- paste0( "\U0001f477\U0001f3ff\u200d\u2640\ufe0f", "\U0001f477\U0001f3ff", "\U0001f477\u200d\u2640\ufe0f", "\U0001f477\U0001f3fb", "\U0001f477\U0001f3ff") cat(str, "\n") chrs <- utf8_graphemes(str)
# Five grapheme clusters str <- paste0( "\U0001f477\U0001f3ff\u200d\u2640\ufe0f", "\U0001f477\U0001f3ff", "\U0001f477\u200d\u2640\ufe0f", "\U0001f477\U0001f3fb", "\U0001f477\U0001f3ff") cat(str, "\n") chrs <- utf8_graphemes(str)
By default it counts Unicode grapheme clusters, instead of code points.
utf8_nchar(x, type = c("chars", "bytes", "width", "graphemes", "codepoints"))
utf8_nchar(x, type = c("chars", "bytes", "width", "graphemes", "codepoints"))
x |
Character vector, it is converted to UTF-8. |
type |
Whether to count graphemes (characters), code points, bytes, or calculate the display width of the string. |
Numeric vector, the length of the strings in the character vector.
Other UTF-8 string manipulation:
utf8_graphemes()
,
utf8_substr()
# Grapheme example, emoji with combining characters. This is a single # grapheme, consisting of five Unicode code points: # * `\U0001f477` is the construction worker emoji # * `\U0001f3fb` is emoji modifier that changes the skin color # * `\u200d` is the zero width joiner # * `\u2640` is the female sign # * `\ufe0f` is variation selector 16, requesting an emoji style glyph emo <- "\U0001f477\U0001f3fb\u200d\u2640\ufe0f" cat(emo) utf8_nchar(emo, "chars") # = graphemes utf8_nchar(emo, "bytes") utf8_nchar(emo, "width") utf8_nchar(emo, "codepoints") # For comparision, the output for width depends on the R version used: nchar(emo, "chars") nchar(emo, "bytes") nchar(emo, "width")
# Grapheme example, emoji with combining characters. This is a single # grapheme, consisting of five Unicode code points: # * `\U0001f477` is the construction worker emoji # * `\U0001f3fb` is emoji modifier that changes the skin color # * `\u200d` is the zero width joiner # * `\u2640` is the female sign # * `\ufe0f` is variation selector 16, requesting an emoji style glyph emo <- "\U0001f477\U0001f3fb\u200d\u2640\ufe0f" cat(emo) utf8_nchar(emo, "chars") # = graphemes utf8_nchar(emo, "bytes") utf8_nchar(emo, "width") utf8_nchar(emo, "codepoints") # For comparision, the output for width depends on the R version used: nchar(emo, "chars") nchar(emo, "bytes") nchar(emo, "width")
This function uses grapheme clusters instead of Unicode code points in UTF-8 strings.
utf8_substr(x, start, stop)
utf8_substr(x, start, stop)
x |
Character vector. |
start |
Starting index or indices, recycled to match the length
of |
stop |
Ending index or indices, recycled to match the length of
|
Character vector of the same length as x
, containing
the requested substrings.
Other UTF-8 string manipulation:
utf8_graphemes()
,
utf8_nchar()
# Five grapheme clusters, select the middle three str <- paste0( "\U0001f477\U0001f3ff\u200d\u2640\ufe0f", "\U0001f477\U0001f3ff", "\U0001f477\u200d\u2640\ufe0f", "\U0001f477\U0001f3fb", "\U0001f477\U0001f3ff") cat(str) str24 <- utf8_substr(str, 2, 4) cat(str24)
# Five grapheme clusters, select the middle three str <- paste0( "\U0001f477\U0001f3ff\u200d\u2640\ufe0f", "\U0001f477\U0001f3ff", "\U0001f477\u200d\u2640\ufe0f", "\U0001f477\U0001f3fb", "\U0001f477\U0001f3ff") cat(str) str24 <- utf8_substr(str, 2, 4) cat(str24)
This is utility function that calculates the state of a VT-5xx screen after a certain set of output.
vt_output(output, width = 80L, height = 25L)
vt_output(output, width = 80L, height = 25L)
output |
Character vector or raw vector. Character vectors are
collapsed (without a separater), and converted to a raw vector using
|
width |
Terminal width. |
height |
Terminal height. |
Currently it supports:
configurable terminal width and height
ASCII printable characters.
\n
, \r
.
ANSI SGR colors, 8 color mode, 256 color mode and true color mode.
Other ANSI SGR features: bold, italic, underline, strikethrough, blink, inverse.
It does not currently supports other features, mode notably:
Other ANSI control sequences and features. Other control sequences are silently ignored.
Wide Unicode characters. Their width is not taken into account correctly.
Unicode graphemes.
Data frame with columns lineno
, segmentno
, segment
,
attributes
.
This function is experimental, and the virtual temrinal API will likely change in future versions of cli.