skipperwannabe

joined 1 year ago
[–] skipperwannabe@lemm.ee 2 points 11 months ago* (last edited 11 months ago) (5 children)

Initially, I used HDMI -> Soundbar -> Monitor. The soundbar handles the sound and forwards the video signal to the monitor. Right now, it's the same, except it is using display port for Laptop to Soundbar connection. Hope I understood the question correctly. If you ever figure out the delay, please do update with a solution.

[–] skipperwannabe@lemm.ee 1 points 11 months ago (7 children)

I have noticed this too on pipewire. Everytime a new audio stream starts , even from a paused state, there is a small delay before it is heard. Not a syncing problem as the audio is synced, but a delayed start. I thought it might have something do with the sound bar I had routed the audio through. Based on your experience, seems not. I did experience the same delay when using HDMI port instead of DisplayPort too (IIRC). So it might be something else not related to port.

[–] skipperwannabe@lemm.ee 1 points 1 year ago

There is also this official extension. IIRC, this also makes sure that all the meta owned sites are not able to interact with other sites, but can work fine with each other. It also makes sure that any links leading to their sites also only open in the container, maybe also sanitized to remove the tracker from original link. The last part I am not sure, as I might be confusing it with a different extension. But if you are using any of the Meta sites, I would recommend it.

[–] skipperwannabe@lemm.ee 1 points 1 year ago (1 children)

Sorry, I missed the previous message. Glad you got it working with the help of @rewire@programming.dev.

Regarding the massive list, yeah that is expected. If you haven't got fd or rg installed in you system, telescope falls back to regular find. Find doesn't have any sort of builtin ignore list, so it just lists all the files. If you are using the builtin.find_files normally, I think it executes (at least something close to)

find -not -path "*/.*" -type f

With the hidden=true, it does something along the lines of

find . -type f

Both of these commands are executed from the cwd (normally the directory you started nvim in). If you want it only show to a certain depth, you can use the telescope's setup to change the default find_command

telescope.setup({
  pickers = {
    find_files = {
      find_command = { "find", "-maxdepth", "3", ".", "-type", "f"},
    },
  },
}

Modify that to your requirement and then use the keymap to call builtin.find_files() and it should work.

[–] skipperwannabe@lemm.ee 4 points 1 year ago* (last edited 1 year ago) (5 children)

If you have fd installed, telescope uses it's settings including ignore files (including .ignore and .gitignore etc). So if have the default settings for fd to show hidden files, telescope will respect that.

Otherwise, if you want to have hidden files only in telescope without changing the default behavior of fd , when using your key binding, change it as follows:

vim.keymap.set("n", "<leader>ff",  function() builtin.find_files({hidden=true}) end, {})

Edit: Change to keybind format Edit2: Wrap builtin in function call

view more: ‹ prev next ›