wf-recorder VS onedark.vim

Try wf-recorder.

The closest thing is probably wf-recorder.

The spec is designed to be minimal and it's expected for compositors to work together and add additional features, for example here is the tool for screen recording on wlroots compositors (sway and what most wayland WM's use) https://github.com/ammen99/wf-recorder, even though most people claim wayland doesn't support screen-recording/screenshotting. We just don't have a universal tool for that that works on all compositors, pipewire however seems to be coming to fill that niche.

If you are on Wayland, wf-recorder Is a good choice .

As for screen recording, I’ve used wf-recorder (IIRC, not at PC atm) several times the past couple of weeks, works equally well.

The issue I'm encountering is described here in more detail (including images).

Wfrecorder [0] is what I use, doesn't have a fancy gui but it just works

0: https://github.com/ammen99/wf-recorder

A workaround for sharing the whole screen is to use wf-recorder [1], which supports capturing the whole screen, and feeding its output to a virtual V4L2 device using v4l2loopback [2]. Software that is able to capture from a V4L2-compatible webcam (i.e. most) can them capture from the virtual device without knowing anything about Wayland. It's not exactly the most CPU-efficient way of doing things, but if you can afford the cycles it works very well!

[1] https://github.com/ammen99/wf-recorder

[2] https://github.com/umlaeute/v4l2loopback

You want to use wf-recorder. This is in my sway config:

> set $screenrecord wf-recorder -g "$(slurp)" -f ~/screenshots/mov-$(date +"%Y-%m-%d--%H-%M-%S.mp4")

> bindsym Shift+Control+F6 exec $screenrecord

> bindsym Ctrl+Shift+BackSpace exec killall -s SIGINT wf-recorder

Hitting shift-control-f6 will spawn slurp which lets you click and drag to set the area you want to record. This will then launch wf-recorder and record the selected area, saving to ~/screenshots/mov-${date}. You can use ctrl-shift-backspace to kill the recorder and end recording.

https://github.com/ammen99/wf-recorder

https://github.com/emersion/slurp

Onedark has been solid so far for me

As you can see only the langauge keywords are being highlighted but not function and variable names. I am using onedark and coc.nvim.

Github: joshdick/onedark.vim

It turns out this was an issue with my theme, onedark.vim, which was out of date due to some broken configuration somewhere. I reinstalled it with vim-plug and read the README. I learned that my terminal support truecolor, so I turned it on for onedark. That fixed the problem. There's no highlight in 256-color mode, but the highlight works fine in truecolor mode. Strange.

ful1e5/onedark.nvim is completely written in Lua which means it loads way faster. It also supports Treesitter which provides way better syntax highlighting, which dick/onedark.vim doesn't. Lastly, my favourite feature is that it allows you to override/create highlight group configs and pass to the plugin before loading the colorscheme which makes customizing highlight groups super easy (and I would guess faster as well?) compared to calling highlight a bunch of times in your config. Here's What my configuration of it looks like if you're curious.

something similar to this but I am using nvim

I know it's not strictly Linux related but I'm not sure where else to post this, sorry. I have been in the process of configuring my setup including Alacritty but the colors for it look off. I'm using the one dark color scheme but the colors in the terminal don't quite match, specifically the yellow/orange looks like a dark brown. I read here that you can check if a terminal is using truecolor by using this command:

since it doesn't work with : joshdick/onedark.vim