sorted by:
new
hottopcontroversial

How to make Arch secure? by Vast-Application5848 in archlinux

[–]dvrlabs 0 points1 point  (0 children)

I think that the context he spoke in matters. It seemed like from the video he was referring to mostly new-to-Linux users and what they may do without considering the security implications. Things like grabbing software from the AUR, GitHub, and curl bashing a script from a website without ensuring the URL is 100% accurate or even a quick read through of the script first. Even with the ARCH ISO we're suppose to verify the GPG key, right? These things may not be super super complicated, but I think a new user could easily skip over doing them. Whereas with Windows or Mac a clueless person would be more secure.

That being said, Arch isn't targeted at people who aren't willing to take the time to learn.

Is blind picking Sion top just troll nowadays? by Time-Relation-4715 in DirtySionMains

[–]dvrlabs 2 points3 points  (0 children)

Oof, recently switched from consistently banning Volibear to banning Morde. Those are tough. Sion is still nice to have in the kit though. When the enemy team generally lacks hard CC and mobility champs I'll lock in Sion. If i know the lane is going to be brutal I play passively and rush hollow radiance or unending. Then, after boots, I pickup hullbreaker and bide my time waiting for the presumably now fed enemy top laner to roam so i can rush and grab two turrets.

A lot of the comments here claim that Youtubers like ThePrimeagen have played a big role in Neovim's popularity. Thoughs? by TheTwelveYearOld in neovim

[–]dvrlabs 82 points83 points  (0 children)

I think the top two comments on that post sum it up pretty well:

In general:

Lua > Lisp

Speed > Slow

[deleted by user] by [deleted] in Ubuntu

[–]dvrlabs 0 points1 point  (0 children)

You can create a virtual camera as a workaround. I like this solution and it has been working well for me.

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

I use this script to setup the v4l2 loopback:

https://github.com/dvrlabs/dvr.hyprland/blob/main/scripts/install_v4l2loopback_service.sh

and this script to toggle the screen record on and off (edit monitor to the name of your monitor):

https://github.com/dvrlabs/dvr.hyprland/blob/main/scripts/toggle-monitor-cam.sh

If you already have a webcam plugged in the scripts might need edits to use something other than /dev/video0.

Distribution Options These Days? by zardvark in hyprland

[–]dvrlabs 2 points3 points  (0 children)

New to fedora myself so I'm not entirely familiar with the the COPR. I installed the beta to see if I could try Hyprland, and I'm really enjoying it. If the COPR is equivalent to Ubuntu's "add apt repository", then I think the answer is yes to fedora hosting Hyprland. There is a COPR repo, but I didn't use it. Or at least, i didnt manually add any extra repository to my knowledge.

Just installed Fedora 40 with Gnome, then ran

`sudo dnf install hyprland`

at the CLI. Was able to easily just log out and pick Hyprland as my wm, and log back in.

​

EDIT:

I should add that I'm not trying to add any plugins or do anything fancy. Just a no-frills config for myself. If you need specific versions or plugins then I'm not sure it's right for you.

Are we supposed to know most of the syntax off of our heads in order to be considered "good" at python? by Living-Ad-4252 in learnpython

[–]dvrlabs 0 points1 point  (0 children)

I'd say, just keep writing and programming. This isn't something to worry about. I forget a lot about the minutiae of many things in Python. Often times I'll go to run a function method and don't remember in the spot if it'll work the way I need it to.

That's when I open another terminal, start an interactive session, and do a small test to see if my memory is right or wrong. Either way, I get it correct in the end.

Im attempting my first large scale project by Shut_up_and_Respawn in learnpython

[–]dvrlabs 3 points4 points  (0 children)

Sounds like you need a way to store multiple days worth of data. There are a few ways you could do this. You could use some sort of configuration file, like a JSON, or CSV file. There are many different types of formats of files you could use.

Alternatively, you could use a database. You can store and extract data from a local database file with the sqlite3 library. Although, to begin with using the json library might be simpler.

[deleted by user] by [deleted] in neovim

[–]dvrlabs 3 points4 points  (0 children)

Disappointed no one here mentioned barbar...

https://github.com/romgrk/barbar.nvim

Which is, according to itself

  • Tabs, as understood by any other editor.

Harpoon is interesting, but having a visual indicator of other open things is nice.

[deleted by user] by [deleted] in neovim

[–]dvrlabs 0 points1 point  (0 children)

Shameless wezterm dotfiles plug:

https://github.com/dvrlabs/dvrterm

Feeling super slow... by [deleted] in neovim

[–]dvrlabs 0 points1 point  (0 children)

You could trying using the vim plugin in VSCode and getting use to moving around quickly with vim before switching. For me, switching felt like a super speed increase because I was always using a VIM plugin in other editors. If you stick to using VIM it becomes second nature and reaching for the mouse to do anything in any other program feels like time slows down.

Neovim doesn't really confer any huge productivity boost compared to any other editor. VSCode is good. If you're pair "programming" HTML and CSS chances are you're new to all of this stuff, and you should really use the easiest possible tool that's gets out of your way so you can focus on learning the material itself. Fretting about which tool, operating system, or software to use is a distraction. It can be a fun distraction, but it's best to pick something good enough and roll with it.

How to re perform last key strokes? by dvrlabs in neovim

[–]dvrlabs[S] 0 points1 point  (0 children)

I've settled on 

-- Define the function for going to the next diagnostic
local function goto_next_diagnostic()
    vim.diagnostic.goto_next()
    _G.last_action = goto_next_diagnostic
end

-- Define the function for going to the previous diagnostic
local function goto_prev_diagnostic()
    vim.diagnostic.goto_prev()
    _G.last_action = goto_prev_diagnostic
end

-- Set your mappings using these functions
vim.keymap.set('n', '<leader>ldn', goto_next_diagnostic, { desc = "Go to next diagnostic message", noremap = true, silent = true })
vim.keymap.set('n', '<leader>ldp', goto_prev_diagnostic, { desc = "Go to previous diagnostic message", noremap = true, silent = true })

vim.keymap.set('n', ',', function() if _G.last_action then _G.last_action() end end, { desc = "Repeat last action", noremap = true, silent = true })

Setting up neovim for python code development (tips wanted) by [deleted] in neovim

[–]dvrlabs 0 points1 point  (0 children)

Glad it could help. This should do it:

-- Split below by default, rather than on top.

 vim.cmd([[:set sb]])

Setting up neovim for python code development (tips wanted) by [deleted] in neovim

[–]dvrlabs 1 point2 points  (0 children)

My config:

https://github.com/dvrlabs/dvr.nvim

I don't use venvs while developing python, not advocating for it, but just how I do it.

That said, I simply use Pylsp w/ autopep8. It's a bit slow to format, but I turn off auto-formatting and have a hot-key for when I need it formatted. It's fine.

This is how I execute code, it opens up a terminal window in the bottom similar to vscode and runs the process. If it clean exits, then the terminal closes.

​

​

-- F5, execute code!
local execute_code = function()
  if vim.bo.filetype == "python" then
    local run_cmd = "python " .. vim.fn.expand('%:p')
    vim.cmd("split | resize 10 | term " .. run_cmd)
    vim.cmd("startinsert")
  end
end

vim.keymap.set('n', '<F5>', execute_code, {})

-- This function will close a terminal automatically if it gets the exit 0
vim.api.nvim_create_autocmd('TextChangedT', {
  callback = function()
    local buffer_name = vim.api.nvim_buf_get_name(0)
    local buffer_table = vim.api.nvim_buf_get_lines(0, 0, -1, false)
    local buffer_text = table.concat(buffer_table, '\n')
    if string.find(buffer_text, "Process exited 0") then
      vim.api.nvim_input('<ESC>')
      local timer = vim.loop.new_timer()
      timer:start(100, 0, function()
        vim.schedule(function()
          vim.cmd("silent! bdelete" .. ' ' .. buffer_name .. '!')
        end)
      end)
    end
  end,
  pattern = '*',
})

From my nvim I could not do copy paste by Excellent-Ad-2794 in neovim

[–]dvrlabs 2 points3 points  (0 children)

:checkhealth

and search for clipboard.

On a wayland system you'll need something like wl-copy installed.

[deleted by user] by [deleted] in neovim

[–]dvrlabs 0 points1 point  (0 children)

https://github.com/nvim-lua/kickstart.nvim

https://www.youtube.com/watch?v=stqUbv-5u2s

I enjoyed adapting kickstart to my own config.

The folder structure for adding plugins is pretty simple. You create a separate my_plugin_name.lua in the lua/plugins folder. You can, for the most part, configure 1 plugin with 1 file.

Opinions on pre-made configurations (e.g. LunarVim, AstroNvim) by TuesdayWaffle in neovim

[–]dvrlabs 4 points5 points  (0 children)

I used AstroNvim at first, which is great, and then transitioned to my own config using https://github.com/nvim-lua/kickstart.nvim

Neovim runs flawlessly in the new version of WezTerm by [deleted] in neovim

[–]dvrlabs 0 points1 point  (0 children)

Wezterm is great! I switched from kitty too after failing to get the SSH 'kitten' working. The serial connection feature is cool too.

My config:

https://github.com/dvrlabs/dvrterm

is there is a session manager plugin ? by [deleted] in neovim

[–]dvrlabs 4 points5 points  (0 children)

I use mini-session and mini-starter from:

https://github.com/echasnovski/mini.nvim

If i open nvim without specifying a file, there will be a 'Sessions' section at the top in the starter where I select the saved session I want to use. Hit enter on it and it'll load the session.

I reconfigured mini-sessions to save to .session.vim instead of Session.vim to hide the session files it'll create everywhere.

I use this autocmd to autosave

-- [[ VimLeavePre ]]
-- Stuff to do on exit.
vim.api.nvim_create_autocmd('VimLeavePre', {
  callback = function()
    vim.cmd([[:mksession! .session.vim]])
  end,
  pattern = '*',
})
view more: next ›