Package 'huxtable'

Description

Huxtable is a package for creating HTML and LaTeX tables. It provides similar functionality to xtable, with a simpler interface.

Quick start

To create a huxtable object, use huxtable() or as_huxtable():

 library(huxtable)
 employees <- huxtable(
         Names    = c("Hadley", "Yihui", "Dirk"),
         Salaries = c(1e5, 1e5, 1e5),
         add_colnames = TRUE
       )
 car_hux <- as_hux(mtcars)

You can then set properties which affect how the huxtable is displayed:

 # make the first row bold:
 bold(employees)[1, ] <- TRUE

 # change the font size everywhere:
 font_size(employees) <- 10

Or you can use a tidyverse style with the pipe operator:

library(magrittr)
employees <- employees %>%
      set_font_size(10) %>%
      set_bold(1, everywhere, TRUE)

For more information, see the website or read the vignette with vignette("huxtable").

See huxtable-FAQ for frequently asked questions, including ways to get help.

To report a bug, or suggest an enhancement, visit github.

Author(s)

Maintainer: David Hugh-Jones [email protected]

See Also

Useful links:

• https://hughjonesd.github.io/huxtable/

• Report bugs at https://github.com/hughjonesd/huxtable/issues

Description

Subset a huxtable

Usage

## S3 method for class 'huxtable'
x[i, j, drop = FALSE]

## S3 replacement method for class 'huxtable'
x[i, j] <- value

## S3 replacement method for class 'huxtable'
x$name <- value

## S3 replacement method for class 'huxtable'
x[[i, j]] <- value

Arguments

Value

[ returns a huxtable. $ and [[ return data from the underlying data frame.

Replacing existing rows and columns

For the replacement function ⁠[<-⁠, if value is a huxtable, then its properties will be copied into x. Replacement functions ⁠$<-⁠ and ⁠[[<-⁠ replace existing data without affecting any properties.

Adding new rows and columns

If new columns or rows are created, then properties will be copied from the last column or row of x, or from value if value is a huxtable.

These methods are stricter than their data frame equivalents in some places. You can't add new rows or column at a numeric location without specifying all intervening rows/columns. New values must have the appropriate dimensions (vectors will be interpreted appropriately).

Examples

jams[1:3, ]
class(jams[1:3, ])
jams[, 1]
jams$Type
prices <- huxtable(c("Price", 1.70, 2.00, 2.20))
number_format(prices) <- 2
bold(prices) <- TRUE
jams[, 2] <- prices
jams

data(jams)
jams$price <- c("Price", 1.70, 2.00, 2.20)
jams

Description

Add a first row of column names, or a first column of row names, to the huxtable.

Usage

add_colnames(ht, rowname = NULL, ...)

add_rownames(ht, colname = "rownames", preserve_rownames = TRUE, ...)

Arguments

Details

Note that add_colnames will change the mode of all columns to character. Also note that it will move your rows down by one: what was row 1 will now be row 2, and the column names will now be row 1.

add_colnames preserves column names. add_rownames only preserves them if asked to.

Value

The modified object.

Examples

ht <- huxtable(
  First = rnorm(5),
  Second = rnorm(5),
  add_rownames = FALSE
)
add_rownames(ht)
add_colnames(ht)

# Out by 1:
add_rownames(add_colnames(ht))

# Better:
add_colnames(add_rownames(ht))

# Alternatively:
add_colnames(add_rownames(ht, ""))

Description

This adds a single row at the bottom. The first cell contains the footnote; it spans all table columns and has an optional border above.

Usage

add_footnote(ht, text, border = 0.8, number_format = NA, ...)

Arguments

Value

The modified huxtable

Examples

jams <- add_footnote(
  jams,
  "* subject to availability"
)
jams

Description

These functions combine two huxtables or similar objects and return the result.

Usage

add_rows(x, y, after = nrow(x), copy_cell_props = TRUE)

add_columns(x, y, after = ncol(x), copy_cell_props = TRUE)

Arguments

Details

Arguments in ... can include copy_cell_props.

Value

A huxtable.

See Also

insert_row() and insert_column(), which insert multiple values into a single row.

Examples

ht <- hux("Gooseberry", 2.15)
add_rows(jams, ht)
add_rows(jams, ht, after = 1)

mx <- matrix(
  c(
    "Sugar", "50%", "60%", "40%",
    "Weight (g)", 300, 250, 300
  ),
  4, 2
)
add_columns(jams, mx)

Description

Values may be "left", "center", "right", NA or a single character. If value is a single character (e.g. a decimal point), then the cell is aligned on this character.

Usage

align(ht)

align(ht) <- value

set_align(ht, row, col, value)

map_align(ht, row, col, fn)

Arguments

Aligning on a decimal point

To align cells on the decimal point, set align to "." or any other single character (e.g. "," in European languages).

By default, huxtable aligns these cells by padding with spaces. The mechanics of this were improved for LaTeX in version 5.3.0, but are still not perfect. Using a fixed-width font may help.

If options("huxtable.latex_siunitx_align") is set to TRUE, then in LaTeX output, numbers in these cells will be surrounded by ⁠\\tablenum{}⁠. See the siunitx documentation for more details. Note that this may have other side-effects, for example 1e3 becomes ⁠1 x 10^3⁠.

To use non-default decimal points, set both align(ht) and number_format(). See the example.

Examples

numbers <- c(1, 1.5, 1.03, 10, 10.01)
number_hux <- as_hux(matrix(numbers, 5, 5))
number_format(number_hux) <- "%.4g"
number_format(number_hux)[, 5] <- fmt_pretty(
  decimal.mark = ",",
  big.mark = ""
)

number_hux <- map_align(
  number_hux,
  by_cols("left", "center", "right", ".", ",")
)

alignments <- c(
  "left",
  "centre",
  "right",
  "decimal (.)",
  "decimal (,)"
)
number_hux <- rbind(
  alignments,
  number_hux
)

align(number_hux)
number_hux

Description

Huxtables can be converted to flextable::flextable() objects, for use in Word and Powerpoint documents.

Usage

as_flextable(x, ...)

## S3 method for class 'huxtable'
as_flextable(x, colnames_to_header = FALSE, ...)

Arguments

Details

With recent versions of "flextable" and Pandoc, huxtables can be automatically outputted from rmarkdown word_document and/or powerpoint_presentation documents. (Powerpoint presentations require pandoc version >= 2.4.0.)

Properties are supported, with the following exceptions:

• Rotation of 0, 90 or 270 is supported.

• Non-numeric widths and heights are not supported. Table heights are treated as a proportion of 9 inches; table widths are treated as a proportion of 6 inches. So e.g. height(ht) <- 0.5 will give a height of 4.5 inches.

• Table wrap and table position are not supported.

• Border style "double" is not supported and becomes "solid".

• Captions are supported with recent versions of flextable, but not caption_pos() or caption_width().

Value

an object of class flextable.

Challenge

Try to say as_flextable.huxtable ten times without pausing.

Examples

ht <- hux(a = 1:3, b = 1:3)
ft <- as_flextable(ht)
## Not run: 
my_doc <- officer::read_docx()
my_doc <- flextable::body_add_flextable(
  my_doc, ft
)
print(my_doc,
  target =
    "path/to/my_doc.docx"
)

## End(Not run)

Description

as_huxtable or as_hux converts an object to a huxtable. Conversion methods exist for data frames and tibbles, tables, ftables, matrices and (most) vectors.

Usage

as_huxtable(x, ...)

as_hux(x, ...)

## Default S3 method:
as_huxtable(
  x,
  add_colnames = getOption("huxtable.add_colnames", TRUE),
  add_rownames = FALSE,
  autoformat = getOption("huxtable.autoformat", TRUE),
  ...
)

## S3 method for class 'grouped_df'
as_huxtable(x, ..., groups_to_headers = FALSE)

is_huxtable(x)

is_hux(x)

Arguments

Details

is_hux[table] tests if an object is a huxtable.

For table objects, add_colnames and add_rownames are TRUE by default. For matrix objects, they are FALSE. Other classes use options("huxtable.add_colnames"), which is TRUE by default; add_rownames is FALSE.

For dplyr::grouped_df() objects, groups will be converted to header rows if groups_to_headers is TRUE.

Value

An object of class "huxtable".

Examples

dfr <- data.frame(
  a = 1:5,
  b = letters[1:5],
  stringsAsFactors = FALSE
)
as_huxtable(dfr)
mx <- matrix(letters[1:12], 4, 3)
as_huxtable(mx, add_colnames = FALSE)
library(stats)
tbl <- table(
  Wool    = warpbreaks$wool,
  Tension = warpbreaks$tension
)
as_huxtable(tbl) # adds row and column names by default

# adding rownames:
as_hux(mtcars[1:3, ],
  add_colnames = TRUE,
  add_rownames = "Car"
)

if (requireNamespace("dplyr")) {
  iris_grp <- dplyr::group_by(iris[c(1:4, 51:54, 101:104), ], Species)
  as_hux(iris_grp, groups_to_headers = TRUE)
}

Description

If the openxlsx package is installed, Huxtables can be converted to openxlsx::openxlsx() Worbook objects, for use in Excel documents.

Usage

as_Workbook(ht, ...)

## S3 method for class 'huxtable'
as_Workbook(
  ht,
  Workbook = NULL,
  sheet = "Sheet 1",
  write_caption = TRUE,
  start_row = 1,
  start_col = 1,
  ...
)

Arguments

Details

Use openxlsx::saveWorkbook() to save the resulting object to an Excel file.

Properties are supported with the following exceptions:

• Non-numeric column widths and row heights, table width and height.

• Decimal padding.

• Cell padding.

• Table position.

• Caption width.

Huxtable tries to guess appropriate widths and height for rows and columns; numeric width() and height() are treated as scaling factors.

Contents are only stored as numbers if a whole column is "numeric", i.e. can be converted by as.numeric()). Otherwise, they are stored as text.

Value

An object of class Workbook.

Examples

wb <- as_Workbook(jams)

## Not run: 
openxlsx::saveWorkbook(
  wb,
  "my-excel-file.xlsx"
)

## End(Not run)

# multiple sheets in a single workbook:
wb <- openxlsx::createWorkbook()
wb <- as_Workbook(jams,
  Workbook = wb, sheet = "sheet1"
)
wb <- as_Workbook(
  hux("Another", "huxtable"),
  Workbook = wb,
  sheet = "sheet2"
)

Description

Colors can be in any format understood by R:

• A color name like "darkred"

• A HTML string like "#FF0000"

• The result of a function like rgb(1, 0, 0) or grey(0.5)

Usage

background_color(ht)

background_color(ht) <- value

set_background_color(ht, row, col, value)

map_background_color(ht, row, col, fn)

Arguments

Details

Transparent colors are not guaranteed to work at present.

See Also

Other formatting functions: bold(), font(), font_size(), na_string(), number_format(), text_color()

Examples

background_color(jams) <- grey(0.7)
background_color(jams)

set_background_color(jams, "yellow")
set_background_color(jams, 2:3, 1, "yellow")
map_background_color(jams, by_rows("yellow", grey(0.7)))

Description

Make cell text bold or italic

Usage

bold(ht)

bold(ht) <- value

set_bold(ht, row, col, value = TRUE)

map_bold(ht, row, col, fn)

italic(ht)

italic(ht) <- value

set_italic(ht, row, col, value = TRUE)

map_italic(ht, row, col, fn)

Arguments

See Also

Other formatting functions: background_color(), font(), font_size(), na_string(), number_format(), text_color()

Examples

bold(jams) <- TRUE
bold(jams)

set_bold(jams, FALSE)
set_bold(
  jams,
  2:3, 1, FALSE
)
map_bold(
  jams,
  by_rows(FALSE, TRUE)
)

Description

brdr() objects can be passed into set_top_border() and friends. They set multiple border properties simultaneously.

Usage

brdr(thickness = 0.4, style = "solid", color = NA_character_)

Arguments

Value

An object of class "brdr".

Examples

set_bottom_border(jams, brdr(1, "solid", "red"))

Get thickness of a brdr() object

Description

Get thickness of a brdr() object

Usage

brdr_thickness(x)

Arguments

Value

A number or numeric matrix.

Examples

brdr_thickness(left_border(jams))
brdr_thickness(brdr(1, "solid", "red"))

Description

This function uses dplyr::case_when() to set cell properties.

Usage

by_cases(..., ignore_na = TRUE)

Arguments

Details

Within the formulas, the variable . will refer to the content of ht[rows, cols], after conversion to a vector.

case_when returns NA when no formula LHS is matched. To avoid this, set a default in the last formula: TRUE ~ default.

case_when can't deal with brdr() objects, so you cannot use these in by_cases().

Value

A function for use in ⁠map_***⁠ functions.

See Also

mapping-functions

Other mapping functions: by_colorspace(), by_function(), by_quantiles(), by_ranges(), by_regex(), by_rows(), by_values()

Examples

if (!requireNamespace("dplyr")) {
  stop("Please install the 'dplyr' package to run this example")
}

ht <- hux(runif(5), letters[1:5])

map_background_color(ht, by_cases(
  . == "a" ~ "red",
  . %in% letters ~ "green",
  . < 0.5 ~ "pink"
))

Description

by_colorspace() can be used to set background, border or text colors, visually differentiating high or low values.

Usage

by_colorspace(
  ...,
  range = NULL,
  na_color = NA,
  ignore_na = TRUE,
  colwise = FALSE
)

Arguments

Details

by_colorspace requires the "scales" package.

Value

A function for use in ⁠map_***⁠ functions.

See Also

mapping-functions

Other mapping functions: by_cases(), by_function(), by_quantiles(), by_ranges(), by_regex(), by_rows(), by_values()

Examples

if (!requireNamespace("scales")) {
  stop("Please install the \"scales\" package to run this example")
}
ht <- as_hux(matrix(rnorm(25), 5, 5))
map_background_color(
  ht,
  by_colorspace("red", "yellow", "blue")
)
map_background_color(
  ht,
  by_colorspace("red", "yellow", "blue",
    colwise = TRUE
  )
)

Description

This creates a simple wrapper around a function for use in map_xxx. Useful functions include scales and palettes from the scales package.

Usage

by_function(inner_fn, ignore_na = TRUE)

Arguments

Details

The argument of inner_fn will be as.matrix(ht[row, col]). Be aware how matrix conversion affects the mode of cell data.

Value

A function for use in ⁠map_***⁠ functions.

See Also

mapping-functions

Other mapping functions: by_cases(), by_colorspace(), by_quantiles(), by_ranges(), by_regex(), by_rows(), by_values()

Examples

ht <- as_hux(matrix(runif(20), 5, 4))

map_background_color(
  ht,
  by_function(grey)
)

if (requireNamespace("scales")) {
  map_text_color(ht, by_function(
    scales::seq_gradient_pal()
  ))
}

Description

These functions split cell values by quantiles. Non-numeric cells are ignored.

Usage

by_quantiles(
  quantiles,
  values,
  right = FALSE,
  extend = TRUE,
  ignore_na = TRUE,
  colwise = FALSE
)

by_equal_groups(n, values, ignore_na = TRUE, colwise = FALSE)

Arguments

Details

by_equal_groups(n, values) splits the data into n equal-sized groups (i.e. it is a shortcut for by_quantiles(seq(1/n, 1 - 1/n, 1/n), values)).

Value

A function for use in ⁠map_***⁠ functions.

See Also

mapping-functions

Other mapping functions: by_cases(), by_colorspace(), by_function(), by_ranges(), by_regex(), by_rows(), by_values()

Examples

ht <- hux(rnorm(5), rnorm(5))

map_background_color(
  ht,
  by_quantiles(
    c(0.2, 0.8),
    c("red", "yellow", "green")
  )
)

map_background_color(
  ht,
  by_quantiles(
    c(0.2, 0.8),
    c("red", "yellow", "green"),
    colwise = TRUE
  )
)

map_background_color(
  ht,
  by_equal_groups(
    3,
    c("red", "yellow", "green")
  )
)

Description

by_ranges() sets property values for cells falling within different numeric ranges.

Usage

by_ranges(breaks, values, right = FALSE, extend = TRUE, ignore_na = TRUE)

Arguments

Details

Non-numeric cells return NA. The effects of this depend on ignore_na.

Value

A function for use in ⁠map_***⁠ functions.

See Also

mapping-functions

Other mapping functions: by_cases(), by_colorspace(), by_function(), by_quantiles(), by_regex(), by_rows(), by_values()

Examples

ht <- huxtable(c(1, 3, 5))
map_background_color(
  ht,
  by_ranges(
    c(2, 4),
    c("red", "yellow", "blue")
  )
)

map_background_color(
  ht,
  by_ranges(
    c(2, 4),
    "pink",
    extend = FALSE
  )
)

map_background_color(
  ht,
  by_ranges(
    c(1, 5),
    c("red", "yellow", "green"),
    right = TRUE
  )
)
map_background_color(
  ht,
  by_ranges(
    c(1, 5),
    c("red", "yellow", "green"),
    right = FALSE
  )
)

Description

by_regex() sets properties on cells which match a regular expression.

Usage

by_regex(..., .grepl_args = list(), ignore_na = TRUE)

Arguments

Value

A function for use in ⁠map_***⁠ functions.

See Also

mapping-functions

Other mapping functions: by_cases(), by_colorspace(), by_function(), by_quantiles(), by_ranges(), by_rows(), by_values()

Examples

ht <- hux(c("The cat sat", "on the", "mat"))

map_bold(ht, by_regex("at" = TRUE))
map_bold(ht, by_regex("a.*a" = TRUE))

map_bold(ht, by_regex(
  "the" = TRUE,
  .grepl_args = list(
    ignore.case = TRUE
  )
))

Description

by_rows and by_cols set properties in horizontal or vertical "stripes".

Usage

by_rows(..., from = 1, ignore_na = TRUE)

by_cols(..., from = 1, ignore_na = TRUE)

Arguments

Value

A function for use in ⁠map_***⁠ functions.

See Also

mapping-functions

Other mapping functions: by_cases(), by_colorspace(), by_function(), by_quantiles(), by_ranges(), by_regex(), by_values()

Examples

ht <- as_hux(matrix(rnorm(25), 5, 5))
map_background_color(
  ht,
  by_rows("green", "grey")
)
map_background_color(
  ht,
  by_cols("green", "grey")
)

Description

Use by_values() to set properties for cells with specific, pre-determined contents.

Usage

by_values(..., ignore_na = TRUE)

Arguments

Value

A function for use in ⁠map_***⁠ functions.

See Also

mapping-functions

Other mapping functions: by_cases(), by_colorspace(), by_function(), by_quantiles(), by_ranges(), by_regex(), by_rows()

Examples

ht <- hux(letters[1:3])
map_background_color(
  ht,
  by_values(a = "red", c = "yellow")
)
map_background_color(
  ht,
  by_values(a = "red", c = "yellow", "green")
)

Description

By default, captions are displayed above the table. You can change this with caption_pos().

Usage

caption(ht)

caption(ht) <- value

set_caption(ht, value)

Arguments

Details

Captions are not escaped. See the example for a workaround.

Value

property() returns the property value(s). set_property() and map_property() return the modified huxtable.

See Also

Other caption properties: caption_pos(), caption_width()

Examples

set_caption(jams, "Pots of jam for sale")
# escape caption characters:
caption(jams) <- sanitize(
  "Make $$$ with jam",
  type = "latex"
)

Description

If caption_pos is "top" or "bottom", then the horizontal position ("left", "center" or "right") will be determined by the huxtable"s position().

Usage

caption_pos(ht)

caption_pos(ht) <- value

set_caption_pos(ht, value)

Arguments

Value

property() returns the property value(s). set_property() and map_property() return the modified huxtable.

See Also

Other caption properties: caption(), caption_width()

Examples

caption(jams) <- "Jam for sale"
jams
set_caption_pos(jams, "bottom")

Description

A numeric widths is interpreted as a proportion of text width in LaTeX, or of width of the containing element in HTML. A character width must be a valid LaTeX or CSS dimension. The default, NA, makes the caption the same width as the table.

Usage

caption_width(ht)

caption_width(ht) <- value

set_caption_width(ht, value)

Arguments

Value

property() returns the property value(s). set_property() and map_property() return the modified huxtable.

See Also

Other caption properties: caption(), caption_pos()

Examples

set_caption_width(jams, 0.5)

Description

These methods are called when one argument to cbind/rbind is a huxtable. As well as combining cell contents, they copy table, row, column and/or cell properties into the returned result.

Usage

## S3 method for class 'huxtable'
cbind(..., deparse.level = 1, copy_cell_props = TRUE)

## S3 method for class 'huxtable'
rbind(..., deparse.level = 1, copy_cell_props = TRUE)

Arguments

Details

Table properties will be taken from the first argument which is a huxtable. So will row properties (for cbind) and column properties (for rbind).

If some of the inputs are not huxtables, and copy_cell_props isTRUE, then cell properties will be copied to non-huxtables. Objects on the left or above get priority over those on the right or below.

If copy_cell_props is FALSE, cells from non-huxtable objects will get the default properties.

You cannot bind huxtables with data frames, since the R method dispatch will always call the data frame method instead of the huxtable-specific code. For a solution, see add_columns().

Value

A huxtable.

Examples

sugar <- c("Sugar", "40%", "35%", "50%")
jams <- set_bold(jams, 1, everywhere)
cbind(jams, sugar)
cbind(jams, sugar,
  copy_cell_props = FALSE
)

jams <- set_text_color(
  jams,
  everywhere, 1, "red"
)
rbind(jams, c("Damson", 2.30))
rbind(jams, c("Damson", 2.30),
  copy_cell_props = FALSE
)

Description

Numeric column widths are treated as proportions of the table width. Character widths must be valid CSS or LaTeX dimensions.

Usage

col_width(ht)

col_width(ht) <- value

set_col_width(ht, col, value)

Arguments

Details

In LaTeX, if you specify a column width, but set wrap to FALSE and have cells which overrun, then you may have problems with table position and with background colours in other cells. The workaround is to adjust the width, so that your cells no longer overrun.

Value

col_width() returns the col_width property. set_col_width() returns the modified huxtable.

See Also

Other table measurements: height(), row_height(), width()

Examples

col_width(jams) <- c(.2, .8)
col_width(jams)

jams$Notes <- c(
  "Notes",
  "This year's finest", "", ""
)
jams
set_col_width(jams, c(.4, .5, .1))

Description

Convert a column to header rows

Usage

column_to_header(
  ht,
  col,
  ...,
  glue = "{value}",
  start_col = 1,
  ignore_headers = TRUE,
  set_headers = TRUE
)

Arguments

Examples

column_to_header(jams, "Type")
column_to_header(jams, "Type", text_color = "red")
column_to_header(jams, "Price",
  number_format = 2,
  italic = TRUE,
  glue = "Price: {value}"
)

iris_hux <- as_hux(iris[c(1:4, 51:54, 101:104), ])
column_to_header(iris_hux, "Species",
  markdown = TRUE,
  glue = "Species: **{value}**"
)

Description

Setting escape_contents to FALSE allows you to include raw HTML or TeX code in your cells.

Usage

escape_contents(ht)

escape_contents(ht) <- value

set_escape_contents(ht, row, col, value)

map_escape_contents(ht, row, col, fn)

Arguments

Details

If markdown() is TRUE for a cell, the escape_contents property will be ignored.

See Also

sanitize() for escaping text manually.

Examples

ht <- huxtable(
  Text   = "x squared",
  Maths  = "$x^2$"
)
ht <- set_escape_contents(ht, FALSE)
## Not run: 
quick_pdf(ht)

## End(Not run)

Description

This is a convenience function to use in row and column specifications. In that context, it returns the last n row or column numbers of the huxtable.

Usage

final(n = 1)

Arguments

Details

Technically, final returns a two-argument function - see rowspecs for more details.

Examples

set_bold(jams, final(2), final(1), TRUE)

Description

fmt_ functions are designed to work with number_format().

Usage

fmt_percent(digits = 1, format = "f", ...)

Arguments

Value

An object you can pass into number_format().

See Also

Other format functions: fmt_pretty()

Examples

jams$Sugar <- c(
  "Sugar content",
  0.4, 0.35, 0.45
)
set_number_format(
  jams, -1, "Sugar",
  fmt_percent(1)
)

Description

Use prettyNum() to format numbers

Usage

fmt_pretty(big.mark = ",", ..., scientific = FALSE)

Arguments

Value

An object you can pass into number_format().

See Also

Other format functions: fmt_percent()

Examples

jams$Sales <- c(
  "Sales", 35000,
  55500, 20000
)
set_number_format(
  jams, -1, "Sales",
  fmt_pretty()
)

Description

Set the font for cell text

Usage

font(ht)

font(ht) <- value

set_font(ht, row, col, value)

map_font(ht, row, col, fn)

Arguments

Details

To find out what fonts are on your system, systemfonts::match_font() is useful.

For HTML, you can use comma-separated lists of font names like "Times New Roman, Times, Serif". This is not portable, though.

LaTeX and HTML use different font names. To use the same font names across document formats, see options("huxtable.latex_use_fontspec") in huxtable-options.

See Also

Other formatting functions: background_color(), bold(), font_size(), na_string(), number_format(), text_color()

Examples

font(jams) <- "times"
font(jams)

set_font(jams, "arial")
set_font(jams, 2:3, 1, "arial")
map_font(jams, by_rows("arial", "times"))

Description

Font size is in points.

Usage

font_size(ht)

font_size(ht) <- value

set_font_size(ht, row, col, value)

map_font_size(ht, row, col, fn)

Arguments

See Also

Other formatting functions: background_color(), bold(), font(), na_string(), number_format(), text_color()

Examples

font_size(jams) <- 14
font_size(jams)

jams2 <- set_font_size(
  jams,
  12
)
font_size(jams2)

jams3 <- set_font_size(
  jams,
  2:3, 1, 12
)
font_size(jams3)

jams4 <- map_font_size(
  jams,
  by_rows(
    12,
    14
  )
)
font_size(jams4)

Description

Convenience function which tries to guess the ultimate output from knitr and rmarkdown.

Usage

guess_knitr_output_format()

Value

"html", "latex", "typst", or something else. If we are not in a knitr document, returns an empty string.

Examples

## Not run: 
# in a knitr document
guess_knitr_output_format()

## End(Not run)

Description

Arbitrary rows and columns can be headers: they do not have to be at the top or left of the table.

Usage

header_cols(ht)

header_cols(ht) <- value

set_header_cols(ht, col, value)

header_rows(ht)

header_rows(ht) <- value

set_header_rows(ht, row, value)

Arguments

Details

By default header rows and columns are not shown differently from other rows, but you can change this with style_headers(). Various themes may set properties on headers. Lastly, headers are treated differently when restacking.

Examples

jams <- set_header_rows(jams, 1, TRUE)
jams <- set_header_cols(jams, 1, TRUE)
style_headers(jams,
  bold       = TRUE,
  text_color = "purple"
)

Description

height() sets the height of the entire table, while row_height() sets the height of individual rows. A numeric height is treated as a proportion of the containing block (HTML) or ⁠\textheight⁠ (LaTeX). A character height must be a valid CSS or LaTeX dimension.

Usage

height(ht)

height(ht) <- value

set_height(ht, value)

Arguments

Value

property() returns the property value(s). set_property() and map_property() return the modified huxtable.

See Also

Other table measurements: col_width(), row_height(), width()

Examples

set_height(jams, 0.4)

Description

Returns a randomized huxtable logo, inspired by Mondrian.

Usage

hux_logo(compact = FALSE, latex = NULL)

Arguments

Value

A huxtable.

Examples

# Default logo
print_screen(hux_logo())

# Compact single-row version
print_screen(hux_logo(compact = TRUE))

Description

Create a huxtable to display model output

Usage

huxreg(
  ...,
  error_format = "({std.error})",
  error_pos = c("below", "same", "right"),
  number_format = "%.3f",
  align = ".",
  ci_level = NULL,
  tidy_args = NULL,
  glance_args = NULL,
  stars = c(`***` = 0.001, `**` = 0.01, `*` = 0.05),
  bold_signif = NULL,
  borders = 0.4,
  outer_borders = 0.8,
  note = if (is.null(stars)) NULL else "{stars}.",
  statistics = c(N = "nobs", R2 = "r.squared", "logLik", "AIC"),
  coefs = NULL,
  omit_coefs = NULL
)

Arguments

Details

Models must have a generics::tidy() method defined, which should return "term", "estimate", "std.error", "statistic" and "p.value". The "broom" package provides methods for many model objects. If the tidy method does not have a conf.int option, huxreg will calculate confidence intervals itself, using a normal approximation.

If ... has names or contains a single named list, the names will be used for column headings. Otherwise column headings will be automatically created.

If the coef and/or statistics vectors have names, these will be used for row headings. If different values of coef have the same name, the corresponding rows will be merged in the output.

statistics should be column names from generics::glance(). You can also use "nobs" for the number of observations. If statistics is NULL then all columns from glance will be used. To use no columns, set statistics = character(0).

error_format is a string to be interpreted by glue::glue(). Terms in parentheses will be replaced by computed values. You can use any columns returned by tidy: typical columns include statistic, p.value, std.error, as well as conf.low and conf.high if you have set ci_level. For example, to show confidence intervals, you could write error_format = "{conf.low} to {conf.high}".

Value

A huxtable object.

Fixing p values manually

If you wish to use e.g. robust standard errors, you can pass results from e.g. lmtest::coeftest() into huxreg, since these objects have tidy methods. Alternatively, to manually insert your own statistics, see tidy_override().

Examples

if (!requireNamespace("broom")) {
  stop("Please install 'broom' to run this example.")
}

lm1 <- lm(mpg ~ cyl, mtcars)
lm2 <- lm(mpg ~ cyl + hp, mtcars)
glm1 <- glm(I(mpg > 20) ~ cyl, mtcars,
  family = binomial
)

huxreg(lm1, lm2, glm1)

if (requireNamespace("sandwich") &&
  requireNamespace("lmtest")) {
  lm_robust <- lmtest::coeftest(lm1,
    vcov = sandwich::vcovHC
  )
  # coeftest() has no "glance" method:
  huxreg(lm_robust,
    statistics = character(0)
  )
}

Description

huxtable, or hux, creates a huxtable object.

Usage

huxtable(
  ...,
  add_colnames = getOption("huxtable.add_colnames", TRUE),
  add_rownames = FALSE,
  autoformat = getOption("huxtable.autoformat", TRUE)
)

hux(
  ...,
  add_colnames = getOption("huxtable.add_colnames", TRUE),
  add_rownames = FALSE,
  autoformat = getOption("huxtable.autoformat", TRUE)
)

tribble_hux(
  ...,
  add_colnames = getOption("huxtable.add_colnames", TRUE),
  autoformat = getOption("huxtable.autoformat", TRUE)
)

Arguments

Details

If you use add_colnames or add_rownames, be aware that these will shift your rows and columns along by one: your old row/column 1 will now be row/column 2, etc.

add_colnames defaults to TRUE. You can set the default globally by setting options("huxtable.add_colnames") to TRUE or FALSE.

tribble_hux is a simple wrapper around tibble::tribble() which lets you create data in a readable format. It requires the "tibble" package to be installed.

Value

An object of class huxtable.

Automatic formatting

If autoformat is TRUE, then columns will have number_format() and align() properties set automatically, as follows:

• Integer columns will have number_format set to 0.

• Other numeric columns will have number_format set to "%.3g".

• All other columns will have number_format set to NA (no formatting).

• Integer, Date and date-time (i.e. POSIXct and POSIXlt) columns will be right-aligned.

• Other numeric columns will be aligned on options("OutDec"), usually ".".

• Other columns will be left aligned.

You can change these defaults by editing options("huxtable.autoformat_number_format") and options("huxtable.autoformat_align"). See huxtable-package for more details.

Automatic alignment also applies to column headers if add_colnames is TRUE; headers of columns aligned on a decimal point will be right-aligned. Automatic number formatting does not apply to column headers.

See Also

huxtable-options

Examples

ht <- huxtable(
  column1 = 1:5,
  column2 = letters[1:5]
)
ht
tribble_hux(
  ~Name, ~Salary,
  "John Smith", 50000,
  "Jane Doe", 50000,
  "David Hugh-Jones", 50000,
  add_colnames = TRUE
)

Description

A FAQ of common issues.

Details

• I get a LaTeX error when I try to compile my document!

  Have you installed the LaTeX packages you need? LaTeX packages are different from R packages. Run check_latex_dependencies() to find out if you are missing any. Then install them using your system's LaTeX management application. Or you can try install_latex_dependencies().

  In some rmarkdown and LaTeX formats, you also need to add LaTeX dependencies manually. Run report_latex_dependencies() and add the output to your LaTeX preamble, or in Rmarkdown formats, add it to the rmarkdown header like this:

  header-includes:
    - \usepackage{array}
    - \usepackage{caption}
    ... et cetera
  

• Huxtable isn't working in my Rmarkdown beamer_presentation slides.

  You may need to set the beamer "fragile" option, like this:

  # Slide title {.fragile}
  

• Numbers in my cells look weird!

  You can change numeric formatting using number_format(). Base R options like scipen usually have no effect.

• How can I use HTML, TeX etc. in my table?

  Use escape_contents():

  jams |>
       add_footnote("These jams are <i>tasty</i>!") |>
       set_escape_contents(final(1), everywhere, FALSE) |>
       quick_html()
  

  Alternatively you might consider using markdown in cells, with set_markdown_contents().

• I ran caption(ht) <- "Something" and got an error message:

  Error in UseMethod("caption<-") :
  no applicable method for 'caption<-' applied to an object of class "c('huxtable',   'data.frame')"
  

  You may have loaded another package with a caption method, e.g. "xtable". Try loading huxtable after xtable.

• How can I get line breaks in my cells?

  Just insert a line break "\n" in the cell contents. Then make sure that width() is set and wrap() is TRUE (it is by default).

• How can I change the font size, font etc. of captions?

  There are no direct commands for this. You have to use raw HTML/TeX/other commands within the caption itself. For example to have a bold caption in HTML, you might do something like:

  set_caption(jams, "<b>Jam Prices</b>")
  

• How do I refer to tables in bookdown?

  As of version 4.3.0, this is handled automatically for you. Just set the label using label(), then in markdown text do e.g.:

  \@ref(tab:my-table-label).
  

• How do I refer to tables in quarto?

  In quarto versions up to 1.3, or when compiling to HTML and other formats, simply use quarto cell labels like label: tbl-foo and refer to them via ⁠@tbl-foo⁠.

  In quarto versions 1.4 and above, when compiling to PDF, quarto cross-referencing no longer works. Instead, set labels within huxtable using label() or set_label() and refer to them with TeX-only referencing using ⁠\ref{label}⁠. You must also set a caption.

  Here's an example:

  A reference to Table \ref{tbl-jams}.
  
  ```{r}
  label(jams) <- "tbl-jams"
  caption(jams) <- "Some jams"
  jams
  ```
  

If you really need cross-referencing for both PDF and other output formats, either downgrade to quarto 1.3, use a different package, or write code to emit appropriate references.

• I called library(huxtable) and now my data.table objects are getting printed!

  Set options(huxtable.knit_print_df = FALSE).

• How can I set a property on an arbitrary group of cells?

  If you can't use the mapping-functions interface, and you want to set a property for multiple cells that aren't all in the same rows and/or columns, you could use a little-known fact about R subsetting. If you subset ht[x] where x is two-column numeric matrix, then each row of x indexes a single ⁠(row, column)⁠ cell. So, for example, here's how to set the background color of cells ⁠(2,1)⁠, ⁠(1, 3)⁠ and ⁠(4, 2)⁠ of a huxtable:

  indices <- matrix(c(2, 1, 1, 3, 4, 2), ncol = 2, byrow = TRUE)
  background_color(jams)[indices] <- "orange"
  

  Another useful trick sets properties on the diagonal, using diag():

  diag(background_color(jams)) <- "grey"
  

• I have another problem.

  If you have a bug - i.e. there is something wrong with the software - or a feature request, please report it to https://github.com/hughjonesd/huxtable/issues. Otherwise, ask a question on StackOverflow or https://forum.posit.co. That way, other people will benefit from the answers you get.

• Can I email you directly?

  I'd rather you asked on a public website. If you then email me a link, I may be able to help.

Author(s)

Maintainer: David Hugh-Jones [email protected]

See Also

Useful links:

• https://hughjonesd.github.io/huxtable/

• Report bugs at https://github.com/hughjonesd/huxtable/issues

Description

This help page simply gives the contents of NEWS.md.

huxtable 5.8.0

Other changes

• Redesigned hux_logo() function to spell out “huxtable” with customizable layout, fonts, and colors. Added compact and latex parameters for different output formats.

• Workaround for a bug in stringr 1.6.0.

huxtable 5.7.0

Breaking changes

• Functions are no longer generic, so you can’t subclass a huxtable object. AFAIK nobody has ever done this; if I’m wrong, please tell me.

• Reworked internals, with the help of OpenAI Codex.

Other changes

• HTML tables now wrap header rows in ⁠<thead>⁠ (using ⁠<th>⁠ cells) and body rows in ⁠<tbody>⁠ when header rows are at the top of the table.

• Added Typst export via to_typst() and print_typst(). Quarto integration is available as well as quick_typst(), quick_typst_pdf(), quick_typst_png(), and quick_typst_svg() functions.

• HTML output now uses CSS classes with a shared ⁠<style>⁠ block instead of long inline styles.

• Added as_html() for obtaining table as htmltools tags.

• to_screen() now displays double, dashed and dotted border styles.

huxtable 5.6.0

Breaking changes

• Removed underscore dplyr verbs (slice_, select_ etc.) These have long been deprecated in dplyr itself.

Other changes

• Bugfix: add newline at end of report_latex_dependencies() output. Thanks @ceresek.

• You can now add multiple huxtables to the same Excel worksheet in as_Workbook(). Suggestion by @oobd.

huxtable 5.5.7

• Bugfix: fix quarto referencing in quarto 1.5

• Bugfix: integer overflow on very large huxtables. Thanks @kpagacz.

huxtable 5.5.6

• Bugfix: quarto cross-referencing was giving too many warnings.

huxtable 5.5.5

• Bugfix: quarto cross-referencing doesn’t work for PDF with quarto version 1.4. See ?huxtable-FAQ for workarounds.

• Bugfix: by_cases() wasn’t picking up variables from the caller environment.

• huxtable 5.5.4 was never released due to failing a reverse dependency check.

huxtable 5.5.3

• Bugfix: disable quarto styling on HTML tables. You can reenable quarto processing with options(huxtable.quarto_process = TRUE).

• Bugfix: borders weren’t working with merged cells in Word documents.

huxtable 5.5.2

• Update by_cases() to work with dplyr 1.1.0. Within by_cases() formulas, . is now vector rather than matrix when dplyr version 1.1.0 is detected. Thanks @DavisVaughan.

• Add package checks in ⁠quick_*⁠ functions. Thanks @reuning.

huxtable 5.5.1

• CSS borders are now set explicitly even if they are all set to 0.

• Bugfix: shell-quote files in ⁠quick_*⁠ functions. Thanks to @ceresek.

• Bugfix: cope with adjustbox version “1.3a” among latex dependencies.

huxtable 5.5.0

• Huxtable should work with Quarto documents.

  • Quarto labels and captions will override huxtable-provided ones.

  • Quarto style references like ⁠@table-label⁠ only work with quarto labels.

  • Please report any bugs!

• New column_to_header() function converts a column to header rows. New as_hux() method for grouped_df objects optionally converts groups to header rows.

• New convenience functions stripe_rows() and stripe_columns().

• Add format and ... options to fmt_percent() to allow flexible formatting via formatC().

• add_footnote() gets an explicit number_format argument which is NA by default.

• Bugfix: infinite loop with wide characters in to_screen().

• Bugfix: duplicate colnames when exporting huxreg(..., error_pos = "right") to flextable.

• Bugfix: bookdown-style references weren’t working in blogdown.

huxtable 5.4.0

• New behaviour: setting colspan() or rowspan() overwrites the content of cells that have been shadowed.

  ht <- hux(c(1, 1), c(2, 2), c(3, 3))
  ht <- set_all_borders(ht)
  colspan(ht)[1, 1] <- 3
  
  # old behaviour                
  ht[, c(2, 1, 3)]
  ##   +--------------------------+
  ##   |                  2       |
  ##   +--------+--------+--------+
  ##   |      2 |      1 |      3 |
  ##   +--------+--------+--------+
  
  # new behaviour
  ht[, c(2, 1, 3)]
  ##   +--------------------------+
  ##   |                  1       |
  ##   +--------+--------+--------+
  ##   |      2 |      1 |      3 |
  ##   +--------+--------+--------+
  

• New option huxtable.latex_siunitx_align allows you to use the LaTeX siunitx package to handle decimal point alignment. This is FALSE by default.

• Bugfix: centre alignment was not working in print_screen().

• Bugfix: failure in to_md() with recent versions of stringi package.

• Bugfix: repeating a single row in a subset, like ht[c(1, 1, 2, 3), ], was setting colspan = 2 on the repeated row.

• Bugfix: zero-argument subset replacement like ht[] <- ... wasn’t working.

huxtable 5.3.0

• Improve decimal alignment in LaTeX when align(ht) == ".". This may change the appearance of some documents.

• Allow tidy_override() to extend columns of tidy and glance.

• Bugfix: #196 ^ was giving errors in LaTeX.

huxtable 5.2.0

• Add table_environment property so you can use e.g. "table*" in TeX.

• Bugfix: print_screen(h, colnames = FALSE) didn’t print a final newline.

• Bugfix: italic from markdown was being printed as underlined in TeX.

• Minor test update for compatibility with broom.

huxtable 5.1.1

• Minor test update for compatibility with broom.

• Fixes for R 4.1.0.

huxtable 5.1.0

• as_flextable() now exports markdown in cells to RTF, and to Word with the help of the optional ftExtra package. Thanks @atusy for adding this feature.

• Improvements to markdown screen export. This now uses the optional fansi package.

• New feature: as_Workbook() gains start_row and start_col arguments, to write a huxtable into an Excel worksheet starting at a particular row or column.

• New feature: huxreg() gains a glance_args argument to pass arguments to glance().

• New feature: options(huxtable.long_minus = TRUE) will try to use long minus signs before numbers. The default is FALSE. It will probably become TRUE in a future version.

• Bugfix: insert_row/column(..., after = 0) was unsetting table properties.

• Bugfix: unicode characters above 32767 were incorrectly represented in RTF. Thanks @kaigu1990.

• Bugfix: columns were being collapsed in as_Workbook().

• Bugfix: style_cells didn’t work unless huxtable was on the search path.

• Bugfix: merge_repeated_rows merged NA rows incorrectly.

• Bugfix: number format was not set correctly in huxreg()’s note.

• Bugfix: in huxreg(), tidy_args threw an error if the first argument to tidy() was a named list.

• Bugfix: tidy_replace() was broken.

• Clearer error messages for tidy_override() when extend = FALSE. In future, extend will probably default to TRUE.

Other news:

• Huxtable received its first Patreon sponsor! Thanks to Ross Mattheis.

huxtable 5.0.0

Huxtable 5.0.0 brings numerous changes. For a more user-friendly introduction, see https://hughjonesd.github.io/whats-new-in-huxtable-5.0.0.html.

Breaking changes

• There are changes to LaTeX output.

  • LaTeX ⁠\tabcolsep⁠ is now set to 0 within huxtable tables, while left and right padding should now take effect even when wrap is FALSE.

  • The default LaTeX table environment is now “tabular” unless width is set. If width is set, it is “tabularx”.

  • wrap only matters if width is set. Otherwise, cell wrapping is off.

  • the ⁠\centerbox⁠ macro from the LaTeX “adjustbox” package is used to centre tables. This should improve centring when tables are too wide. You may need to update the LaTeX “adjustbox” package to a recent version. check_latex_dependencies() can inform you about this.

• As previously signalled, add_colnames has now become TRUE by default in huxtable() and as_huxtable(). Set options(huxtable.add_colnames = FALSE) to go back to the old behaviour.

• Newlines in cell contents are now respected (in LaTeX, so long as wrap = TRUE and width has been set).

• Huxtable borders have been reworked, fixing some longstanding bugs and adding new features.

  • Borders are now automatically collapsed. For example:

    jams %>% 
        set_right_border(everywhere, 1, 1) %>% 
        set_left_border(everywhere, 2, 0.4)
    

    will set the border in between the columns of jams to 0.4, overwriting the previous value. This is more in line with what you would expect. For example, the following code now does what you probably want:

    jams %>% 
        set_rowspan(2, 1, 3) %>% 
        set_bottom_border(4, everywhere, 1)
    ##                 Type              Price  
    ##                 Strawberry         1.90  
    ##                                    2.10  
    ##                                    1.80  
    ##               ---------------------------
    

    instead of the old behaviour:

    jams %>% 
        set_rowspan(2, 1, 3) %>% 
        set_bottom_border(4, everywhere, 1)
    ##                 Type           Price  
    ##                 Strawberry      1.90  
    ##                                 2.10  
    ##                                 1.80  
    ##                            -----------
    

  • set_left_border(), set_all_borders() and friends all use a default value of 0.4. So to set a default border, write e.g.

    as_hux(head(iris)) %>% 
          set_bottom_border(1, everywhere)
    

  • A new brdr() class encapsulates border thickness, style and colour. You can set all properties at once by writing, e.g.:

    as_hux(jams) %>% 
          set_bottom_border(1, everywhere, brdr(1, "dotted", "darkgreen"))
    

    left_border(ht) and friends return a brdr object. To access the border thickness, write brdr_thickness(left_border(ht)).

• Various deprecated items have been removed:

  • The 3-argument form of ⁠set_*⁠. Instead, use ⁠map_*⁠.

  • The byrow argument to ⁠set_*⁠. Instead, use ⁠map_*⁠ and by_cols().

  • error_style and pad_decimal arguments in huxreg. Use error_format and align(hx) <- ".".

  • The where(), is_a_number() and pad_decimal() functions. Use ⁠map_*⁠ functions, ! is.na(as.numeric(x)), and align(ht) <- ".".

• Default padding has been increased to 6 points.

• By default, width() is now unset.

• By default, wrap() is now TRUE.

• every() has been renamed to stripe(), to avoid a clash with purrr::every(). everywhere, evens and odds are still the same.

• The little-used ability to set copy_cell_props to a character vector in rbind.huxtable and cbind.huxtable has been removed. You can still set it to FALSE.

• add_rows() and add_columns() now always call rbind.huxtable() or cbind.huxtable() and return a huxtable.

• Huxtable no longer supports dplyr versions less than 0.7.0 (released mid-2017).

• set_cell_properties() has been renamed style_cells(). It is retained as a soft-deprecated alias.

• Various themes have been tweaked:

  • theme_basic() now has bold headers and no header column by default.

  • theme_plain() defaults to position = "centre".

  • theme_striped() uses grey stripes, a white border, and subtler headers.

  • theme_article() has thinner borders.

Other changes

• You can now use markdown within table cells.

  • Use set_markdown(ht, rows, cols) to turn this on.

  • Or use the convenience function set_markdown_contents() to set cell contents that will be interpreted as markdown.

  • Markdown works for HTML and LaTeX. There’s basic support for on-screen display.

• Huxtable now has the concept of header row and columns.

  • By default, data frame column names will be headers.

  • To set other rows to be headers, use set_header_rows(ht, row_numbers, TRUE). For columns, use header_cols() or set_header_cols().

  • New functions style_headers(), style_header_cols(), and style_header_rows() to set multiple properties on headers.

  • In themes, header_row/col = TRUE set the first row/col to a header, and style all header rows/cols.

• set_bold() and set_italic() now use a default value of TRUE. So you can write e.g.

  as_hux(head(iris)) %>% 
        set_bold(1, everywhere)
  

• Console output in R now shows table position and caption position.

• By default, huxtable now sets labels from the current knitr chunk label, if there is one. This is consistent with kable(). In bookdown, you can then do e.g.

  Some iris species are shown in \@ref(tab:mytable):
  
  ```r
  as_hux(iris)
  ```
  

  Set options(huxtable.autolabel = FALSE) to turn off this behaviour.

• The one-argument form of [ now works for huxtables just as it does for data frames. For example, ht[2:3] selects columns 2 and 3.

• New functions fmt_percent() and fmt_pretty() for passing into number_format():

  jams$Sugar <-c ("Sugar content", 0.4, 0.35, 0.45)
  set_number_format(jams, -1, "Sugar", fmt_percent(1))
  

• split_across() and split_down() split a huxtable into a list of sub-tables. Headers can be automatically included.

• restack_across() and restack_down() split a huxtable, then join it back up. This is useful for making a table fit on a page.

• merge_across() and merge_down() merge an area of cells horizontally across rows, or vertically down columns.

• New functions ⁠set_lr_borders()/_border_colors()/_border_styles()/_padding()⁠ set left and right borders and padding simultaneously. New functions set_tb_borders() etc. set top and bottom properties simultaneously. There are map_ equivalents of all of these.

• set_outer_padding() sets padding around a range of cells, similarly to set_outer_borders().

• A new table-level property, caption_width(), allows you to set the width of the caption. The default, NA, sets the width equal to the table width.

• There are two new themes: theme_compact() and theme_bright().

• For huxreg(), a new function tidy_replace() allows you to replace the output of tidy(x) entirely.

• huxtable now only sets options(huxtable.knit_print_df = TRUE) if it is attached, not if it is loaded.

• huxtable supports dplyr::relocate(), new in dplyr 1.0.0.

• Improvements to as_flextable().

• Improvements to quick_pptx() (thanks @davidgohel).

• Bugfixes for options(huxtable.use_fontspec = TRUE).

• Bugfix: add_rownames = "string" now works as promised.

• Bugfix: non-ASCII characters are now supported in RTF.

Other news

• New versions of the gtsummary package will have an as_huxtable() method.

• Package texreg on CRAN includes a huxtablereg() function for creating a table of regression outputs.

huxtable 4.7.1

• The expss package now supports export to huxtables.

• by_quantiles(), by_equal_groups() and by_colorspace() have gained a colwise argument, which calculates quantiles or colors separately for each column.

• Add caption support for as_flextable() (thanks @sjewo).

huxtable 4.7.0

• Better error messages.

• New merge_repeated_rows() function: merge repeated rows into a single cell.

• New fill and colspan/rowspan arguments for insert_row()/insert_column():

  • insert_row(ht, "blah", "", "", "", "", ...) can be written insert_row(ht, "blah", fill = "").

  • colspan/rowspan set colspan/rowspan of the first cell in the inserted row/column.

huxtable 4.6.1

• Bugfix: right borders in wrong place when cells were merged.

• Bugfix: chinese characters were displaying wrongly in to_screen().

huxtable 4.6.0

• Set options('huxtable.latex_use_fontspec') to TRUE to use portable font names in TeX documents, with the LaTeX “fontspec” package.

• Bugfix: attributes were being copied wrongly in subset assignment of huxtables.

• Bugfix: text colors in hux_logo().

• Bugfix: rbind of huxtable and matrix wasn’t setting row_height correctly.

huxtable 4.5.0

• Add quick_latex() function.

• The texreg package now includes a huxtablereg function, analogous to huxreg, which outputs a huxtable from a list of regressions. This will be available from the next version of texreg.

huxtable 4.4.0

• Huxtables can now be printed directly in Word documents and Powerpoint presentations, thanks to the flextable package and recent versions of Pandoc. (Powerpoint printing requires Pandoc >= 2.4.0.)

• New “wrapleft” and “wrapright” options to position() allow text wrapping around tables.

• New set_outer_border_colors() and set_outer_border_styles() functions, like set_outer_borders().

• Huxtable no longer requires the broom package, instead using the generics package. If you use huxreg(), you will still need e.g. broom or broom.mixed to provide tidy() and glance() methods for specific models.

• Bugfix: tidy.tidy_override() and glance.tidy_override() should work even if underlying object has no tidy() or glance() method.

• Bugfix: huxtables had option clash when echo = TRUE in Rmd pdf_document format.

• Bugfix: caption() and height() weren’t playing nicely.

• Bugfix: mutate(..., copy_cell_props = FALSE) was adding a column named copy_cell_props.

• Bugfix: check_latex_dependencies and install_latex_dependencies gave misleading errors.

• Enhancement: when stars is NULL in huxreg, don’t print a note by default.

• Enhancement: use tinytex when available, allowing autoinstallation of latex packages.

huxtable 4.3.0

• More work on TeX. Tables should now compile when raw_attributes is not set.

• New map_xxx functions to set properties variably by cell values.

• Functions for mapping properties variably: by_rows, by_values, by_ranges, by_quantiles etc.

• Correct bookdown labels are now automatically created.

• New grey, blue, green and orange themes.

• New “themes” vignette.

• New tidy_override function to override p values etc. in huxreg.

• New set_contents function to change huxtable contents within dplyr pipes.

• Enhancement: left- and right-aligned captions are now set above the table in LaTeX, using the “threeparttable” package. You will need to install this using e.g. install_latex_dependencies() or tlmgr if it is not already on your system.

• Enhancement: in huxtable() and friends, add_rownames = "Colname" now sets the name for the new column.

• Improvements to the vignettes and help files.

• Bugfix: to_md could hang with bold/italic cells.

Deprecated

• The 3 argument form of set_xxx functions is deprecated, as is the where function. Use map_xxx instead.

• Argument byrow is soft-deprecated. Use by_cols() instead.

huxtable 4.2.1

• Bugfix: wrap=TRUE caused squeezed text in RTF.

Important

• TeX code was getting escaped by pandoc. To avoid this, if possible, huxtable now adds fenced code blocks round latex tables (see https://pandoc.org/MANUAL.html#extension-raw_attribute). You must add

  md_extensions: +raw_attribute

  to your YAML header for this to work, and you will need a recent (> 2.0.0) version of Pandoc.

huxtable 4.2.0

• More speedups: LaTeX 2-3x faster, as_Workbook 2-3x faster.

• Simplify LaTeX output using our own LaTeX commands.

• RTF support: new print_rtf, to_rtf and quick_rtf functions.

• New border_style properties to set “solid”, “double”, “dotted” or “dashed” borders. (At present, LaTeX only allows “solid” or “double”.)

• New merge_cells function, an alternative interface to colspan and rowspan.

• New quick_pptx function to print data frames and huxtables into Powerpoint.

• New install_latex_dependencies and check_latex_dependencies utility functions.

• add_rows and add_columns now accept data frames as arguments.

• New theme_mondrian theme :-D

• Enhancement: print_md now handles bold and italic cells.

• Enhancement: quick_pdf has new width and height options to change paper size.

• Use CSS writing-mode where possible for text rotation. Note that this may break on non-LTR languages. If this affects you, please file an issue.

• Bugfix: LaTeX didn’t compile when height and caption were both set.

• Bugfix: print_screen and print_md would hang with a wide huxtable.

• Tweaks to documentation.

huxtable 4.1.0

• dplyr, knitr, rmarkdown and some other packages have moved to “Suggests:”, lowering the dependency load considerably. All the functionality is still present. huxtable gives an informative warning if a needed package is not installed.

• Code rewrites for better performance and maintainability: HTML is up to 10x faster, LaTeX is up to 4x faster.

• Documentation improvements.

• New tribble_hux function wrapping tibble::tribble() for readable data input.

• New add_rows and add_columns functions to insert one or more rows into the middle of a huxtable.

• New option “huxtable.knitr_output_format” to override the default output format in knitr documents.

• Numeric row heights and column widths are rescaled to 1 when huxtables are cbinded/rbinded.

• LaTeX: at points where borders cross, priority is given to the horizontal border color.

• Bugfix: property accessors had the wrong environment. Thanks to Iñaki Úcar.

• Bugfix: row heights and column widths weren’t being copied with cbind/rbind.

• Bugfixes for 0-row or 0-column huxtables:

  • Output works, usually with a warning.

  • cbind and rbind work.

• Bugfix: HTML cols were printed with ‘width: NA’.

• Bugfix: width, col_width etc. can be reset to a number after setting them to a string.

  • The (undocumented) ability to mix numeric and non-numeric values for padding and/border widths has been removed. If you want a number, set a number and not a string.

• Bugfix: HTML tables with position “right” weren’t right-aligned.

• Nicer error messages when rbinding objects with different numbers of rows.

• Vignette improvements.

• is_a_number is deprecated.

• … and a cool new randomized hux_logo() ;-)

huxtable 4.0.1

• Improved formatting in Excel output.

• New format method which returns the result of to_html, to_latex etc. as appropriate.

• Bugfix: to_html printing e.g. “left-border: NA;” in cell CSS.

• Bugfix: ⁠set_all_*⁠ not working when huxtable is not attached.

• Bugfix: as_Workbook failing with non-numeric width.

• Bugfix: hux_logo was using multiple fonts, fails with Excel output.

• Bugfix: as_flextable borders not working in cells with colspan > 1.

• Documentation bugfixes.

• Compatibility with broom 5.0.0 - thanks @alexpghayes

huxtable 4.0.0

• New theme_plain theme.

• The default value for add_colnames is going to become TRUE. At present it remains FALSE. Set options("huxtable.add_colnames") to TRUE or FALSE to set the default and avoid warnings in future.

• ⁠quick_*⁠ functions now automatically open documents if used interactively. Use open = FALSE to avoid.

• Tweak top and bottom margins for HTML tables.

• pad_decimal is deprecated in favour of align(ht) <- ".".

• huxreg continues with a warning if statistics are unavailable for some models.

Breaking changes

• huxtable now provides knit_print.data.frame methods. This means that bare data frames will be pretty-printed via huxtable if the package is loaded.

  • Set options("huxtable.knit_print_df") to FALSE if you don’t want this.

  • By default data frames are printed using the theme_plain theme. Set options(“huxtable.knit_print_df_theme”) to a different one-argument function if you want to use a different theme.

• The new autoformat argument lets huxtable() and as_huxtable() automatically choose alignment and number format based on column type. Set options("huxtable.autoformat") to FALSE to turn off this feature by default.

• The default value of number_format has changed from “%5.3g” to “%.3g”, which no longer space-pads numbers.

• as_flextable now does not print column names in the header. This matches the standard huxtable behaviour whereby headers are “just another row/column”. To get the old behaviour, use colnames_to_header = TRUE.

Bugfixes

• Bugfix: Date and datetime columns were converted to numbers by add_colnames.

• LaTeX bugfix: background colors were printing an extra space.

• huxreg was never using built-in confidence intervals.

• Screen bugfixes:

  • set max_width to screen width (thanks @jacob-long)

  • misaligned decimal points

• Various bugfixes for number_format, huxreg, as_hux.table, as_flextable.

huxtable 3.0.0

• Output to Excel workbooks using the openxlsx package.

• New quick_xlsx function.

• dplyr select helpers now work inside ⁠set_*⁠ column specifications: e.g. set_bold(ht, 1:3, matches(“ab”), TRUE)

• Column names can now be used for the after argument to insert_column.

• ⁠quick_*⁠ functions: when the file argument is not explicitly specified, confirm overwrites manually, or fail if called non-interactively.

• Add pointless quote marks in Description and Title… I don’t make the rules.

• Don’t apply number_format to negative exponents (e.g. 1.12e-3).

• New tidy_args argument to huxreg allows per-model customization of the call to tidy.

Breaking changes

• quick_xxx functions without an explicit file argument throw an error if called non-interactively, and prompt before overwriting files if called interactively.

huxtable 2.0.2

• Don’t apply number_format to exponents in scientific notation.

• Turn off some tests on CRAN, as they fail there but not elsewhere.

huxtable 2.0.1

• Fix quick_pdf error when moving output across filesystems.

huxtable 2.0.0

• New quick_html, quick_pdf and quick_docx functions to print table-like objects to a new document.

• to_screen only shows colnames if there are any non-zero-length column names.

Breaking changes

• number_format now applies to any number-like substrings in cells. This means you can include e.g. significance stars in a cell and still use number_format to format the content.

• If number_format is NA, numbers are unchanged.

• Default value of number_format has changed from “%5.2f” to “%5.3g”, which plays nicer with integers but may surprise you by using scientific format for large numbers.

huxtable 1.2.0

• New outer_borders argument for huxreg. This changes default behaviour slightly.

• New border argument for add_footnote to choose width of footnote’s top border.

• Added guard assertions to many exported functions.

• Bugfix: captions and colnames are wrapped in to_screen to respect max_width.

huxtable 1.1.0

• No more ugly autocreated column names.

• Allow huxtable to have invalid or empty column names in general.

• LaTeX should now be much faster on large tables.

• set_outer_borders now accepts the same row/column arguments as other set_ functions.

• Better handling in LaTeX of horizontal borders which don’t cross the entire table. (But not varying positive border widths….)

• Bugfix: flextable didn’t like huxreg’s syntactically invalid column names.

• Accept, but silently change, English spelling of ‘centre’ in align, position and caption_pos.

huxtable 1.0.0

• LaTeX implements different thicknesses for vertical and horizontal borders (but only one horizontal thickness per row).

• LaTeX border colors now collapse nicely: set colors override unset ones.

• React gracefully to lack of p values in huxreg.

• New set_outer_borders function to set borders round a rectangle of cells.

• to_screen and to_md now respect wrap and col_widths properties.

• Screen and markdown wrap respect word boundaries.

• to_screen and to_md gain a min_width argument; to_md gains a logical header argument; to_screen gains a compact argument replacing blank = NULL.

• On screen colour and bold support, if the crayon package is installed. New huxtable.color_screen option.

• Move from ReporteRs to officer and flextable. No more RJava horror.

• New error_format argument to huxreg for flexible control over uncertainty estimates.

• Infrastructure improvements: slightly less ugly code in screen.R and LaTeX.R.

Breaking changes

• Removed options collapse, borders, blank and colname_color from to_screen/print_screen.

• as_FlexTable is deprecated and calls as_flextable with a warning. header_rows and footer_rows arguments are ignored. If you need this feature, tell me.

• HTML border sizes are now set in points, not pixels.

• In huxreg:

  • ci_level is NULL by default. Set it to a number to calculate confidence intervals.

  • error_style is deprecated with a warning in favour of error_format.

  • Use {stars} not ⁠%stars%⁠ to display significance levels in the note argument.

  • borders becomes a number specifying border width. Set to 0 for no borders.

huxtable 0.3.1

• New convenience functions insert_row and insert_column.

• latex_float property allows you to change positioning in LaTeX.

• (Semantic versioning fail: this should have been 0.4.0.)

huxtable 0.3.0

• New borders argument for huxreg, gives borders in sensible places.

• Allow more flexible caption positioning with caption_pos.

• New set_default_properties function to set default properties for new huxtables.

• Fix compatibility with dplyr 0.6.0.

huxtable 0.2.2

• Fix a bug that could lead to wrong significance stars in huxreg.

huxtable 0.2.1

• Compatibility with dplyr 0.6.0.

• Use ~ for decimal padding in LaTeX.

huxtable 0.2.0

• New huxreg function to convert a list of models to a huxtable.

• New set_* interface allowing column ranges, expressions a la subset, and filling in values by row.

• Replacement methods ⁠$<-⁠, ⁠[<-⁠ and ⁠[[<-⁠ now work better.

• New function set_cell_properties to set multiple properties on cells.

• evens, odds, everywhere, every(n, from), final(n), where(cond): convenience functions to select rows, columns and cells.

• Export to Word/Powerpoint via ReporteRs.

• Huxtable now supports dplyr verbs like filter and select.

• Exported function guess_knitr_output_format.

• Ability to set border colors.

• Prevent overlapping row/colspans.

• Expanded introduction and new vignette for huxreg.

• Numerous bugs have been fixed and replaced with new, more advanced bugs.

Breaking changes

• theme_minimal has been renamed theme_basic to avoid a name clash with ggplot2.

huxtable 0.1.0

• Added a NEWS.md file to track changes to the package.

• First CRAN release.

Author(s)

Maintainer: David Hugh-Jones [email protected]

See Also

Useful links:

• https://hughjonesd.github.io/huxtable/

• Report bugs at https://github.com/hughjonesd/huxtable/issues

Description

Huxtable has several options.

Details

• options("huxtable.add_colnames") sets the default value for add_colnames in huxtable() and as_huxtable(). As of version 5.0.0, this defaults to TRUE.

• options("huxtable.print") sets the print method for huxtable objects. See print.huxtable().

• options("huxtable.knitr_output_format") overrides the default output format when huxtable objects are printed by knitr. Set to "html", "latex", "md" or "screen". If NULL (the default), huxtable guesses the format using guess_knitr_output_format().

• options("huxtable.autolabel"). If TRUE, (the default) automatically sets label() from the knitr chunk label, if there is one.

• options("huxtable.color_screen"). If TRUE and package crayon is available, huxtables will be printed in color on screen.

• options("huxtable.bookdown"). Set to TRUE within a bookdown document to automatically print bookdown-style labels. If unset, huxtable will try to guess if we are in a bookdown document.

• options("huxtable.knit_print_df"). If TRUE, data frames in knitr will be pretty-printed using huxtable. This option defaults to TRUE only if huxtable is attached to the search path using library(); not if huxtable is merely loaded (e.g. imported by another package).

• options("huxtable.knit_print_df_theme"). A function applied to data frames before printing in knitr. The function should take one argument (a data frame) and return a huxtable. Defaults to theme_plain().

• options("huxtable.autoformat") sets the default value for autoformat in huxtable() and as_huxtable(). It defaults to TRUE.

• options("huxtable.latex_use_fontspec"). If TRUE, use the "fontspec" package, which allows you to use the same font names in TeX and HTML. This requires the the xetex or xelatex engine, which can be set using an .rmd header option. Note that quick_pdf() may use pdflatex. The default is FALSE.

• options("huxtable.long_minus"). If TRUE, prints long minus signs for numbers. The default is FALSE. In LaTeX output, this option is overridden by options("huxtable.latex_siunitx_align").

• options("huxtable.latex_siunitx_align"). If TRUE, uses the ⁠\tablenum⁠ macro from the "siunitx" package to align numbers when align(ht) is "." or similar. See align() for details. The default is FALSE.

  options("huxtable.quarto_process"). If TRUE, enables quarto processing of HTML tables. This overrides some huxtable styles, but may allow quarto to do other things, e.g. process citations correctly. The default is FALSE.

• options("huxtable.autoformat_number_format") and options("huxtable.autoformat_align") are lists. The list names are base R classes. huxtable() with autoformat = TRUE will set number_format() and align() for data columns according to the corresponding list values. For example, to center-align Date objects you could set "huxtable.autoformat_align" to something like list(..., Date = "center", ...).

Author(s)

Maintainer: David Hugh-Jones [email protected]

See Also

Useful links:

• https://hughjonesd.github.io/huxtable/

• Report bugs at https://github.com/hughjonesd/huxtable/issues

Description

These convenience functions wrap cbind or rbind for huxtables, to insert a single row or column.

Usage

insert_column(
  ht,
  ...,
  after = 0,
  fill = NULL,
  rowspan = 1,
  copy_cell_props = TRUE
)

insert_row(
  ht,
  ...,
  after = 0,
  fill = NULL,
  colspan = 1,
  copy_cell_props = TRUE
)

Arguments

Details

In insert_column only, you can use a column name for after.

Even if colspan or rowspan are greater than 1, you must still provide values for the hidden cells. Use fill = "" for this.

Value

The modified huxtable

See Also

add_rows() and add_columns(), which insert multiple rows/columns at once.

Examples

insert_row(jams,
  c("Gooseberry", 2.15),
  after = 1
)

insert_column(jams,
  c("Sugar", "50%", "60%", "40%"),
  after = "Price"
)

insert_column(jams,
  "Sugar",
  after = "Price",
  fill = "50%"
)

# don't forget to use `fill`:
insert_row(jams,
  "Jams and prices",
  fill = "",
  colspan = 2
)

Description

A huxtable of jams.

Usage

jams

Format

A huxtable with 4 rows and 2 columns ("Type" and "Price").

Description

Print data frames in knitr using huxtable

Usage

knit_print.data.frame(x, options, ...)

Arguments

Details

huxtable defines a knit_print method for data.frames. This converts the data frame to a huxtable, with add_colnames = TRUE, themes it using theme_plain() and prints it. It also tries to set a few intelligent defaults, e.g. wrapping long columns and setting an appropriate width. To turn this behaviour off, set options(huxtable.knit_print_df = FALSE). To change the theme, set options("huxtable.knit_print_df_theme") to a one-argument function which should return the huxtable.

See Also

huxtable-options

Other knit_print: knit_print.huxtable()

Examples

## Not run: 
# in your knitr document
mytheme <- function(ht) {
  ht <- set_all_borders(ht, 0.4)
  ht <- set_all_border_colors(
    ht,
    "darkgreen"
  )
  ht <- set_background_color(
    ht,
    evens, odds, "salmon"
  )
  ht
}

options(
  huxtable.knit_print_df_theme = mytheme
)
# groovy!
data.frame(
  a = 1:5,
  b = 1:5
)

## End(Not run)

Description

Print a huxtable within knitr

Usage

knit_print.huxtable(x, options, ...)

Arguments

Details

knitr calls knitr::knit_print() on objects when they are printed in a knitr (or RMarkdown) document. The method for huxtable objects guesses the appropriate output format (including Typst documents when using the typst package) and prints itself out appropriately. You can override the output format by setting options("huxtable.knitr_output_format").

See Also

huxtable-options

Other knit_print: knit_print.data.frame()

Description

The label is used as the table's label in LaTeX, and as the "id" property of the table element in HTML.

Usage

label(ht)

label(ht) <- value

set_label(ht, value)

Arguments

Details

LaTeX table labels typically start with "tab:".

Within knitr, huxtable labels will default to the same as the knitr chunk label. To turn off this behaviour, set options(huxtable.autolabel = FALSE).

If you use bookdown, and set a label on your table, the table caption() will automatically be prefixed with ⁠(#label)⁠. You can then refer to the table using ⁠@ref(label)⁠. label needs to start with "tab:"; if it doesn't, the "tab:" prefix will be added automatically. To turn off this behaviour, set options(huxtable.bookdown = FALSE).

Value

property() returns the property value(s). set_property() and map_property() return the modified huxtable.

See Also

huxtable-options

Examples

set_label(jams, "tab:mytable")

Description

Possible values include:

• "h": here

• "h!" definitely here

• "t" top of page

• "ht" here or at top of page

• "b" bottom of page

• "p" page of floats

Usage

latex_float(ht)

latex_float(ht) <- value

set_latex_float(ht, value)

Arguments

Details

See LaTeX documentation for more details.

Value

property() returns the property value(s). set_property() and map_property() return the modified huxtable.

Examples

set_latex_float(jams, "b")

Description

These functions set borders between cells.

Usage

left_border(ht)

right_border(ht)

top_border(ht)

bottom_border(ht)

left_border(ht) <- value

right_border(ht) <- value

top_border(ht) <- value

bottom_border(ht) <- value

set_left_border(ht, row, col, value = 0.4)

set_right_border(ht, row, col, value = 0.4)

set_top_border(ht, row, col, value = 0.4)

set_bottom_border(ht, row, col, value = 0.4)

map_left_border(ht, row, col, fn)

map_right_border(ht, row, col, fn)

map_top_border(ht, row, col, fn)

map_bottom_border(ht, row, col, fn)

Arguments

Details

Borders are always "collapsed": right_border(ht)[, 1] is the same as left_border(ht)[, 2], and setting one sets the other.

Setting left_border(ht) <- number sets the border thickness. You can set multiple properties at once by using brdr().

Currently in LaTeX, all non-zero border widths on a given line must be the same.

Limitations

• In HTML, you will need to set a width of at least 3 to get a double border.

• Only "solid" and "double" styles are currently implemented in LaTeX, and all non-zero horizontal border widths on a given line must be the same.

See Also

set-multiple

Other border properties: left_border_color(), left_border_style()

Examples

bottom_border(jams)[1, ] <- 0.4
jams

bottom_border(jams)[1, ] <- brdr(0.4, "solid", "blue")
jams

set_bottom_border(jams, brdr(0.4, "solid", "green"))

Description

These functions set border colors.

Usage

left_border_color(ht)

right_border_color(ht)

top_border_color(ht)

bottom_border_color(ht)

left_border_color(ht) <- value

right_border_color(ht) <- value

top_border_color(ht) <- value

bottom_border_color(ht) <- value

set_left_border_color(ht, row, col, value)

set_right_border_color(ht, row, col, value)

set_top_border_color(ht, row, col, value)

set_bottom_border_color(ht, row, col, value)

map_left_border_color(ht, row, col, fn)

map_right_border_color(ht, row, col, fn)

map_top_border_color(ht, row, col, fn)

map_bottom_border_color(ht, row, col, fn)

Arguments

Details

Borders are always "collapsed": right_border_color(ht)[, 1] is the same as left_border_color(ht)[, 2], and setting one sets the other.

Limitations

• Transparent borders with the alpha channel set are not guaranteed to work.

See Also

set-multiple, brdr()

Other border properties: left_border(), left_border_style()

Examples

jams <- set_all_borders(jams)
bottom_border_color(jams)[1, ] <- "red"
jams

set_bottom_border_color(jams, "blue")

Description

These functions set border styles.

Usage

left_border_style(ht)

right_border_style(ht)

top_border_style(ht)

bottom_border_style(ht)

left_border_style(ht) <- value

right_border_style(ht) <- value

top_border_style(ht) <- value

bottom_border_style(ht) <- value

set_left_border_style(ht, row, col, value)

set_right_border_style(ht, row, col, value)

set_top_border_style(ht, row, col, value)

set_bottom_border_style(ht, row, col, value)

map_left_border_style(ht, row, col, fn)

map_right_border_style(ht, row, col, fn)

map_top_border_style(ht, row, col, fn)

map_bottom_border_style(ht, row, col, fn)

Arguments

Details

Borders are always "collapsed": right_border_style(ht)[, 1] is the same as left_border_style(ht)[, 2], and setting one sets the other.

Limitations

• In HTML, you will need to set a width of at least 3 to get a double border.

• Only "solid" and "double" styles are currently implemented in LaTeX.

See Also

set-multiple, brdr()

Other border properties: left_border(), left_border_color()

Examples

jams <- set_all_borders(jams)
bottom_border_style(jams)[1, ] <- "dotted"
jams

set_bottom_border_style(jams, "double")

Description

This help page explains how to set properties differently for cells, depending on their contents.

For example, in a table of p-values, you could bold cells where p < 0.05:

  map_bold(pval_hux, by_ranges(0.05, c(TRUE, FALSE)))

Or you can use red text for a particular value:

  hxtbl %>% map_text_color(by_values("Warning" = "red"))

There is a map_... function for each huxtable cell property. The syntax is:

  map_property(ht, row, col, fn)

where property is the property name.

row and col specify ranges of rows and columns. See rowspecs for details. To set properties for the whole table, omit row and col:

  map_property(ht, fn)

The fn argument is a mapping function which maps cell contents to property values.

• To set property values in "stripes" by rows or by columns, use by_rows() and by_cols().

• To set property values for cells with specific contents, use by_values().

• To set property values for cells within a numeric range, use by_ranges().

• To set property values for cells by quantiles, use by_quantiles() or by_equal_groups().

• To set property values for cells that match a string or regular expression, use by_regex().

• To map numeric values to a colorspace, use by_colorspace().

• For a more general solution, use by_function() or by_cases().

Caveat

Most functions convert the huxtable to a matrix using as.matrix(). This can have unexpected results if you mix character and numeric data. See the example.

Technical details

fn takes four arguments: the entire original huxtable ht, a numeric vector of rows, a numeric vector of cols, and the current property values for ht[rows, cols], as a matrix. It should return the new property values for ht[rows, cols], as a matrix.

Examples

ht <- hux(Condition = c("OK", "Warning", "Error"))
ht <- map_text_color(ht, by_values(
  OK      = "green",
  Warning = "orange",
  Error   = "red"
))
ht

# Leaving NA values alone:
map_text_color(ht, by_values(
  "OK" = "blue", NA, ignore_na = TRUE
))

# Resetting values:
map_text_color(ht, by_values(
  "OK" = "blue", NA, ignore_na = FALSE
))

ht <- as_hux(matrix(rnorm(15), 5, 3))
map_background_color(ht, by_ranges(
  c(-1, 1),
  c("blue", "yellow", "red")
))
map_background_color(
  ht,
  by_equal_groups(2, c("red", "green"))
)

ht <- hux(
  Coef = c(3.5, 2.4, 1.3),
  Pval = c(0.04, 0.01, 0.07),
  add_colnames = TRUE
)
map_bold(
  ht, everywhere, "Pval",
  by_ranges(0.05, c(TRUE, FALSE))
)

# Problems with as.matrix:

ht <- hux(c(-1, 1, 2), letters[1:3])
as.matrix(ht) # look at the spaces...
as.matrix(ht) > 0 # uh oh
map_text_color(
  ht,
  by_cases(. < 0 ~ "red", TRUE ~ "blue")
)

# To avoid this, only look at the truly numeric columns:
map_text_color(ht,
  row = 1:3, col = 1,
  by_cases(. < 0 ~ "red", TRUE ~ "blue")
)

Description

Cells where the markdown property is TRUE will be interpreted as markdown.

Usage

markdown(ht)

markdown(ht) <- value

set_markdown(ht, row, col, value = TRUE)

map_markdown(ht, row, col, fn)

Arguments

Details

Markdown is currently implemented for HTML, Word, Powerpoint, RTF, LaTeX and on-screen display. Word requires the ftExtra package.

Most formats use commonmark, with the "strikethrough" extension enabled.

The following features are intended to work:

• bold and italic text

• strikethrough (write ⁠~~text~~⁠ to strike through text).

• hyperlinks

There are some quirks:

• Paragraph-level properties (e.g. lists) won't work in Word.

• Strikethrough will probably not work in Word.

• To make lists work in LaTeX, set width() and ensure wrap() is TRUE.

• Inline images in RTF work using the INCLUDEPICTURE field type.

• Only local images (not urls) work in typst.

If you try to use markdown tables within a table cell, then seek psychiatric help.

Note

Markdown content in cells is completely separate from printing the whole table as markdown using print_md(). When you set markdown to TRUE, huxtable itself interprets the cell contents as markdown, and spits out HTML, TeX or whatever.

See Also

set_markdown_contents(), a shortcut function.

Examples

jams[3, 2] <- "~2.10~ **Sale!** 1.50"
set_markdown(jams, 3, 2)

Description

merge_across() creates multicolumn cells within each row. merge_down() creates multirow cells within each column.

Usage

merge_across(ht, row, col)

merge_down(ht, row, col)

Arguments

Value

The ht object.

Cell content

In merged cell ranges, only the top left cell's content is displayed. In addition, when you merge cells (either by setting colspan() or rowspan(), or using merge_cells() and friends) the content of the top left cell is copied to other cells. This prevents unexpected changes to content if you reorder or subset rows and columns.

See Also

Other cell merging: merge_cells(), merge_repeated_rows()

Examples

ht <- as_hux(matrix(1:12, 4, 3, byrow = TRUE))
ht <- set_all_borders(ht, 1)
merge_across(ht, 2:4, 2:3)
merge_down(ht, 2:4, 2:3)

Description

merge_cells() merges a rectangle of cells into a single displayed cell, by setting colspan() and rowspan().

Usage

merge_cells(ht, row, col)

Arguments

Details

merge_cells(ht, c(min_row, max_row), c(min_col, max_col)) is equivalent to

  colspan(ht)[min_row, min_col] <- max_col - min_col + 1
  rowspan(ht)[min_row, min_col] <- max_row - min_row + 1

Value

The ht object.

Cell content

In merged cell ranges, only the top left cell's content is displayed. In addition, when you merge cells (either by setting colspan() or rowspan(), or using merge_cells() and friends) the content of the top left cell is copied to other cells. This prevents unexpected changes to content if you reorder or subset rows and columns.

See Also

Other cell merging: merge_across(), merge_repeated_rows()

Examples

ht <- hux(a = 1:3, b = 1:3)
ht <- set_all_borders(ht, 1)
merge_cells(ht, 2:3, 1:2)

Description

merge_repeated_rows() looks within each column for contiguous groups of identical cells. These are merged by setting rowspan(). Doing this helps remove redundant information from the table.

Usage

merge_repeated_rows(ht, row, col)

Arguments

Details

If row contains gaps, results may be unexpected (and a warning is given).

Value

The ht object.

Cell content

In merged cell ranges, only the top left cell's content is displayed. In addition, when you merge cells (either by setting colspan() or rowspan(), or using merge_cells() and friends) the content of the top left cell is copied to other cells. This prevents unexpected changes to content if you reorder or subset rows and columns.

See Also

Other cell merging: merge_across(), merge_cells()

Examples

ht <- as_hux(jams[c(1, 2, 2, 3, 3, 4), ])
ht <- add_columns(ht, c("Sugar", "30%", "40%", "30%", "40%", "30%"),
  after = 1
)
ht
merge_repeated_rows(ht)
merge_repeated_rows(ht, everywhere, "Type")

Description

Huxtable can be used with dplyr verbs dplyr::select(), dplyr::rename(), dplyr::relocate(), dplyr::slice(), dplyr::arrange(), dplyr::mutate() and dplyr::transmute(). These will return huxtables. Other verbs like dplyr::summarise() will simply return data frames as normal; dplyr::pull() will return a vector. mutate has an extra option, detailed below.

Usage

mutate.huxtable(.data, ..., copy_cell_props = TRUE)

Arguments

Details

If mutate creates new columns, and the argument copy_cell_props is missing or TRUE, then cell and column properties will be copied from existing columns to their left, if there are any. Otherwise, they will be the standard defaults. Row and table properties, and properties of cells in existing columns, remain unchanged.

Examples

ht <- hux(a = 1:5, b = 1:5, c = 1:5, d = 1:5, add_colnames = FALSE)
bold(ht)[c(1, 3), ] <- TRUE
bold(ht)[, 1] <- TRUE
ht2 <- dplyr::select(ht, b:c)
ht2
bold(ht2)
ht3 <- dplyr::mutate(ht, x = a + b)
ht3
bold(ht3)
ht4 <- dplyr::mutate(ht,
  x = a + b,
  copy_cell_props = FALSE
)
bold(ht4)

Description

NA values in the huxtable are printed as the value of na_string.

Usage

na_string(ht)

na_string(ht) <- value

set_na_string(ht, row, col, value)

map_na_string(ht, row, col, fn)

Arguments

See Also

Other formatting functions: background_color(), bold(), font(), font_size(), number_format(), text_color()

Examples

jams[3, 2] <- NA
jams
set_na_string(jams, "---")

Description

If number_format is:

• numeric, numbers will be rounded to that many decimal places;

• character, it will be used as an argument to sprintf();

• a function, the function will be applied to the numbers;

• NA, then numbers will not be formatted (except by conversion with as.character).

Usage

number_format(ht)

number_format(ht) <- value

set_number_format(ht, row, col, value)

map_number_format(ht, row, col, fn)

Arguments

Details

Number formatting is applied to any parts of cells that look like numbers. The exception is exponents in scientific notation; huxtable attempts to detect and ignore these.

The default value is "%.3g", which rounds numbers if they have more than 3 significant digits, and which may use scientific notation for large numbers.

Note that if your cells are of type numeric, a number format of NA doesn't guarantee you get back what you typed in, since R's default conversion may apply scientific notation and rounding.

To set number_format to a function, enclose the function in list. The function should take one argument and return a string. fmt_pretty() and fmt_percent() are useful shortcuts for common formatting functions.

See Also

fmt_pretty() and fmt_percent().options("huxtable.long_minus") in huxtable-options for pretty-printing minus signs.

Other formatting functions: background_color(), bold(), font(), font_size(), na_string(), text_color()

Examples

ht <- huxtable(
  number_format = c(
    "Default",
    "NA",
    "2",
    "\"%5.2f\"",
    "Pretty",
    "Sign"
  ),
  a = rep(1000, 6),
  b = rep(1000.005, 6),
  c = rep(0.0001, 6),
  d = rep(-1, 6),
  e = rep("3.2 (s.e. 1.4)", 6)
)

number_format(ht)[3, -1] <- NA
number_format(ht)[4, -1] <- 2
number_format(ht)[5, -1] <- "%5.2f"

number_format(ht)[6, -1] <- fmt_pretty()

number_format(ht)[7, -1] <- list(
  function(x) ifelse((x > 0), "+", "-")
)

right_border(ht) <- 1
bottom_border(ht)[1, ] <- 1

ht

ht_bands <- huxtable("10000 Maniacs", autoformat = FALSE)
# probably not what you want:
ht_bands
# fixed:
set_number_format(ht_bands, NA)

Description

Functions to get or set the space around cell borders. Top, bottom, left and right padding all default to 6 points.

Usage

left_padding(ht)

left_padding(ht) <- value

set_left_padding(ht, row, col, value)

map_left_padding(ht, row, col, fn)

right_padding(ht)

right_padding(ht) <- value

set_right_padding(ht, row, col, value)

map_right_padding(ht, row, col, fn)

top_padding(ht)

top_padding(ht) <- value

set_top_padding(ht, row, col, value)

map_top_padding(ht, row, col, fn)

bottom_padding(ht)

bottom_padding(ht) <- value

set_bottom_padding(ht, row, col, value)

map_bottom_padding(ht, row, col, fn)