Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
One thing I like to do if i have unstable internet (eg mobile data in train) is to open a screen and then edit away there. If i disconnect I can just screen -r and tada! Back at where I left off :)
Scrolling is kinda weird though.. have to press Ctrl +A+D to be able to scroll properly on command output -
@ThatPerlDeb Oh yeah, screen.. I love that! I've pretty much made a habit of it that when I'm working on that crappy Windows host and doing a long task (say rsync of several hundreds of GB or something like that) it's always prepended by "screen -dmS $someJob". And when I have to get back to it, "screen -radU" is my personal default set of command-line switches here.
For unstable connections like those on trains, do check out mosh by the way! It's pretty much a drop-in replacement for SSH that's made exactly for unstable connections. Keyboard input and things like that are handled locally to improve the experience on slow connections, and there's virtually no timeouts to speak of, it just reconnects again to the server and catches up whenever the network connection gets active again. Highly recommended! -
@Condor Never heard about mosh but I checked it out and it looks amazing! Gonna try it out soon 😀 thanks for the recommendation!
-
@ThatPerlDeb I use tmux to do the same
-
@qdsp13 probably damaged hardware or buggy drivers. Unless they're using Win98 or early beta test versions, BSOD is a thing of the past.
-
@qdsp13 @Fast-Nop Fortunately they don't happen that often.. but they used to. Software updates to Windows miraculously reduced it to once every few days. My drivers nor the hardware changed. But it's a hardware issue, right? It's a driver issue, right?! Like fucking hell it is.
@CodeMasterAlex if only it actually TOLD me what the hell is wrong!!! Memory management, IRQ errors, kernel security failure (well that makes sense, given that it's Windows we're talking about), every fucking BSOD and their cat, this fucking thing has had it. So what is it, and how can it be resolved? I have no fucking idea. Why is it getting all those BSOD's? At this point, the moon and the sun being in a position that the system doesn't like seems the most plausible to me. Because what else could cause *so* fucking many of them, after mere days of uptime?! -
@GyroGearloose I have no idea to be honest ¯\_(ツ)_/¯ perhaps Microsoft just doesn't like me all that much.
*edits file on remote server*
WanBLowS: naah you can't 😈
*le wild BSOD appears for the over 9000-th time*
... Yeah. Windows, great job. Who needs system integrity when they're working on remote servers anyway, right?!
And to top it all off, le reboot mentions that they're working on fucking "features" again. That's what you needed to BSOD for?! For a goddamn motherfucking feature?!! Fucking piece of shit.
At least when I opened vim on that server again, it's saved everything neatly in the .swp files, ready for recovery. Now that's neat, isn't it? Microsoft, the Linux community has already moved on to nvim in terms of development, but maybe, just maybe, you can learn a thing or two from our "legacy software", vim.
As for me, maybe it's time to take out my Arch laptop again. At least that won't crap out on me because the sun and the stars are in a position that the OS doesn't like, or something stupid like that. FUCK YOU MICROSHIT!!!
rant
wanblows