Ian Lyttle ijlyttle

The invitation is sent to [email protected], and the I sign in using my ijlyttle account, which uses [email protected].

The invitation is to a space, ours is called "From R User to R Programmer". Within that space, we can create a project; we will create "r-programming-exercises". We will create a code project.

It looks like I will:

create a project from a git repository
install our pre-req packages: install.packages(c("devtools", "tidyverse", "palmerpenguins", "here"))
make changes only by pulling in from the repo:

Using deno, git, virtualenv plugins

lyttle.zsh-theme:

PROMPT='%{$fg_bold[cyan]%}$(virtualenv_prompt_info)%}$(git_prompt_info) %c %{$fg_bold[white]%}%% %{$reset_color%}'

ZSH_THEME_GIT_PROMPT_PREFIX="("
ZSH_THEME_GIT_PROMPT_SUFFIX=")"
ZSH_THEME_GIT_PROMPT_DIRTY=""

This is macOS-centric.

Installation

brew install deno

Configuration

MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

These ideas based on GitHub Flow and are heavily influenced by Jenny Bryan and Hadley Wickham, through their R package {usethis}.

Remotes

The term upstream refers to a remote that is the "canonical" repository for a project.

The term origin refers to a remote that is a fork of an upstream remote.

If you are one of the maintainers for a repository, you can push to the upstream remote.

SSH for travis-pkgdown

In the .ssh directory, we should have:

id_rsa & id_rsa.pub - the default keys for this computer

In addition, you need a distinct set of keys for each repository. Accordingly, each of these would be a directory within .ssh:

gh-deploy-vegawidget
gh-deploy-altair

	# Example of vegawidget with dynamic data and signal
	#
	# To use shiny_get_signal along with dynamic data (on R side), you have to use
	# shiny_set_data as well. This is because the binding of shiny_get_signal breaks
	# if you use normal reactive data (see other file in this folder).
	#
	# shiny_set_data work saround that problem and uses an elegant reactive solution
	#
	# based on: https://github.com/rhenkin/rsnippets/blob/main/vegawidget_shinygetsignal/app_working.R
	#

	---
	title: "Altair-reticulate"
	output: html_document
	---

	```{r load_packages}
	library(vegawidget)
	library(reticulate)
	```

	# imports lubridate, emo, glue, purrr

	as_woodiac <- function(x) {

	is_dst <- lubridate::dst(as.POSIXct(x)) # pick up OS timzone

	x <- lubridate::as_date(x)
	date_2000 <- x
	lubridate::year(date_2000) <- 2000