start new:
tmux
start new with session name:
tmux new -s myname
| #!/bin/bash | |
| LOL=/tmp/LOLZ | |
| RUNNING=true | |
| while $RUNNING; do | |
| case $([ -f $LOL ] && cat $LOL) in | |
| INIT) | |
| echo "Reached INIT State. Moving to WORK state." | |
| echo "WORK" > $LOL |
| To use: create a new bookmark and paste into the URL field. | |
| In Chrome, you can paste the full multiline code as shown below. | |
| In other browsers, you may need to minify the code into one line first. |
Gravizo is a really cool tool to display graphs in your README.
Lately, none of their examples seem to be working for me. I don't like using the
indirect method,
because it means that if the indirect breaks or is no longer public or whatever, who
Short (72 chars or less) summary
More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).
Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages
| use std::str; | |
| fn main() { | |
| // -- FROM: vec of chars -- | |
| let src1: Vec<char> = vec!['j','{','"','i','m','m','y','"','}']; | |
| // to String | |
| let string1: String = src1.iter().collect::<String>(); | |
| // to str | |
| let str1: &str = &src1.iter().collect::<String>(); | |
| // to vec of byte |