I am BEGGING for any editor other than VSCode to have decent remote development. I want to go open source but everything I’ve tried (remote-nvim, distant, tramp, vscodium, etc.) just doesn’t cut it.
It has Microsoft BLObs baked in as part of the build process. VS Codium is the FLOSS distribution of VS code’s open source code. Liveshare doesn’t appear in the package repo Codium uses (because of the Microsoft BLObs it contains as an extension). For work I manually download the live share extension VSX and load it into vscodium
Have you tried running doom emacs in tmux on the remote server and accessing it with ssh? Doom emacs is all the good of an emacs environment, all the good of vim keybinds, and they worked in a decent amount of optimizations so it only loads the necessary stuff on demand (mine has a startup time of just over 1 second, slower than vim but barely an inconvenience). Can write a quick script to ssh copy (or git pull) your current configs on the server so you only have to maintain one set of configs if you want
Pair programming over the net. The old school way is tmux and vim but to do that you and your partner need port 22 open and most enterprises are gonna be like “hell no you can’t let people connect to your company owned work laptop SSH into your machine”
IntelliJ products my dude! If you go on there education side you can find the packages for free to compile yourself. There’s tons of guides online to do it.
@wiki_me I would like to see this model work. Because free software definitely benefits from funding and it's far more transparent like this than financing software efforts with hardware funds.
it’s not that transparent , for example if i am considering funding signal , i can look at the 990 form , see the top salaries, the amount spent on salaries, the number of employees and calculate the average salary. I don’t mind it if the shareholders make a 10-20 percent return but i don’t want to to be a 90 percent return (which basically no public company has, from what i have seen in tech companies it is somewhere around 10-30 percent).
Like some other replies said, it probably won’t get you a job by itself. But it may get you the interview if it’s the distinguishing factor between you and an equivalent candidate.
I got RHCSA (and later RHCE), and I think they were worthwhile. On cost, I would not go out of pocket for the Red Hat training if that’s the bundle you’re referring to. That stuff is priced for people that are being funded by their companies. Personally, I did self-study using Sander van Vugt’s materials. He has both books and videos for RHCSA, depending on your learning style. I found them to be excellent preparation for the exam.
This doesn’t sound like a calibration issue, but a driver issue sadly. It’s possible your new battery uses a different gas gauge IC that isn’t supported (yet).
I had a similar issue and had to reboot without a battery first, so the previous one was “forgotten”. It seems like the battery control is a completely separate circuit which in some cases needs to be be reset (if you have such options) or depleted so new batteries are recognized. Maybe search for such instructions for your specific laptop brand and model. HTH
If you’re serious about sticking to the terminal, it’s probably worth learning a terminal text editor like emacs or vim. Once you get the hang of them, you can be much more productive compared to something like nano.
I think it’s also worth learning about job control and/or terminal multiplexers, but I’ve yet to fully understand them myself.
Easy. Just learn to use it and it is already there.
With nano, you work with that letter where your cursor is at the moment. This is convenient, but limited.
With vim, you can also work with a word, or the whole line, or part of the line, or a section, or the whole file (or many files if you use the shell extension) and it goes all with the same ease.
Vim also allows you to keep your hands in place on the letters on your keyboard all the time. No need to move the hands around, grabbing the mouse and back, or the arrow keys, and thus search for the correct position for your hand every few seconds - which costs time and focus.
If I understand you correctly, I can write more efficiently because I can move to the next paragraph or sentence which I can’t with normal keybindings. Or special commands where I delete everything within “”. I understand the appeal of special moves but why not simply creating a Ctrl, Meta or alt command for that?
Vim uses these commands like di" (delete everything inside “”) instead of chords (holding multiple keys down at once). Both work fine. The reason vim does this is that many regard it as more ergonomic. You don’t stretch your hand/fingers out and you can keep your fingers at homerow. You might have heard about people getting an “Emacs Pinky”. It’s basically down to preference. I don’t use emacs but I know people use vim bindings in emacs (emacs is very scriptable after all). That way you can try or integrate vim like bindings without leaving your comfy emacs.
That is some very useful commands, thx! But I don’t think I’ll be using it often and hence I’ll lose the skill. I know ctrl+vxs or f etc because I use them very often. Anything that I don’t use is forgotten even if I’d use vim
Exactly! If you only have to edit small text files on a server once in a blue moon, nano is much less biomemory-heavy. But if you regularly write docs and code in l vim or neovim, it starts to pay off after a week or two.
I really enjoyed learning to quickly select and change entire words or lines, doing things like: :%s/replace_this_text/with_that/gEtc. If you enjoy that, you will soon get to a point where you miss the motions in your regular editor and install a vim extension in VS Code and stuff, just before fully switching to neovim
vim has better default keybindings/commands that allow for less movement of your hands. Nowadays, in reasonably current versions of nano, that's mostly it. The main difference is nano is somewhat usable but extremely inefficient unless you learn it, while vim forces you to learn it to get anything done at all, which also pushes people to spend a bit of time learning it in general.
If you're sure of the numbers you're using, vim's ability to repeat commands is also helpful. In practice I find that it's really hard to make use of them beyond low numbers, where nano can still achieve things in similar amounts of keypresses. Eg something to delete 3 words like <escape>3dwi can be done similar with a sequence like Alt-A ^→ ^→ ^→ ^K in nano. Make it 20 words and nano is going to be a lot slower, but that's quite an uncommon action.
But the practice is that nano users don't spend time learning any of that and just hold delete until the words are gone, which takes forever. Everyone that can do basics in vim quickly learns that you can dw words away and make it 3dw to delete 3 of them. The default, easiest to use & access tool for any given situation gets blamed not just for its flaws, but also for the users that don't want to spend time learning any tool.
After reading up on vim, I ended up at emacs now and I like the emacs style because it works with ctrl and meta keys which feels familar to me. I may learn emacs now.
Your example makes completely sense, yet I’ve never felt that the standard way was slow in the first place. I could see my workflow improving, but I guess I just want to have extra special commands. Thank you!
vim for one-time tasks at work. When people are proposing to script something, I open buffers, normalize the data and filter the results. I think in vim and I would very, very much recommend it, if you work with data or are a dev.
VIM for the win. I really enjoy the built in file browser accessed by the command :explore
I also code in go frequently and go-fmt and go-lint etc work flawlessly. You can use whatever LSP you want so you get your code tips and autosuggestion etc.
The tabs and split window functions are nice too. Plus if you learn Vi well it’s on almost every system in existence. Nano not so much
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.