home.social

Search

360 results for “myTerminal”

  1. #asciiNema asciinema.org/ is a tiny little terminal-only screencasting tool that produces tiny recordings.

    It's the same one used on the #NixOS homepage nixos.org

    I'm hoping I can use it with github.com/marionebl/svg-term- to embed my terminal demonstrations into #Sozi presentations:
    * yes, I know this just plays a continuous loop without a pause option, but it is an intriguing embedded solution that doesn't require stepping out of the presentation.

    #bookmark @asciinema

  2. #asciiNema asciinema.org/ is a tiny little terminal-only screencasting tool that produces tiny recordings.

    It's the same one used on the #NixOS homepage nixos.org

    I'm hoping I can use it with github.com/marionebl/svg-term- to embed my terminal demonstrations into #Sozi presentations:
    * yes, I know this just plays a continuous loop without a pause option, but it is an intriguing embedded solution that doesn't require stepping out of the presentation.

    #bookmark @asciinema

  3. #asciiNema asciinema.org/ is a tiny little terminal-only screencasting tool that produces tiny recordings.

    It's the same one used on the #NixOS homepage nixos.org

    I'm hoping I can use it with github.com/marionebl/svg-term- to embed my terminal demonstrations into #Sozi presentations:
    * yes, I know this just plays a continuous loop without a pause option, but it is an intriguing embedded solution that doesn't require stepping out of the presentation.

    #bookmark @asciinema

  4. #asciiNema asciinema.org/ is a tiny little terminal-only screencasting tool that produces tiny recordings.

    It's the same one used on the #NixOS homepage nixos.org

    I'm hoping I can use it with github.com/marionebl/svg-term- to embed my terminal demonstrations into #Sozi presentations:
    * yes, I know this just plays a continuous loop without a pause option, but it is an intriguing embedded solution that doesn't require stepping out of the presentation.

    #bookmark @asciinema

  5. So, #Fedora lasted 24 hours before succumbing to the exact same issue. (Part of the 24 hours was adapting some of my Ansible roles for RedHat based distros).

    I also had an issue where my terminal would stop accepting any keyboard input except ENTER. (Wtf?) This was happening in Kitty but also in the native KDE terminal.

    I then thought sod it, and fired up good old Debian 12 with Gnome ... and what do you know, it's the same issues!

    I figure at this point, I'm cursed and I have some broken config. So, I rename by .zshrc file and reboot ... joy... the keyboard works! My shell no longer freezes!

    Only now, I can't get #goverlay running, and #corectrl won't install.

    As a last ditch effort, I wipe the system one more time and install #Mint 21.3 ... everything works. Everything. Goverlay, corectrl, gamemode, my shell, 1Passwords SSH agent ... all of it.

    #Manjaro #ansible #neovim #Fedora

  6. #kittyterm for the win!
    Moved from iTerm to Kitty a year ago on a whim as I rejigged my terminal and shell situation. Zero regrets. zomglol.wtf/@jamie/11247650573

  7. New #blog post:

    schafe-sind-bessere-rasenmaehe

    This week I managed to plug a hole in my terminal workflow that's been bugging me for a while.

    It's related to #NetFramework, #CodeCoverage and my stubbornness for not wanting to use Visual Studio anymore. 😬

    I count this as part of the #30DayFossChallenge , because all parts of the solution are FOSS.

    I didn't really replace anything proprietary with this, but I plugged another hole that removing Visual Studio (Code) left. 🙂

  8. 24 hours later, I'm back!

    Summary of the previous episodes:

    1. 3 days ago, my old dedicated server started spewing error messages about the CPU.
    2. On a hunch, I ran backup-manager with my existing configuration that's supposed to send the compressed database dump + files to an FTP backup server.
    3. I contacted my hosting provider to figure out the error.
    4. Answer was quick: "we can't physically intervene on the server, and the same offer isn't available anymore, you have to pick a new offer".
    5. I pick an upgrade, no answer for a day.
    6. A day ago, they made the new server available to me, and immediately removed access to the old server from my account, including the attached FTP backup storage.
    7. Asked the support to restore access either to the old server or at least the FTP storage. At this point I've lost all my Internet history from 2009 onwards.
    8. The "Customer Excellence Specialist Level 2" throws his hands in the air, saying that the CPU errors are making either SSH or KVM impossible.
    9. 12 hours ago, they restored my access to the server and the FTP storage. No luck, last backup on that server dates back to 2019. Server's IP is "very pingable" according to support, but no remote connection is possible.
    10. Through the hosting provider console, I rebooted in rescue mode. No luck, still no remote connection. I switch back to regular mode with a new reboot.
    11. I start to receive emails from my third-party monitoring system that my web sites are available again!
    12. I jump on my terminal, the remote connection works! I don't know how much time I have, I stop the web server to save CPU cycles. I found the fresh local backup files. I start to download them locally. 25 GB at 500 kB/s, it's not looking good. I try to access my old server from my new server directly, transfer rate is 50 MB/s, we're getting somewhere.
    13. The archive is compressed with LZMA, but I'm unable to expand the archive, lzma reports an succint error.
    14. Pushing my luck, I start a full MariaDB database backup on the old server. Meanwhile, I start copying the old server's files onto the new using scp. Wrong choice, permissions and symbolic links aren't preserved. Started again with rsync with better success.
    15. Importing the database backup was straightforward, works right out of the box with the already existing user credentials.
    16. I finish importing the files, fire the web server after fixing several unmet dependency issues, and here I am again!

    Phew. Did you miss me?

    #SysAdmining #SysAdmin #IDontKnowWhatImDoing

  9. 24 hours later, I'm back!

    Summary of the previous episodes:

    1. 3 days ago, my old dedicated server started spewing error messages about the CPU.
    2. On a hunch, I ran backup-manager with my existing configuration that's supposed to send the compressed database dump + files to an FTP backup server.
    3. I contacted my hosting provider to figure out the error.
    4. Answer was quick: "we can't physically intervene on the server, and the same offer isn't available anymore, you have to pick a new offer".
    5. I pick an upgrade, no answer for a day.
    6. A day ago, they made the new server available to me, and immediately removed access to the old server from my account, including the attached FTP backup storage.
    7. Asked the support to restore access either to the old server or at least the FTP storage. At this point I've lost all my Internet history from 2009 onwards.
    8. The "Customer Excellence Specialist Level 2" throws his hands in the air, saying that the CPU errors are making either SSH or KVM impossible.
    9. 12 hours ago, they restored my access to the server and the FTP storage. No luck, last backup on that server dates back to 2019. Server's IP is "very pingable" according to support, but no remote connection is possible.
    10. Through the hosting provider console, I rebooted in rescue mode. No luck, still no remote connection. I switch back to regular mode with a new reboot.
    11. I start to receive emails from my third-party monitoring system that my web sites are available again!
    12. I jump on my terminal, the remote connection works! I don't know how much time I have, I stop the web server to save CPU cycles. I found the fresh local backup files. I start to download them locally. 25 GB at 500 kB/s, it's not looking good. I try to access my old server from my new server directly, transfer rate is 50 MB/s, we're getting somewhere.
    13. The archive is compressed with LZMA, but I'm unable to expand the archive, lzma reports an succint error.
    14. Pushing my luck, I start a full MariaDB database backup on the old server. Meanwhile, I start copying the old server's files onto the new using scp. Wrong choice, permissions and symbolic links aren't preserved. Started again with rsync with better success.
    15. Importing the database backup was straightforward, works right out of the box with the already existing user credentials.
    16. I finish importing the files, fire the web server after fixing several unmet dependency issues, and here I am again!

    Phew. Did you miss me?

    #SysAdmining #SysAdmin #IDontKnowWhatImDoing

  10. 24 hours later, I'm back!

    Summary of the previous episodes:

    1. 3 days ago, my old dedicated server started spewing error messages about the CPU.
    2. On a hunch, I ran backup-manager with my existing configuration that's supposed to send the compressed database dump + files to an FTP backup server.
    3. I contacted my hosting provider to figure out the error.
    4. Answer was quick: "we can't physically intervene on the server, and the same offer isn't available anymore, you have to pick a new offer".
    5. I pick an upgrade, no answer for a day.
    6. A day ago, they made the new server available to me, and immediately removed access to the old server from my account, including the attached FTP backup storage.
    7. Asked the support to restore access either to the old server or at least the FTP storage. At this point I've lost all my Internet history from 2009 onwards.
    8. The "Customer Excellence Specialist Level 2" throws his hands in the air, saying that the CPU errors are making either SSH or KVM impossible.
    9. 12 hours ago, they restored my access to the server and the FTP storage. No luck, last backup on that server dates back to 2019. Server's IP is "very pingable" according to support, but no remote connection is possible.
    10. Through the hosting provider console, I rebooted in rescue mode. No luck, still no remote connection. I switch back to regular mode with a new reboot.
    11. I start to receive emails from my third-party monitoring system that my web sites are available again!
    12. I jump on my terminal, the remote connection works! I don't know how much time I have, I stop the web server to save CPU cycles. I found the fresh local backup files. I start to download them locally. 25 GB at 500 kB/s, it's not looking good. I try to access my old server from my new server directly, transfer rate is 50 MB/s, we're getting somewhere.
    13. The archive is compressed with LZMA, but I'm unable to expand the archive, lzma reports an succint error.
    14. Pushing my luck, I start a full MariaDB database backup on the old server. Meanwhile, I start copying the old server's files onto the new using scp. Wrong choice, permissions and symbolic links aren't preserved. Started again with rsync with better success.
    15. Importing the database backup was straightforward, works right out of the box with the already existing user credentials.
    16. I finish importing the files, fire the web server after fixing several unmet dependency issues, and here I am again!

    Phew. Did you miss me?

    #SysAdmining #SysAdmin #IDontKnowWhatImDoing

  11. 24 hours later, I'm back!

    Summary of the previous episodes:

    1. 3 days ago, my old dedicated server started spewing error messages about the CPU.
    2. On a hunch, I ran backup-manager with my existing configuration that's supposed to send the compressed database dump + files to an FTP backup server.
    3. I contacted my hosting provider to figure out the error.
    4. Answer was quick: "we can't physically intervene on the server, and the same offer isn't available anymore, you have to pick a new offer".
    5. I pick an upgrade, no answer for a day.
    6. A day ago, they made the new server available to me, and immediately removed access to the old server from my account, including the attached FTP backup storage.
    7. Asked the support to restore access either to the old server or at least the FTP storage. At this point I've lost all my Internet history from 2009 onwards.
    8. The "Customer Excellence Specialist Level 2" throws his hands in the air, saying that the CPU errors are making either SSH or KVM impossible.
    9. 12 hours ago, they restored my access to the server and the FTP storage. No luck, last backup on that server dates back to 2019. Server's IP is "very pingable" according to support, but no remote connection is possible.
    10. Through the hosting provider console, I rebooted in rescue mode. No luck, still no remote connection. I switch back to regular mode with a new reboot.
    11. I start to receive emails from my third-party monitoring system that my web sites are available again!
    12. I jump on my terminal, the remote connection works! I don't know how much time I have, I stop the web server to save CPU cycles. I found the fresh local backup files. I start to download them locally. 25 GB at 500 kB/s, it's not looking good. I try to access my old server from my new server directly, transfer rate is 50 MB/s, we're getting somewhere.
    13. The archive is compressed with LZMA, but I'm unable to expand the archive, lzma reports an succint error.
    14. Pushing my luck, I start a full MariaDB database backup on the old server. Meanwhile, I start copying the old server's files onto the new using scp. Wrong choice, permissions and symbolic links aren't preserved. Started again with rsync with better success.
    15. Importing the database backup was straightforward, works right out of the box with the already existing user credentials.
    16. I finish importing the files, fire the web server after fixing several unmet dependency issues, and here I am again!

    Phew. Did you miss me?

    #SysAdmining #SysAdmin #IDontKnowWhatImDoing

  12. 24 hours later, I'm back!

    Summary of the previous episodes:

    1. 3 days ago, my old dedicated server started spewing error messages about the CPU.
    2. On a hunch, I ran backup-manager with my existing configuration that's supposed to send the compressed database dump + files to an FTP backup server.
    3. I contacted my hosting provider to figure out the error.
    4. Answer was quick: "we can't physically intervene on the server, and the same offer isn't available anymore, you have to pick a new offer".
    5. I pick an upgrade, no answer for a day.
    6. A day ago, they made the new server available to me, and immediately removed access to the old server from my account, including the attached FTP backup storage.
    7. Asked the support to restore access either to the old server or at least the FTP storage. At this point I've lost all my Internet history from 2009 onwards.
    8. The "Customer Excellence Specialist Level 2" throws his hands in the air, saying that the CPU errors are making either SSH or KVM impossible.
    9. 12 hours ago, they restored my access to the server and the FTP storage. No luck, last backup on that server dates back to 2019. Server's IP is "very pingable" according to support, but no remote connection is possible.
    10. Through the hosting provider console, I rebooted in rescue mode. No luck, still no remote connection. I switch back to regular mode with a new reboot.
    11. I start to receive emails from my third-party monitoring system that my web sites are available again!
    12. I jump on my terminal, the remote connection works! I don't know how much time I have, I stop the web server to save CPU cycles. I found the fresh local backup files. I start to download them locally. 25 GB at 500 kB/s, it's not looking good. I try to access my old server from my new server directly, transfer rate is 50 MB/s, we're getting somewhere.
    13. The archive is compressed with LZMA, but I'm unable to expand the archive, lzma reports an succint error.
    14. Pushing my luck, I start a full MariaDB database backup on the old server. Meanwhile, I start copying the old server's files onto the new using scp. Wrong choice, permissions and symbolic links aren't preserved. Started again with rsync with better success.
    15. Importing the database backup was straightforward, works right out of the box with the already existing user credentials.
    16. I finish importing the files, fire the web server after fixing several unmet dependency issues, and here I am again!

    Phew. Did you miss me?

    #SysAdmining #SysAdmin #IDontKnowWhatImDoing

  13. changed not only the way I work as a software engineer, but also the way I use my computer more generally, since I use very similar key bindings to drive my terminal, web browser and even my file manager (however seldom I use this last one). RIP , thousands of developers across the world will be forever thankful for your contributions to our careers and the world in general.

  14. anyone having trouble with guile packages like artanis not being available for import?

    both guile and artanis have been installed via guix and i have the "art" command readily available in my terminal, but the moment i drop into a guile repl i don't get to "use-module" the library. (just an error that there is no module)

    #guile #artanis #guix

  15. #TIL: yes of course in Linux you can create a file name that starts with a Unicode BOM (Byte Order Mark). E.g. like this:

    $ python3 -c 'open("test".encode("utf-8-sig"), "w")'

    Funnily on my Ubuntu 20.04 system I didn't find a way to show the special character with "ls" (neither -b nor -q nor -Q helped). But in my terminal I could copy-paste the names from "ls" output and use them in other commands.

    Anyway... nice:
    $ ls -Q
    "test" "test"

    #UTF8 #Unicode #BOM #blindSpots

  16. @RL_Dane @teamtuck

    XTerm, urxvt, GNOME Terminal, and Konsole all have it. As has my terminal emulator. You just have to output the DECSCNM control sequence, just as you would with a real DEC VT.

    #DECVT #ECMA48 #T416 #terminal

  17. Welp....i'm back to trying #WarpTerminal again. I have no idea why i suddenly get urges to change my terminal every so often 🤷‍♂️

  18. I am seriously considering setting up a #RaspberryPi with an external HD and hooking it up to our modem at home and running a #privateinstance
    I am not a #sysadmin nor am I a #coder even though I sort of know my way around my #terminal but often times I end up super frustrated and throw up my hands in despair. As the #fediverse is nonprofit and federated I don't want to overburden some poor generous soul. I really love it here. Am I asking for trouble? @martinbogo @david @rabble @eqe thoughts?

  19. Hach... nice and clean 😻
    I just wonder how much more stuff I am going to put in my terminal output applet (aka #desklet 🙄)

    (watch out @sustainrelease , you have been shot...on the screen 😁)
    #toottui
    #showmeyourdesktop
    #showyourdesktop

  20. Update: I found this (macOS) utility for playing MIDI files from the command line and it works great with Lilypond/Neovim!

    ssb22.user.srcf.net/mwrhome/ma

    It's about a hundred lines of C, which means even if it's abandoned at some point I should be able to update it myself.

    The problem with a lot of similar programs is they use e.g., fluidsynth, when what I want is to play the file back over the IAC bus into Max/MSP, SuperCollider/etc. This lets me choose the starting point in the MIDI file and easily play it into IAC from my terminal!

    #Neovim #Lilypond #macOS #MIDI #Composer

  21. Update: I found this (macOS) utility for playing MIDI files from the command line and it works great with Lilypond/Neovim!

    ssb22.user.srcf.net/mwrhome/ma

    It's about a hundred lines of C, which means even if it's abandoned at some point I should be able to update it myself.

    The problem with a lot of similar programs is they use e.g., fluidsynth, when what I want is to play the file back over the IAC bus into Max/MSP, SuperCollider/etc. This lets me choose the starting point in the MIDI file and easily play it into IAC from my terminal!

    #Neovim #Lilypond #macOS #MIDI #Composer

  22. Update: I found this (macOS) utility for playing MIDI files from the command line and it works great with Lilypond/Neovim!

    ssb22.user.srcf.net/mwrhome/ma

    It's about a hundred lines of C, which means even if it's abandoned at some point I should be able to update it myself.

    The problem with a lot of similar programs is they use e.g., fluidsynth, when what I want is to play the file back over the IAC bus into Max/MSP, SuperCollider/etc. This lets me choose the starting point in the MIDI file and easily play it into IAC from my terminal!

  23. Update: I found this (macOS) utility for playing MIDI files from the command line and it works great with Lilypond/Neovim!

    ssb22.user.srcf.net/mwrhome/ma

    It's about a hundred lines of C, which means even if it's abandoned at some point I should be able to update it myself.

    The problem with a lot of similar programs is they use e.g., fluidsynth, when what I want is to play the file back over the IAC bus into Max/MSP, SuperCollider/etc. This lets me choose the starting point in the MIDI file and easily play it into IAC from my terminal!

    #Neovim #Lilypond #macOS #MIDI #Composer

  24. Update: I found this (macOS) utility for playing MIDI files from the command line and it works great with Lilypond/Neovim!

    ssb22.user.srcf.net/mwrhome/ma

    It's about a hundred lines of C, which means even if it's abandoned at some point I should be able to update it myself.

    The problem with a lot of similar programs is they use e.g., fluidsynth, when what I want is to play the file back over the IAC bus into Max/MSP, SuperCollider/etc. This lets me choose the starting point in the MIDI file and easily play it into IAC from my terminal!

    #Neovim #Lilypond #macOS #MIDI #Composer

  25. Someone here posted about the #Starship prompt for the terminal once. I liked it a lot and decided to try. Then I found out #iTerm2 - a better terminal emulator. Then there were themes, color schemes, and finally, I discovered #Fish shell.

    I now want to spend more time in my terminal than in UI.

    Starship prompt: starship.rs
    Fish shell: fishshell.com
    iTerm2: iterm2.com

    #terminalEmulator #FishShell #StarshipPrompt #terminal #console #homelab

  26. Someone here posted about the #Starship prompt for the terminal once. I liked it a lot and decided to try. Then I found out #iTerm2 - a better terminal emulator. Then there were themes, color schemes, and finally, I discovered #Fish shell.

    I now want to spend more time in my terminal than in UI.

    Starship prompt: starship.rs
    Fish shell: fishshell.com
    iTerm2: iterm2.com

    #terminalEmulator #FishShell #StarshipPrompt #terminal #console #homelab

  27. Someone here posted about the #Starship prompt for the terminal once. I liked it a lot and decided to try. Then I found out #iTerm2 - a better terminal emulator. Then there were themes, color schemes, and finally, I discovered #Fish shell.

    I now want to spend more time in my terminal than in UI.

    Starship prompt: starship.rs
    Fish shell: fishshell.com
    iTerm2: iterm2.com

    #terminalEmulator #FishShell #StarshipPrompt #terminal #console #homelab

  28. Someone here posted about the #Starship prompt for the terminal once. I liked it a lot and decided to try. Then I found out #iTerm2 - a better terminal emulator. Then there were themes, color schemes, and finally, I discovered #Fish shell.

    I now want to spend more time in my terminal than in UI.

    Starship prompt: starship.rs
    Fish shell: fishshell.com
    iTerm2: iterm2.com

    #terminalEmulator #FishShell #StarshipPrompt #terminal #console #homelab

  29. Someone here posted about the #Starship prompt for the terminal once. I liked it a lot and decided to try. Then I found out #iTerm2 - a better terminal emulator. Then there were themes, color schemes, and finally, I discovered #Fish shell.

    I now want to spend more time in my terminal than in UI.

    Starship prompt: starship.rs
    Fish shell: fishshell.com
    iTerm2: iterm2.com

    #terminalEmulator #FishShell #StarshipPrompt #terminal #console #homelab