home.social

#mksh — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #mksh, aggregated by home.social.

  1. P.S., the body of the parent #toot was created by a simple #shell #function:

    function apod {
        #Today's NASA Astronomy Picture of the Day info-fetcher
        curl -sL 'https://apod.nasa.gov/apod/archivepix.html' \
            |grep -m1 "[0-9][0-9]:" \
            |sed 's/^/Date: /;
                s|: *<a href="|\nURL: https://apod.nasa.gov/apod/|;
                s/">/\nTitle: /; s/<.*$//'
        echo
        echo "#NASA #Astronomy #PictureOfTheDay"
    }
    

    #bash #ksh #mksh #shellScripting #unix #UnixShell #WebScraping #Scraping #HTML

  2. P.S., the body of the parent #toot was created by a simple #shell #function:

    function apod {
        #Today's NASA Astronomy Picture of the Day info-fetcher
        curl -sL 'https://apod.nasa.gov/apod/archivepix.html' \
            |grep -m1 "[0-9][0-9]:" \
            |sed 's/^/Date: /;
                s|: *<a href="|\nURL: https://apod.nasa.gov/apod/|;
                s/">/\nTitle: /; s/<.*$//'
        echo
        echo "#NASA #Astronomy #PictureOfTheDay"
    }
    

    #bash #ksh #mksh #shellScripting #unix #UnixShell #WebScraping #Scraping #HTML

  3. P.S., the body of the parent #toot was created by a simple #shell #function:

    function apod {
        #Today's NASA Astronomy Picture of the Day info-fetcher
        curl -sL 'https://apod.nasa.gov/apod/archivepix.html' \
            |grep -m1 "[0-9][0-9]:" \
            |sed 's/^/Date: /;
                s|: *<a href="|\nURL: https://apod.nasa.gov/apod/|;
                s/">/\nTitle: /; s/<.*$//'
        echo
        echo "#NASA #Astronomy #PictureOfTheDay"
    }
    

    #bash #ksh #mksh #shellScripting #unix #UnixShell #WebScraping #Scraping #HTML

  4. P.S., the body of the parent #toot was created by a simple #shell #function:

    function apod {
        #Today's NASA Astronomy Picture of the Day info-fetcher
        curl -sL 'https://apod.nasa.gov/apod/archivepix.html' \
            |grep -m1 "[0-9][0-9]:" \
            |sed 's/^/Date: /;
                s|: *<a href="|\nURL: https://apod.nasa.gov/apod/|;
                s/">/\nTitle: /; s/<.*$//'
        echo
        echo "#NASA #Astronomy #PictureOfTheDay"
    }
    

    #bash #ksh #mksh #shellScripting #unix #UnixShell #WebScraping #Scraping #HTML

  5. P.S., the body of the parent #toot was created by a simple #shell #function:

    function apod {
        #Today's NASA Astronomy Picture of the Day info-fetcher
        curl -sL 'https://apod.nasa.gov/apod/archivepix.html' \
            |grep -m1 "[0-9][0-9]:" \
            |sed 's/^/Date: /;
                s|: *<a href="|\nURL: https://apod.nasa.gov/apod/|;
                s/">/\nTitle: /; s/<.*$//'
        echo
        echo "#NASA #Astronomy #PictureOfTheDay"
    }
    

    #bash #ksh #mksh #shellScripting #unix #UnixShell #WebScraping #Scraping #HTML

  6. #Poll: Curious about people's attitudes towards shell scripting.

    Two part question:

    1. Are you a DEVeloper (or working in a development-heavy role), OTHER-IT worker (such as a sysadmin, architect, anything in a non-development-heavy role), or NON-IT (accountant, doctor, whatever)
    2. Do you HATE shell scripting, are you INDIFferent towards (or ignorant of) shell scripting, or do you LOVE it?

    #Unix #UnixShell #ShellScript #ShellScripting #POSIX #PosixShell #sh #bash #zsh #csh #tcsh #ksh #pdksh #oksh #mksh

  7. #Poll: Curious about people's attitudes towards shell scripting.

    Two part question:

    1. Are you a DEVeloper (or working in a development-heavy role), OTHER-IT worker (such as a sysadmin, architect, anything in a non-development-heavy role), or NON-IT (accountant, doctor, whatever)
    2. Do you HATE shell scripting, are you INDIFferent towards (or ignorant of) shell scripting, or do you LOVE it?

    #Unix #UnixShell #ShellScript #ShellScripting #POSIX #PosixShell #sh #bash #zsh #csh #tcsh #ksh #pdksh #oksh #mksh

  8. #Poll: Curious about people's attitudes towards shell scripting.

    Two part question:

    1. Are you a DEVeloper (or working in a development-heavy role), OTHER-IT worker (such as a sysadmin, architect, anything in a non-development-heavy role), or NON-IT (accountant, doctor, whatever)
    2. Do you HATE shell scripting, are you INDIFferent towards (or ignorant of) shell scripting, or do you LOVE it?

    #Unix #UnixShell #ShellScript #ShellScripting #POSIX #PosixShell #sh #bash #zsh #csh #tcsh #ksh #pdksh #oksh #mksh

  9. #Poll: Curious about people's attitudes towards shell scripting.

    Two part question:

    1. Are you a DEVeloper (or working in a development-heavy role), OTHER-IT worker (such as a sysadmin, architect, anything in a non-development-heavy role), or NON-IT (accountant, doctor, whatever)
    2. Do you HATE shell scripting, are you INDIFferent towards (or ignorant of) shell scripting, or do you LOVE it?

    #Unix #UnixShell #ShellScript #ShellScripting #POSIX #PosixShell #sh #bash #zsh #csh #tcsh #ksh #pdksh #oksh #mksh

  10. #Poll: Curious about people's attitudes towards shell scripting.

    Two part question:

    1. Are you a DEVeloper (or working in a development-heavy role), OTHER-IT worker (such as a sysadmin, architect, anything in a non-development-heavy role), or NON-IT (accountant, doctor, whatever)
    2. Do you HATE shell scripting, are you INDIFferent towards (or ignorant of) shell scripting, or do you LOVE it?

    #Unix #UnixShell #ShellScript #ShellScripting #POSIX #PosixShell #sh #bash #zsh #csh #tcsh #ksh #pdksh #oksh #mksh

  11. I've probably tooted about this before, but I don't know why this isn't standard.

    It's just so obvious, at least to me. ;)

    ~ $ type mcd
    mcd is a function
    mcd () 
    { 
        [[ -n $1 ]] && mkdir "$1" && cd "$1"
    }
    

    #shell #UnixShell #ShellScripting #sh #bash #ksh #mksh

  12. I've probably tooted about this before, but I don't know why this isn't standard.

    It's just so obvious, at least to me. ;)

    ~ $ type mcd
    mcd is a function
    mcd () 
    { 
        [[ -n $1 ]] && mkdir "$1" && cd "$1"
    }
    

    #shell #UnixShell #ShellScripting #sh #bash #ksh #mksh

  13. I've probably tooted about this before, but I don't know why this isn't standard.

    It's just so obvious, at least to me. ;)

    ~ $ type mcd
    mcd is a function
    mcd () 
    { 
        [[ -n $1 ]] && mkdir "$1" && cd "$1"
    }
    

    #shell #UnixShell #ShellScripting #sh #bash #ksh #mksh

  14. I've probably tooted about this before, but I don't know why this isn't standard.

    It's just so obvious, at least to me. ;)

    ~ $ type mcd
    mcd is a function
    mcd () 
    { 
        [[ -n $1 ]] && mkdir "$1" && cd "$1"
    }
    

    #shell #UnixShell #ShellScripting #sh #bash #ksh #mksh

  15. I've probably tooted about this before, but I don't know why this isn't standard.

    It's just so obvious, at least to me. ;)

    ~ $ type mcd
    mcd is a function
    mcd () 
    { 
        [[ -n $1 ]] && mkdir "$1" && cd "$1"
    }
    

    #shell #UnixShell #ShellScripting #sh #bash #ksh #mksh

  16. Process Substitution is hella neat.

    $ diff important-data.txt <(clipo |sort -u)
    

    (Of course #mksh has it as well ;)

  17. Process Substitution is hella neat.

    $ diff important-data.txt <(clipo |sort -u)
    

    (Of course #mksh has it as well ;)

  18. Process Substitution is hella neat.

    $ diff important-data.txt <(clipo |sort -u)
    

    (Of course #mksh has it as well ;)

  19. Process Substitution is hella neat.

    $ diff important-data.txt <(clipo |sort -u)
    

    (Of course #mksh has it as well ;)

  20. Process Substitution is hella neat.

    $ diff important-data.txt <(clipo |sort -u)
    

    (Of course #mksh has it as well ;)

  21. While we could add a bunch of CHECK_PORTABILITY_SKIP entries to skip these files, I prefer to fix things properly, and so have committed a general fix for this which should speed up most packages.

    github.com/TritonDataCenter/pk

    Nice reduction in runtime from 86 seconds down to just 1!

    If anyone has access to really old systems and are able to tell me if they do not have "read -n" then that'd be hugely appreciated, though it's likely we'd bootstrap #mksh on them anyway.

    #pkgsrc #dtrace

  22. While we could add a bunch of CHECK_PORTABILITY_SKIP entries to skip these files, I prefer to fix things properly, and so have committed a general fix for this which should speed up most packages.

    github.com/TritonDataCenter/pk

    Nice reduction in runtime from 86 seconds down to just 1!

    If anyone has access to really old systems and are able to tell me if they do not have "read -n" then that'd be hugely appreciated, though it's likely we'd bootstrap #mksh on them anyway.

    #pkgsrc #dtrace

  23. While we could add a bunch of CHECK_PORTABILITY_SKIP entries to skip these files, I prefer to fix things properly, and so have committed a general fix for this which should speed up most packages.

    github.com/TritonDataCenter/pk

    Nice reduction in runtime from 86 seconds down to just 1!

    If anyone has access to really old systems and are able to tell me if they do not have "read -n" then that'd be hugely appreciated, though it's likely we'd bootstrap #mksh on them anyway.

    #pkgsrc #dtrace

  24. While we could add a bunch of CHECK_PORTABILITY_SKIP entries to skip these files, I prefer to fix things properly, and so have committed a general fix for this which should speed up most packages.

    github.com/TritonDataCenter/pk

    Nice reduction in runtime from 86 seconds down to just 1!

    If anyone has access to really old systems and are able to tell me if they do not have "read -n" then that'd be hugely appreciated, though it's likely we'd bootstrap #mksh on them anyway.

    #pkgsrc #dtrace

  25. While we could add a bunch of CHECK_PORTABILITY_SKIP entries to skip these files, I prefer to fix things properly, and so have committed a general fix for this which should speed up most packages.

    github.com/TritonDataCenter/pk

    Nice reduction in runtime from 86 seconds down to just 1!

    If anyone has access to really old systems and are able to tell me if they do not have "read -n" then that'd be hugely appreciated, though it's likely we'd bootstrap #mksh on them anyway.

    #pkgsrc #dtrace

  26. Interesting performance and behaviour difference between shells and the "read" builtin.

    After upgrading to macOS Sonoma I noticed the #pkgsrc check-portability script occasionally taking over an hour and falling foul of my "ulimit -t 3600".

    $ wc text-public.js.map
    0 960590 13488786 text-public.js.map

    Time to "read f < text-public.js.map" and wc $f:

    #bash: 0.5 seconds
    1 960590 13060347

    #mksh: 6.2 seconds
    15904 973513 13030108

    #dash: 6.4 seconds
    15903 973410 13033181

  27. Interesting performance and behaviour difference between shells and the "read" builtin.

    After upgrading to macOS Sonoma I noticed the #pkgsrc check-portability script occasionally taking over an hour and falling foul of my "ulimit -t 3600".

    $ wc text-public.js.map
    0 960590 13488786 text-public.js.map

    Time to "read f < text-public.js.map" and wc $f:

    #bash: 0.5 seconds
    1 960590 13060347

    #mksh: 6.2 seconds
    15904 973513 13030108

    #dash: 6.4 seconds
    15903 973410 13033181

  28. Interesting performance and behaviour difference between shells and the "read" builtin.

    After upgrading to macOS Sonoma I noticed the #pkgsrc check-portability script occasionally taking over an hour and falling foul of my "ulimit -t 3600".

    $ wc text-public.js.map
    0 960590 13488786 text-public.js.map

    Time to "read f < text-public.js.map" and wc $f:

    #bash: 0.5 seconds
    1 960590 13060347

    #mksh: 6.2 seconds
    15904 973513 13030108

    #dash: 6.4 seconds
    15903 973410 13033181

  29. Interesting performance and behaviour difference between shells and the "read" builtin.

    After upgrading to macOS Sonoma I noticed the #pkgsrc check-portability script occasionally taking over an hour and falling foul of my "ulimit -t 3600".

    $ wc text-public.js.map
    0 960590 13488786 text-public.js.map

    Time to "read f < text-public.js.map" and wc $f:

    #bash: 0.5 seconds
    1 960590 13060347

    #mksh: 6.2 seconds
    15904 973513 13030108

    #dash: 6.4 seconds
    15903 973410 13033181

  30. Interesting performance and behaviour difference between shells and the "read" builtin.

    After upgrading to macOS Sonoma I noticed the #pkgsrc check-portability script occasionally taking over an hour and falling foul of my "ulimit -t 3600".

    $ wc text-public.js.map
    0 960590 13488786 text-public.js.map

    Time to "read f < text-public.js.map" and wc $f:

    #bash: 0.5 seconds
    1 960590 13060347

    #mksh: 6.2 seconds
    15904 973513 13030108

    #dash: 6.4 seconds
    15903 973410 13033181