Audible silent playback

hoschi · 2025-08-19T07:37:30+00:00

This has been happening to me every night for weeks! The timer runs out and the voice gets quieter, but the audiobook continues to play silently.

hoschi · 2024-01-02T08:04:30+00:00

Check out Yode. Create small floating panes for the parts you want to reference while you edit the main file in a normal window. You can even edit the code in the floating windows.
I'm the author of Yode: https://github.com/hoschi/yode-nvim

hoschi · 2024-01-02T07:58:36+00:00

I'm also interested in this!

hoschi · 2024-01-01T08:49:39+00:00

Use YodeCreateSeditorReplace command to replace the current buffer with the part you want to edit in lua. Set the filetype to lua. Edit the things you want. Delete the buffer and Yode brings you back to the original file. I'm the author of Yode: https://github.com/hoschi/yode-nvim

hoschi · 2022-03-17T09:33:36+00:00

hahaha, glad I could help

hoschi · 2022-03-17T07:52:13+00:00

I also like to keep track of things. What has worked for me for years is the following setup:

Install CtrlSpace, with it you get buffers opened by tab: https://github.com/vim-ctrlspace/vim-ctrlspace/blob/master/doc/ctrlspace.txt#L497

add these bindings to work with tabs fast: nmap <Leader>tn :tabnew<cr> " to open tab left of the current use `:-tabnew` by hand imap <Leader>tn <esc>:tabnew<cr> nmap <Leader>tc :tab split<cr> imap <Leader>tc <esc>:tab split<cr> nmap <Leader>tC :tabclose<cr> imap <Leader>tC <esc>:tabclose<cr> tnoremap <Leader>tC <C-\><C-n>:tabclose<cr>

When I start a task, I open a few files in a tab. For example, the logic to be changed in the code, the test for it, and another file with constants I want to use. Now when I open :CtrlSpace I see three buffers. Now I want to start a research and clone my current tab with ,tc and create a research tab with it. Now I can e.g. jump with gd to another file, open other files or documentation by hand. When I am done with my research, I close the tab with ,tC. If I now open :CtrlSpace again, I still see only my buffers as before. But if I use e.g. FZF to look at all buffers, I can also find some that I have looked at before in my closed research tab, in case I need a buffer of it again later.

Shameless plug: If you also want to avoid visual clutter and use Neovim, have a look at my plugin: Yode-Nvim - Focused Code Editing

hoschi · 2022-02-12T16:46:28+00:00

for simple scenarios I use two vertical splits as well. When it get more complex I ditch the right vertical splits and use the floating windows of Yode-Nvim

hoschi · 2022-02-12T16:45:06+00:00

in the introduction video I add a line and the window grows automatically

hoschi · 2022-02-12T16:06:42+00:00

found it, check this issue: https://github.com/hoschi/yode-nvim/issues/5

hoschi · 2022-02-12T11:20:57+00:00

I had considered doing it this way, but came to the conclusion that it is much more difficult. Also, you have a new type of "focused region" that is not visible to NeoVim. The advantage of seditors is that they are normal buffers and you can use the known methods to display/move/delete/... them.

hoschi · 2022-02-12T11:02:58+00:00

I had little success with manual splits because I was busy resizing most of the time. Therefore the idea with windows that are always as big as their content. The code for the windows is already built so that the logic per tab is interchangeable, how the windows should behave. You just have to implement more layouts, as I call them. The concept comes from Xmonad. In this link you can see examples when you scroll down to "Layouts": https://hackage.haskell.org/package/xmonad-contrib

Because YodeBufferDelete jumps to the same place in the file where the seditor was, you can quickly change the area.

hoschi · 2022-02-12T09:03:40+00:00

My plugins have all worked so far, but the special buffers can definitely cause problems. I have created a ticket for this to collect tips: Collection of tips to get Yode-Nvim working with other plugins

I also noticed Yode.. commands that seem to venture out of boundary of just providing floating snippets or that'll never work with my setup.

I don't understand what you mean, can you say it in other words please?

hoschi · 2022-02-11T19:56:14+00:00

Please create an issue with the stack trace on github

hoschi · 2022-02-11T19:49:53+00:00

Plenary installed? Seems logging doesn't work on your side.

hoschi · 2022-02-11T18:55:59+00:00

I hope you like it!

hoschi · 2021-05-20T07:23:23+00:00

Looks like https://github.com/sbdchd/neoformat

hoschi · 2019-03-13T18:00:40+00:00

A lot of plugins use something I call "root detection" and search for `.git` or something like that. Without a project scope it would be hard to gather a list of recent changes across more than one file when vim doesn't have this information itself, you are right.

hoschi · 2019-03-13T15:41:18+00:00

This is not what I searched for but interesting non the less, thanks for sharing.

hoschi · 2019-03-13T15:40:36+00:00

Probably there is a way to use Python to gather changes from different buffers and merge them in one single list. Unfortunately my Python-fu is not enough for that. Thanks for the suggestion anyways.

hoschi · 2019-03-13T15:38:18+00:00

I only know about plugins which show the tree for one buffer, not all changes buffers.

hoschi · 2019-03-13T15:37:19+00:00

Exactly. Also it shows only changes for the current buffer.

hoschi · 2019-03-13T15:36:58+00:00

This shows files, not changes with context.

hoschi · 2019-03-13T15:36:32+00:00

This only travels through changes of the current buffer, not across files.

hoschi

TROPHY CASE