Date: Wed, 28 Feb 2024 10:29:42 -0700 From: Modulok <modulok@gmail.com> To: Simon Connah <simon.n.connah@protonmail.com> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Remote development with neovim, tmux and SSH from macOS? Message-ID: <CAN2%2BEpYVeHc_PmUK=DUdJqfvuEZchN6x0gd8E3J03ypAno_j_g@mail.gmail.com> In-Reply-To: <6-vIFoipZvllLfrAwkIMmQ72B1mFYwcw7IRtdlG0JxM_2y5iN2WPWwMF1PVY8YWHw4jrx270Rg3PlA2qaVeJIPyudjoOhd-kdGd1Bt0M7m4=@protonmail.com> References: <6-vIFoipZvllLfrAwkIMmQ72B1mFYwcw7IRtdlG0JxM_2y5iN2WPWwMF1PVY8YWHw4jrx270Rg3PlA2qaVeJIPyudjoOhd-kdGd1Bt0M7m4=@protonmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000aed39d0612747d77 Content-Type: text/plain; charset="UTF-8" >> I've just set up a FreeBSD server and was curious about the best practices for when it comes to developing on FreeBSD? I have a Mac Studio but I'm not used to neovim or tmux at all and I get the feeling that learning them is going to take some time. >> What do you use for developing on FreeBSD servers? Unfortunately I can't install FreeBSD on my machine (well I can but it would be in VMware Fusion Pro). I don't develop on FreeBSD remotely. I don't see why you couldn't. FreeBSD is my daily driver. I write code in the `helix` text editor running inside `tmux`, itself inside the `alaccrity` terminal emulator (which you wouldn't have if developing remotely). I just use helix because it gives me a 90% vim-like experience with far less configuration out of the box. Like `neovim` it has built in LSP support and will use installed LSP servers e.g. rust-analyzer, clangd, gopls, taplo, etc. I've run VS code in the past, but mostly it's `helix` or occasionally `vim` for me these days. I've used `neovim` for a while but never really liked it as much. I found it was a lot more fragile - a lot of move fast and break things going on. On the rare occasion I need something like Docker, I'll boot a linux install running in `virtualbox`. For commercial solutions there's been a few Jetbrains products that are supported on FreeBSD. I ran `clion` for a bit and `pycharm` (Perhaps not remotely though, unless you want to get in deep with X11 forwarding and debugging any issues that arise, I don't know.) I also have a dedicated Windows box I can remotely boot and `rdesktop` into when I need it. I once tried setting this up to share the same physical CPU with virtualization running two operating systems at once and while it did work, it was a rough sojourn! Not worth the effort. Probably the best time investment is getting comfortable with vim motions. You can use these in `vi`, `vim`, `neovim`, `helix`, and there's even a plugin for `VS code` that supports them. They feel really clunky for a while, but save you tons of time later and are a transferable skill to other operating systems, software and domains. Best of luck! --000000000000aed39d0612747d77 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>>> I've just set up a FreeBSD server and wa= s curious about the best practices for when it comes to developing on FreeB= SD? I have a Mac Studio but I'm not used to neovim or tmux at all and I= get the feeling that learning them is going to take some time.</div><div><= br></div><div>>> What do you use for developing on FreeBSD servers? U= nfortunately I can't install FreeBSD on my machine (well I can but it w= ould be in VMware Fusion Pro).</div><div class=3D"gmail_quote"><div>=C2=A0<= /div><div>I don't develop on FreeBSD remotely. I don't see why you = couldn't. FreeBSD is my daily driver. I write code in the `helix` text = editor running inside `tmux`, itself inside the `alaccrity` terminal emulat= or (which you wouldn't have if developing remotely). I just use helix b= ecause it gives me a 90% vim-like experience with far less configuration ou= t of the box. Like `neovim` it has built in LSP support and will use instal= led LSP servers e.g. rust-analyzer, clangd, gopls, taplo, etc.<br></div><di= v><br></div><div>I've run VS code in the past, but mostly it's `hel= ix` or occasionally `vim` for me these days. I've used `neovim` for a w= hile but never really liked it as much. I found it was a lot more fragile -= a lot of move fast and break things going on. On the rare occasion I need = something like Docker, I'll boot a linux install running in `virtualbox= `. For commercial solutions there's been a few Jetbrains products that = are supported on FreeBSD. I ran `clion` for a bit and `pycharm` (Perhaps no= t remotely though, unless you want to get in deep with X11 forwarding and d= ebugging any issues that arise, I don't know.) I also have a dedicated = Windows box I can remotely boot and `rdesktop` into when I need it. I once = tried setting this up to share the same physical CPU with virtualization ru= nning two operating systems at once and while it did work, it was a rough s= ojourn! Not worth the effort.</div><div>=C2=A0</div><div>Probably the best = time investment is getting comfortable with vim motions. You can use these = in `vi`, `vim`, `neovim`, `helix`, and there's even a plugin for `VS co= de` that supports them. They feel really clunky for a while, but save you t= ons of time later and are a transferable skill to other operating systems, = software and domains.</div><div>=C2=A0</div><div>Best of luck!</div></div><= /div> --000000000000aed39d0612747d77--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN2%2BEpYVeHc_PmUK=DUdJqfvuEZchN6x0gd8E3J03ypAno_j_g>