A few ideas:
Try to create a service that lets you send a message over ActivityPub to a lemmy community.
Try to use Elixir to read and then flip the 3rd bit of an arbitrary byte stored in your system's RAM.
Try to make a simple game in c++ compiled to Webassembly to be played in a browser.
I wouldn't expect that you could go from zero experience with Neovim/Vim to more efficient than the editor you've been using extensively in less than a month. most of the people that responded here had been using Vim prior to switching. The one that had no prior Vim experience took half a month to get the basics down and be comparable with their prior editor (VScode).
Everything you're after is available, but trying to learn it all at once can be overwhelming as you've been experiencing.
So one step at a time, I suggest that you:
:help
while in Normal mode in Neovim.
The best chat beginner community for Neovim that I know of is in The Odin Project Discord. There's a Neovim thread in the #odin-general channel there. (Bonus, while you're in the Discord you can help out others trying to learn web development.)
The point is to find your own way by learning from others, not to simply mimic others. Although up front, mimicing what others are doing is a good way to get started.
Take your time with all of this, there's no rush.
That looks useful. Thanks for the pointer!
Unfortunately, in this case I'm not interested in a summary. I already watched the video and would need to refer back to it for details, not general concepts.
I'll definitely use that site in the future though.
Edit: looks like it's not so good for long videos.
It's a shame that he didn't do a writeup on this. It's nice to have a video to demo the workflow, but it's really annoying to go back to the video to get details to try it yourself.
I don't think this gets at what they are trying to do. I think they want to set up access control to the repo. They want access to the repo to be private but also use it for themselves like any other repo.
This is something companies do, but I believe acess control is by firewall/VPN not the repo tools. As far as I can tell, if you can access the IP address of the URL assets you can get the assets. So making it private is a matter of setting up access to the server(s) not a configuration of the tools that manage the repository.
I'd ask on a debian focused irc/chat room/ mailing list to find out more.
I try to be positive here on programming.dev but someone gave you an incredibly thoughtful reply and you returned the favor with absolute disrespect. I think the only positive outcome here would be for me to simply block you and encourage others to do the same.
@ericjmorey
@programming.dev