x-yuri
x-yuri
Consider the following page: ```html import React from 'https://esm.sh/[email protected]?dev'; import ReactDOM from 'https://esm.sh/[email protected]?dev'; import TextField from 'https://esm.sh/@material-ui/[email protected]/[email protected],[email protected]&dev'; import Button from 'https://esm.sh/@material-ui/[email protected]/[email protected],[email protected]&dev'; const e = React.createElement; ReactDOM.render( // e(Button, {variant: 'contained',...
That would be most welcome for running `dcron` in a docker container. Then there'd no need to set up mail, and `docker logs` could be used to inspect what's going...
See for yourself: ``` >>> Running ./test/chruby_exec_test.sh ... test_chruby_exec_no_arguments test_chruby_exec_no_command test_chruby_exec zsh:1: command not found: chruby ASSERT:did change the ruby expected: but was: ``` As it turns out it has...
First, there doesn't always exist [dir](https://rvm.io/binaries/debian/) for some particular distribution release, like `debian-7,8` (which I need now). And there doesn't always exist ruby for that particular release, like `2.0.0-p353` for...
I've managed to build a package for `debian` recently. So, firstly I wanted to report that the aforementioned directory is in the way of building the package (or rather creating...
- [x] I have fzf 0.23.0 or above - [x] I have read through https://github.com/junegunn/fzf.vim/blob/master/README.md - [x] I have read through https://github.com/junegunn/fzf/blob/master/README-VIM.md - [x] I have read through the manual...
In #153 you suggested to create a Docker image. Supposedly to be able to run `bjoern`. Here's the starting point: ```dockerfile FROM python:alpine RUN apk add --no-cache build-base libev-dev git...
By that I mean, that `required` attr behaves as , e.g., [`checked`][1] one: ```html ``` [1]: https://github.com/ded/bonzo/blob/v2.0.0/src/bonzo.js#L860
## Problem description Backtrace and evaluation doesn't always work, supposedly because of null bytes. ## Expected behavior Null bytes are not in `byebug`'s way. ## Actual behavior See below. ##...
It's really hard to learn how the code looked like at some specific version.