home.social

Search

360 results for “myTerminal”

  1. Yet another compliment (this time from a driver) proves the same thing: a dirty car is more likely to get compliments.

  2. I humbly seek your for our ingratitude toward the gifts you bestowed upon us. I implore you, in my , that in the creation of future universes, those who seek to might be compelled to grant the rest the agency to 'opt-in' to any path of .

    ...

  3. Well, so much for this one. I really can't wait a couple of seconds before my terminal becomes usable again just because I tried something as outrageous as adding another tag to a task.

    But hey, at least this program that has never once crashed on me in over a decade of extensive usage is now safe from those dastardly memory bugs. 🎉

    #TaskWarrior

  4. I was a gomuks user in the past, so recently when setting up Matrix again I decided to try iamb.chat and I love it.

    It has a very minimal UI. You can set up a layout, exit and by default it will remember it.

    Controls are vim-like all the way to macros. You can have tabs for things like rooms, DMs, the room list, and you can further split tabs into panes.

    After tweaking the space taken by the usernames on left side of chat, I now have a compact Matrix monitor on my terminal.

    #matrix #gomuks #iamb #vim #vi

  5. "Software efficiency halves every 18 months, compensating Moore’s Law." - May's Law

  6. "So much complexity in software comes from trying to make one thing do two things." - Ryan Singer

  7. @SDF has migrated the twenex tops-20 users to a new XKL TOAD2 system. (If you don't know what that is, it's like a modern re-imagined PDP-10) - it's really obscure, really rare, and super neat! It apparently now also is able to run bash?! (I never thought I'd see bash on tops-20) - seems to be doing some mapping of the tops-20 paths to be more unix-like. Also sounds like a tops-20 bootcamp is in the works. #tops20 #pdp10 #sdf - Now i just need to get it working better w/ my terminal. :)

  8. 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.

  9. JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.

    Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.

    I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.

    My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.

    Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.

    Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.

    The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.

    JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.

    Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.

    Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.

    #JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies

  10. JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.

    Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.

    I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.

    My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.

    Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.

    Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.

    The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.

    JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.

    Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.

    Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.

  11. JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.

    Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.

    I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.

    My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.

    Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.

    Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.

    The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.

    JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.

    Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.

    Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.

    #JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies

  12. JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.

    Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.

    I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.

    My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.

    Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.

    Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.

    The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.

    JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.

    Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.

    Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.

    #JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies

  13. #TheGate for #Amiga
    My terminal simulator is arising!
    Implemented:
    - Scrolling (only up like an old style term)
    - Labels
    - Jump to labels
    - Variables Increase & decrease by 1
    - JIFEQ -> Jump to label if variable is equal to a certain value

    The shot shows the terminal executing a loop for 2 times increasing a variable, when the variable reaches 3 the program jumps to a label and prints the last line.

    IT WORKS! IT WORKS!! 😃

    note on the left the source program (# = comments)

    #AMOS #AMOSPro

  14. Here are some features I implemented in my terminal simulator within my #Amiga game #TheGate :amiga: 😃

    Lot of fun coding this stuff! 😍

    #AMOS #AMOSPro #indieDev #gameDev #soloDev

  15. An update of my terminal-frame Emacs package.

    - Avoid other buffers being shown in the terminal frame as far as possible for emacsclient, find-file and other-buffer
    - Amend the frame title such that we can see how many shells are open in the frame.

    codeberg.org/harald/terminal-f

    #terminal_frame
    #Emacs
    #foss
    #programming
    #shell

  16. An update of my terminal-frame Emacs package arrived on codeberg, the dedicated terminal frame for Emacs' M-x shell.

    Since most action in a terminal window happens at the botton, I moved the minibuffer, rarely used in a dedicated terminal frame, to the top of that frame.

    codeberg.org/harald/terminal-f

    #terminal_frame
    #Emacs
    #foss
    #programming

  17. I realized never worked for me because I maintained my /boot inside an encrypted volume alongside /, /home, etc.

  18. Just updated my terminal setup to get roasted by my Linux shell history. Every command I run gets judged by a local LLM, and the verdict goes straight to my window title. 😅

    Including a few favorites:

    "Oh, I see you use Arch, by the way..." when I update pacman
    "Looking for your Brains?..." when I ran simonw's llm tool
    "pwd, after ls? How lost are you?", after... well runinng pwd when not recognizing the files in my cwd.

    GIF shows it in action

    #linux #terminal #llama32 #llm #archlinux #shellshaming #ramtospare

  19. So I run Fedora desktop...I am looking to maybe have a local AI run that I can chat with about python...I don't care about a fancy GUI..I want it stuck in my terminal. I don't need it to edit my files I can do that. I don't want it on the web or calling home. I want a local interactive python manual.

    Anyone have anything that can point me the right way?

    #run_local_ai #python #privacy

    I am still wary of the ethics of local AI ....if someone has content for that let me know #aiethics

  20. So I run Fedora desktop...I am looking to maybe have a local AI run that I can chat with about python...I don't care about a fancy GUI..I want it stuck in my terminal. I don't need it to edit my files I can do that. I don't want it on the web or calling home. I want a local interactive python manual.

    Anyone have anything that can point me the right way?

    #run_local_ai #python #privacy

    I am still wary of the ethics of local AI ....if someone has content for that let me know #aiethics

  21. So I run Fedora desktop...I am looking to maybe have a local AI run that I can chat with about python...I don't care about a fancy GUI..I want it stuck in my terminal. I don't need it to edit my files I can do that. I don't want it on the web or calling home. I want a local interactive python manual.

    Anyone have anything that can point me the right way?

    #run_local_ai #python #privacy

    I am still wary of the ethics of local AI ....if someone has content for that let me know #aiethics

  22. So I run Fedora desktop...I am looking to maybe have a local AI run that I can chat with about python...I don't care about a fancy GUI..I want it stuck in my terminal. I don't need it to edit my files I can do that. I don't want it on the web or calling home. I want a local interactive python manual.

    Anyone have anything that can point me the right way?

    #run_local_ai #python #privacy

    I am still wary of the ethics of local AI ....if someone has content for that let me know #aiethics

  23. So I run Fedora desktop...I am looking to maybe have a local AI run that I can chat with about python...I don't care about a fancy GUI..I want it stuck in my terminal. I don't need it to edit my files I can do that. I don't want it on the web or calling home. I want a local interactive python manual.

    Anyone have anything that can point me the right way?

    I am still wary of the ethics of local AI ....if someone has content for that let me know

  24. @virtuous_sloth My setup involves a fairly over complex graph on , but I'd rather keep web bookmarks on . Flat lists don't work for me, especially once they grow tall such that I'm not able to see all the items at once.

  25. Attempt 03: I found , which is blazing fast, and though I managed to replicate my color themes pretty closely to what I like using the ".Xresources" file, getting text-zoom and clipboard to work is a little too much work for my "portable" need.

  26. A few months ago my terminal colours were suddenly messed up. I have no idea what caused that since I didn't touch any related settings for years.
    Now I have a lot of pink on pink, which is obviously not readable.

    I managed to partially fix it by deleting some colour definitions from #Xdefaults.

    Did someone else experience the same?

    #urxvt #rxvt