home.social

Search

449 results for “cmdln”

  1. Ich musste heute eine Mailingliste um Dubletten bereinigen. Habe reflexartig Excel gestartet und die Mailadressen reinkopiert. Und bin kurz drauf gescheitert. Unixpower to the rescue: „uniq mails.txt mails_uniq.txt“. Wenige Sekunden später habe ich eine bereinigte Mailingliste gehabt. #macos #cmdline #shell #unixpower #thepowerofthecommandshell

  2. Ich musste heute eine Mailingliste um Dubletten bereinigen. Habe reflexartig Excel gestartet und die Mailadressen reinkopiert. Und bin kurz drauf gescheitert. Unixpower to the rescue: „uniq mails.txt mails_uniq.txt“. Wenige Sekunden später habe ich eine bereinigte Mailingliste gehabt. #macos #cmdline #shell #unixpower #thepowerofthecommandshell

  3. Ich musste heute eine Mailingliste um Dubletten bereinigen. Habe reflexartig Excel gestartet und die Mailadressen reinkopiert. Und bin kurz drauf gescheitert. Unixpower to the rescue: „uniq mails.txt mails_uniq.txt“. Wenige Sekunden später habe ich eine bereinigte Mailingliste gehabt. #macos #cmdline #shell #unixpower #thepowerofthecommandshell

  4. Table of Basic PowerShell Commands

    I rarely use PowerShell and it pisses me off when I can't recall the commands right away and look like a foo'! So, I printed out this little thing here to keep with me in case I need to use it. Hope it helps someone else!

    #PowerShell #cmdlets #WindowsPowerShell #BasicPowerShellCommands

    devblogs.microsoft.com/scripti

  5. When I load the Waveshare dtoverlays and modify the config.txt and cmdline.txt *after* the first boot of a fresh RaspbianOS install, the DPI LCD is not used.

    If I load the Waveshare dtoverlays onto the SD card and modify the config.txt and cmdline.txt *before* the first boot of a fresh system, everything works as expected.

    Is there some intermediate step happening on first boot?

    #RaspbianOS
    #Ansible

  6. Instead of repeating past mistakes like aliasing curl to the Invoke-WebRequest cmdlet in PowerShell by creating a SUDO command for Windows, Microsoft should embrace their legacy and create Super Administrator Do (SADO)

    #SUDO #SADO #Microsoft #Windows #Curl #Invoke-WebRequest #Tensionheadache

  7. Instead of repeating past mistakes like aliasing curl to the Invoke-WebRequest cmdlet in PowerShell by creating a SUDO command for Windows, Microsoft should embrace their legacy and create Super Administrator Do (SADO)

    #SUDO #SADO #Microsoft #Windows #Curl #Invoke-WebRequest #Tensionheadache

  8. Instead of repeating past mistakes like aliasing curl to the Invoke-WebRequest cmdlet in PowerShell by creating a SUDO command for Windows, Microsoft should embrace their legacy and create Super Administrator Do (SADO)

    #SUDO #SADO #Microsoft #Windows #Curl #Invoke-WebRequest #Tensionheadache

  9. Instead of repeating past mistakes like aliasing curl to the Invoke-WebRequest cmdlet in PowerShell by creating a SUDO command for Windows, Microsoft should embrace their legacy and create Super Administrator Do (SADO)

    #SUDO #SADO #Microsoft #Windows #Curl #Invoke-WebRequest #Tensionheadache

  10. Instead of repeating past mistakes like aliasing curl to the Invoke-WebRequest cmdlet in PowerShell by creating a SUDO command for Windows, Microsoft should embrace their legacy and create Super Administrator Do (SADO)

    #SUDO #SADO #Microsoft #Windows #Curl #Invoke-WebRequest #Tensionheadache

  11. Nothing like being asked to provide cross-platform support for my MSI cmdlets (github.com/heaths/psmsi) to extract the ProductCode - which is dubious since they depend on Windows-only APIs and most features would only work on Windows where MSIs can be installed - and saying you could write a simple CLI using a crate that implements OLE docs and 's proprietary compression algorithm, only to realize you already did it a long time ago: github.com/heaths/msigetprop-rs

  12. Nothing like being asked to provide cross-platform support for my MSI #PowerShell cmdlets (github.com/heaths/psmsi) to extract the ProductCode - which is dubious since they depend on Windows-only APIs and most features would only work on Windows where MSIs can be installed - and saying you could write a simple #rustlang CLI using a crate that implements OLE docs and #WindowsInstaller's proprietary compression algorithm, only to realize you already did it a long time ago: github.com/heaths/msigetprop-r

  13. Nothing like being asked to provide cross-platform support for my MSI #PowerShell cmdlets (github.com/heaths/psmsi) to extract the ProductCode - which is dubious since they depend on Windows-only APIs and most features would only work on Windows where MSIs can be installed - and saying you could write a simple #rustlang CLI using a crate that implements OLE docs and #WindowsInstaller's proprietary compression algorithm, only to realize you already did it a long time ago: github.com/heaths/msigetprop-r

  14. Nothing like being asked to provide cross-platform support for my MSI #PowerShell cmdlets (github.com/heaths/psmsi) to extract the ProductCode - which is dubious since they depend on Windows-only APIs and most features would only work on Windows where MSIs can be installed - and saying you could write a simple #rustlang CLI using a crate that implements OLE docs and #WindowsInstaller's proprietary compression algorithm, only to realize you already did it a long time ago: github.com/heaths/msigetprop-r

  15. Nothing like being asked to provide cross-platform support for my MSI #PowerShell cmdlets (github.com/heaths/psmsi) to extract the ProductCode - which is dubious since they depend on Windows-only APIs and most features would only work on Windows where MSIs can be installed - and saying you could write a simple #rustlang CLI using a crate that implements OLE docs and #WindowsInstaller's proprietary compression algorithm, only to realize you already did it a long time ago: github.com/heaths/msigetprop-r