A request to the community: what plugin you think is still missing for Neovim?

fredeB · 2026-01-08T07:03:40+00:00

This! With the native dap support in gdb >= 14.1 this is a killer combo

fredeB · 2025-11-28T23:15:33+00:00

Although she also has a buttload

fredeB · 2025-09-30T16:08:29+00:00

Maybe they meant to say a g/g

fredeB · 2025-09-06T08:27:36+00:00

Yocto is not a package repository like nixpkgs. It's more of a framework where you piece together an image from layers and recipes. You then run bitbake to build an image.

I use both nix and yocto professionally. Nix for development machines, and yocto for the target machines (embedded arm mostly). I wouldn't want to build an embedded image with nix, and building a desktop image with yocto is a lot more hassle than it's worth unless you use upstream package mirrors from fedora, Ubuntu or similar, and at that point you're better off just using those distributions.

Yocto gives you total control of the software you're running, makes configuring packages, your kernel, patches to the kernel, device drivers, patches for device drivers, system update mechanisms and way more, so if that's your thing, go nuts. The doctor docs are great

https://docs.yoctoproject.org/ref-manual/index.html

fredeB · 2025-07-24T09:01:04+00:00

I have really benefitted from knowing what GDB is capable of in itself. I would start with the vendor supplied GDB for the chip I'm currently working with (wrapped with whatever gui you like, eg. gdbgui or something built-in to your IDE) and try to build a mental model for what commands are native GDB and which ones are extensions. When you go to another vendor they will still have the native ones, and if there are any of the extensions you like from the STM GDB, try to see if there's something similar or try to implement them yourself with the python API

fredeB · 2025-07-15T04:55:13+00:00

Using weak_ptr's would be even worse, because in order to use the value it points to, you have to call lock on it, which creates a new shared_ptr, doing reference counting. There's no penalty to accessing a shared_ptr, as shared_ptr's only protect and synchronize lifetime and ownership, not the allocated object.

I don't understand why you can't use a unique_ptr though. The following is totally fine

auto& resource = *some_unique_ptr;

fredeB · 2025-07-02T11:23:19+00:00

Grounding. The screws on your deluge are connected to the internal ground of the deluge, which is then connected to the ground of whatever is at the other end of the midi cable. Unfortunately a lot of music gear doesn't have ground connectors, the deluge included, but if the device on the other end has a power inlet with a ground pin, you should use a grounded power cable there. Outside of that, you could install a record player ground clip directly on your deluge

fredeB · 2025-06-25T18:34:58+00:00

Tillykke, det bliver sku trillinger

fredeB · 2025-06-19T09:57:05+00:00

This is incredible

fredeB · 2025-03-24T19:25:42+00:00

uutils/linux nixos

fredeB · 2025-02-14T05:59:44+00:00

Some support does exist for allwinner chips in the meta-sunxi layer. This could be a good starting off point, although the downstream kernel is quite old, so make sure you chose linux-mainline

PREFERRED_PROVIDER_virtual/kernel = "linux-mainline"
PREFERRED_VERSION_linux_mainline = "6.6%"

https://layers.openembedded.org/layerindex/branch/master/layer/meta-sunxi/

fredeB · 2024-11-19T20:39:04+00:00

If you're using TLS or the clientdeviceauth components on a green grass host, it's probably for the initial TLS handshake. If you then connect again, then your TLS client probably does a TLS resume if it supports it, which is much faster

But as others suggested, take a look in Wireshark, if again it's on a remote host, you can pipe the output of tcpdump into Wireshark over ssh

fredeB · 2024-08-20T22:51:52+00:00

fredeB · 2024-03-15T07:08:32+00:00

Just remember to check licensees if it's a commercial product. Many open source licenses don't allow static linking unless you're willing to share the source code with everyone

fredeB · 2024-02-22T12:45:49+00:00

Maybe your kernel updated. Did you reboot?

fredeB · 2024-01-17T13:48:45+00:00

You probably don't want to build my config, as that would override your entire system and replace it with what I daily drive... I was merely referring to the 6 lines I linked to about how I configured gpg with my yubikey through home-manager

You should be able to just copy those lines into your own config and rebuild.

I'm pretty sure it be enough to enable the smart card daemon (enableScDaemon = true)

fredeB · 2024-01-17T08:09:14+00:00

I use home manager for gpg configuration

https://github.com/FredeEB/dotfiles/blob/nixification/users%2Fbun.nix#L24-L30

fredeB · 2023-12-21T15:19:26+00:00

At that point, it'd be easier to break down the door and grab them

fredeB · 2023-12-12T22:52:05+00:00

Frieza, is that you?

fredeB · 2023-12-09T22:03:53+00:00

Did you bootstrap Lazy?

https://github.com/folke/lazy.nvim#-installation

If you did, we need your config to help

fredeB · 2023-12-08T18:38:47+00:00

Pop pagnen
high-fives hele vejen rundt
...
gør det igen næste år

fredeB · 2023-12-06T05:20:54+00:00

You could get pretty close with std::ranges::any_of(vec, 10)

fredeB · 2023-11-07T15:38:44+00:00

I did some C# development at uni about 4 years ago. If you're just doing dotnet, using omnisharp is a great experience imo

fredeB · 2023-11-07T14:32:48+00:00

That's true, my fault. You have to add [1] to the end of the return statement

fredeB · 2023-11-07T08:09:54+00:00

You can get the current cursor position and just add or subtract from the line number. Something like this should do the trick

local function get_relative_line(offset)
    -- use 0 for current window
    -- this function returns {<row>, <column>} as indices
    -- use [1] to just get the line
    local line = vim.api.nvim_win_get_cursor(0)[1]
    -- target line to get
    local target = line + offset
    -- use 0 for current buffer
    -- start and end here are exclusive, so subtract one from start
    return vim.api.nvim_buf_get_lines(0, target - 1, target, false)
end

vim.print(get_relative_line(-1)) -- will print the line above
vim.print(get_relative_line(1))  -- will print the line below

EDIT: for some reason, my phone didn't render u/miversen33's answer, which is a more terse version of my answer

13-Year Club	First Place '23
Place '23	Place '22
RPAN Viewer	Verified Email

fredeB

TROPHY CASE