Go to the course and have any video up. The following code relies on the right sidebar to be visible to uncheck all your progress.
You can do this with ctrl+shift+j
and making sure the console
tab is selected for chrome/brave
const toUnixTime = (date) => date.getTime() / 1000; | |
const usageInterval = (start, end) => ({ | |
start: toUnixTime(start), | |
end: toUnixTime(end) | |
}); | |
const getSyndayOfTheWeek = (currentDate) => { | |
const date = new Date(currentDate.getFullYear(), currentDate.getMonth(), currentDate.getDate()); |
Go to the course and have any video up. The following code relies on the right sidebar to be visible to uncheck all your progress.
You can do this with ctrl+shift+j
and making sure the console
tab is selected for chrome/brave
class MultipleInstancesOfState | |
attr_accessor :state | |
def initialize(state:) | |
@state = state | |
end | |
def foo | |
@state.reverse! | |
end |
This is a guide to Vim Script development for Python developers. Sample code for the various expressions, statements, functions and programming constructs is shown in both Python and Vim Script. This is not intended to be a tutorial for developing Vim scripts. It is assumed that the reader is familiar with Python programming.
For an introduction to Vim Script development, refer to usr_41.txt, eval.txt and Learn Vimscript the Hard Way
For a guide similar to this one for JavaScript developers, refer to Vim Script for the JavaScripter
This guide only describes the programming constructs that are present in both Python and Vim. The constructs that are unique to Vim (e.g. autocommands, [key-mapping](https://vimhelp.org/map.txt.html#key-m
I think most of us realize that macOS isn't a Linux OS, but what that also means is that instead of shipping with the GNU flavor of command line tools, it ships with the FreeBSD flavor. As such, writing shell scripts which can work across both platforms can sometimes be challenging.
Homebrew can be used to install the GNU versions of tools onto your Mac, but they are all prefixed with "g" by default.
All commands have been installed with the prefix "g". If you need to use these commands with their normal names, you can add a "gnubin" directory to your PATH from your bashrc.
def to_bool(string)
if string == true || string == 1 || string =~ (/(true|1)$/i)
true
else
false
end
end
import PropTypes from 'prop-types'; | |
type Omit<T, K> = Pick<T, Exclude<keyof T, K>>; | |
type Defined<T> = T extends undefined ? never : T; | |
/** | |
* Get the type that represents the props with the defaultProps included. | |
* | |
* Alternatively, we could have done something like this: |
dconf write /org/gnome/terminal/legacy/profiles:/:<id>/allow-bold false |
# gruvbox-dark colorscheme for kitty | |
# snazzy theme used as base | |
foreground #ebdbb2 | |
background #272727 | |
selection_foreground #655b53 | |
selection_background #ebdbb2 | |
url_color #d65c0d | |
# black |
There are 28 static site generators that support AsciiDoc sourcing.