mgdlbp

http://www.electronicdissonance.com/2010/01/raster-fonts-in-...

They also smashed pianos in the Rube Goldberg video, and a TV with a sledge. Now I wonder if that was a 1984 reference.

https://www.youtube.com/watch?v=0BTnGgzO-tU https://www.youtube.com/watch?v=qybUFnY7Y8w

The segue from CG is much more sensible

  most typefaces: “Hello” „Hallo“

That camera can actually get a bit more resolution out of sensor movements, though the lens might be at its limit already, or focus was still a little off. edit: it's probably the glovebox glass.

https://www.wikidata.org/wiki/Q3271851

https://web.archive.org/web/20201214110440/https://en.wikipe...

  :%s/\([0-9]\+\))/\=submatch(1)-1.')'    " vim

  perl -pe 's/([0-9]+)\)/$1-1 .")"/e'

  ruby -pe 'sub(/([0-9]+)\)/){"#{$1.to_i-1})"}'

  uxterm -xrm '*VT100.translations: #override !<Btn1Down>: vi-button() readline-button()'

https://web.archive.org/web/20070227/http://qdb.gr

https://web.archive.org/web/20060402/http://qdb.hu

https://web.archive.org/web/20040420/http://qdb.us

https://web.archive.org/web/20100222/http://bash.org.az

https://web.archive.org/web/20070217/http://bash.org.by

https://web.archive.org/web/20060424/http://bash.org.il

https://web.archive.org/web/20071022/http://bash.org.kg

https://web.archive.org/web/20061203/http://bash.org.lv

https://web.archive.org/web/20090830/http://bash.org.md

https://web.archive.org/web/20060101/http://bash.org.pl

https://web.archive.org/web/20090421/http://bash.org.ro

https://web.archive.org/web/20040611/http://bash.org.ru

https://web.archive.org/web/20110523/http://bash.org.tj

https://web.archive.org/web/20080105/http://bash.org.ua

https://web.archive.org/web/20101117/http://ibash.org.pl

https://web.archive.org/web/20070609/http://ibash.org.ru

https://web.archive.org/web/20091004/http://bash.cc

https://web.archive.org/web/20030805/http://bash.cx

https://web.archive.org/web/20080315/http://bash.ee

https://web.archive.org/web/20040608/http://bash.hu

https://web.archive.org/web/20090322/http://bash.im

https://web.archive.org/web/20060205/http://bash.lv

https://web.archive.org/web/20180314/http://bash.no

https://web.archive.org/web/20060112/http://bash.ro

https://web.archive.org/web/20080219/http://bash.tj

https://web.archive.org/web/20120114/http://bash.tk

https://web.archive.org/web/20061115/http://ibash.de

https://web.archive.org/web/20160109/http://ibash.im

I was going to say 'chance of death on that day' but apparently rail transport is remarkably safe and in micromorts, you're as likely to die in one day at 20 years of age as in 10000 km by rail, or (only!) 1600 km by air.

Now, it appears that 1600 km is also nearly the distance of the average passenger flight (a disappointly difficult datum to discover on the internet in 2024). Is this a counterpart to the reassuring quips comparing the chances of death by lightning: that boarding a plane doubles your chances of dying that day?

https://en.wikipedia.org/wiki/Micromort#Travel

As far as I know, unless a browser manages its oom_score_adj, which none do, a wrapper is insufficient as a workaround and a daemon would have to do so on its behalf, because the value is inherited when forking.

[0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

Find a query of interest, see for yourself (and take a snapshot of the present state for posterity).

The api enables more powerful queries, https://web.archive.org/cdx/search/cdx?url=google.co.jp*&pag...

Also try other search engines and languages.

Can have security implications, but the target is chosen in the typical way and screen locks should be setting a score_adj to avoid being picked.

[only on HN] could [any state [that Gentoo was ever in]] be [reflected upon [as "just worked like a breeze"] unironically]_,_ and [I] mean [that] [in a fond, loving way]

  Welcome to the Emacs shell
  
  /tmp $ set-variable `x 6; echo $x
  6
  /tmp $ 

  PowerShell 7.4.0
  PS /tmp> set-variable `x 6; echo $x
  6
  PS /tmp> 

¹ https://commons.wikimedia.org/wiki/File:Concorde_(British_AW...

² https://commons.wikimedia.org/wiki/File:Concorde_2015-06_673...

³ https://commons.wikimedia.org/wiki/File:Concorde_2015-06_692...

[0] https://web.archive.org/web/20210826103144/http://www.crimef...

    $ f=-x
    $ cat "$f"
    cat: invalid option -- 'x'

    $ cat -- "$f"
    cat: -x: No such file or directory
    # ^-- correct

    $ f=-
    $ cat -- "$f"
    reading stdin...
    reading stdin...
    ^C

    $ cat ./-
    cat: ./-: No such file or directory

    for i in {1..10}; <<<$i

    foreach ($i in 1..10) { $i }

    1..10|%{$_}

;-D

The substance of the first answer:

    #!/bin/bash
    
    # Check if the first parameter is not provided
    if [ -z "$1" ]; then
        echo "Error: Parameter not provided."
        exit 1
    fi

> This checks if the first parameter (`$1`) is empty.

But what happened to the supplied task? It was stated and echoed as:

> Anonymous: ...if it's not passed?

> ChatGPT: ...if a specific parameter is not passed...

> ChatGPT: ...if the parameter is set.

The second answer:

    #!/bin/bash
    : ${1?"Error: Parameter not provided"}

> ...and the `${1?...}` part checks if the first positional parameter (`$1`) is unset or null.

--

(the most succinct possible idiom is `#!/bin/bash -u`)

    $ echo 25 | pwsh -c '$input-replace"\d",{2*"$_"}'
    410
    $ echo 25 | perl -pe 's/\d/2*$&/eg'
    410

    PS> $temp:pwsh_out = 10000
    PS> /bin/cat /tmp/pwsh_out
    10000

    $ echo ''''

    PS> echo ''''
    '

    PS> $Y = { param($f) . { param($x) . $x $x } { param($y) . $f { param($x) . (. $y $y) $x }.GetNewClosure() }.GetNewClosure() }
    PS> $fac = & $Y { param($f) { param($n) $n -lt 2 ? 1 : $n * (. $f ($n - 1)) }.GetNewClosure() }
    PS> & $fac 5
    120

    PS> gv -v|% m*d|% t*
    gv -v|% m*d|% t*

    PS> &($x={"&(`$x={$x})"})
    &($x={"&(`$x={$x})"})

    $ bash
    $ eval ${x='echo eval \${${x@A}}'}
    eval ${x='echo eval \${${x@A}}'}

bilingual pun,

    .ps1            .pl
     1               1
     {1}             {1}
     end {1}         sub {1}
     {end {1}}       {sub {1}}
     &{end {1}}      &{sub {1}}

    awk  -e 'BEGIN { printf "3\n" }'
    perl -e 'BEGIN { printf "3\n" }'
    ruby -e 'BEGIN { printf "3\n" }'
    pwsh -c 'BEGIN { printf "3\n" }'

    $ time ...; time ...; ....
    real 0.00 ...
    real 0.00 ...
    real 0.03 ...
    real 0.22 ...

- It obscures actual uses of modifiers, particularly ${foo-} when set -u is in effect,

- It's obvious when a name runs into subsequent text, even if one has somehow avoided syntax highlighting,

- And expansions followed by identifier chars don't actually occur in practice. Cases where the quotes cannot be moved to surround the variable are often interpolation of an argument to echo, whose behaviour is such a mess not even portable between bash and dash that shellcheck ought to be demanding printf at all times instead!