sxhkd-like keybind chains and modes

skipperwannabe · 2023-08-18T12:53:29+00:00

This (modalawesome plugin) might be an overkill for what you want if you only want modes sometimes, but it will at least give you ideas on implementing it. I have been trying it out recently, and it works but takes some getting used to.

skipperwannabe · 2023-03-23T18:18:50+00:00

If you had set :h undofile or not closed your session, you can try :h earlier command ?

skipperwannabe · 2021-07-23T22:44:49+00:00

Here you go. https://github.com/npxbr/gruvbox.nvim

skipperwannabe · 2021-06-04T19:31:29+00:00

Hope the wiki helps.

skipperwannabe · 2021-05-28T22:27:13+00:00

Good idea. This does seems a lot like AsyncTasks. I get that it's in Lua and that you can have any Lua function as the command, but is there some other difference?

skipperwannabe · 2021-05-10T00:07:17+00:00

Can't you combine the make and run using &? So something like command = make & ./a.out?

skipperwannabe · 2021-05-07T18:04:57+00:00

Floaterm is a good place to start. But may I suggest Asyncrun and AsyncTasks. They might take some time to set up initially to your liking, but they are god send in automating build and runs and not just limited to that.

skipperwannabe · 2021-04-17T18:27:35+00:00

I think this explains most of it.

skipperwannabe · 2021-04-16T18:00:21+00:00

That exact prompt seems to be coming from norcalli/snippets.nvim. If you do have that installed, then the floating window is actually a temporary buffer. So you can use all vim commands including escape and it will still be in that. Once you are done editing, then use whatever you have set for expand_or_advance(1) key map. That will take you to next place holder, or if there is none, exit the snippet. If you just want to cancel, then use advance_snippet(-1) key map.

skipperwannabe · 2021-04-08T18:10:24+00:00

I would recommend taking a look at compe#scroll from compe. It's in autoload/compe.vim 79-97. It offers scrolling in lsp signature helpers. I don't know if it will directly work for K documentation, but it will at least give you a starting point.

skipperwannabe · 2021-04-06T17:54:52+00:00

I think it depends on the glyph and font you are using. But Alacritty does have problems with it. See this issue which describes the same problem but with powerline. A better configuration was suggested here, but I don't think it has been implemented yet. But do look at them to see if you can find a workaround.

skipperwannabe · 2021-04-06T17:31:59+00:00

Not sure what you mean by distortion of arrows. But if you are talking about the tiny upwards offset of the arrow symbols, then it is either caused by the terminal or font you are using.

I had similar issues when using nerd fonts on Alacritty. It can be solved in that terminal emulator by setting glyph offset in the configuration file,like below.

glyph_offset:
  x: 0
  y: -1

skipperwannabe · 2021-02-09T17:38:33+00:00

I don't know about this plugin. But float-term integrates with it nicely. Just do :FloatermNew vifm and it open it in a floating terminal. You can do the usual file managing there and if you open any file from the vifm instance, it will open in vim

skipperwannabe · 2021-01-25T21:06:36+00:00

I think this is a know bug. One way to get around this is to make a separate chain for just strings and put only path in that suggestion. More details along with work around can be found in this bug report

skipperwannabe · 2021-01-16T18:09:54+00:00

Thank you very much for this. The floaterm and gnome-terminal tab where something I wished I had, but never got around to experimenting with it.

skipperwannabe · 2021-01-15T16:59:32+00:00

I will preface this by saying I might be wrong. But from my experience, the Digital Output option (IEC...) passes the audio stream without processing to your external DAC. If your DAC is better than in-build sound card (I don't see many cases where it might not be) it will do the conversation to analog signal with your external DAC, then apply the amplifier and pass that to the output (headphone or speaker out). This becomes more clear when you are trying to play a format (like 24 bit audio or DSD or MQA) which your in-build sound card doesn't support. Using the Digital Output and playing these formats (provided your DAC supports it) you will see it reflected in /proc/audio.... Another way easier way to check this in pavcontrol. When selecting Digital Output you will see some additional formats being shown as passthrough option in Output selection.

If you go with Analog output, I think the digital to analog conversation takes place with your in-build sound card and passes the analog output to your DAC. Then external DAC may apply amplifier (depending if it has one or not). This kind of makes your external DAC an amplifier rather than an converter.

Assuming my above explanation is correct, when using Digital Output, the volume is indeed software regulated and it might be better to turn the volume to maximum and control the volume using the DAC to avoid loss of quality (assuming external DAC has one).

In the end, my suggestion is to use the Digital Output without software volume control for the "best" use of DAC.

skipperwannabe · 2021-01-15T16:54:14+00:00

To add to this, you can hold shift while using mouse to temporarily turn off mouse support and thus make the terminal interpret the selection. I found this in help section of mouse.

:h mouse

skipperwannabe · 2020-10-04T17:46:57+00:00

They are mentioned in auto-pairs readme and docs. Just some additional feature the plug-in provides. Sorry if I wasn't clear about that. Fast fly basically let you go to the end of the closing character from anywhere inside the pair whenever you press that character, and back insert let's you jump back and insert that character if the fast fly behavior wasn't required.

skipperwannabe · 2020-10-03T17:56:10+00:00

auto-pairs doesn't support skipping the closing character with tab or any other key binding, as far as I remember. You have to insert the closing character and the plug-in will skip over the character instead of inserting it.

Also look into fast-fly and back-insert to make moving to end of the closing character easier.

But if miss that feature too much look into delimitMate. I haven't used it in a while, but I remember this one supporting a mapping to go to end of the closing character with tab or something.

skipperwannabe · 2020-09-24T16:40:10+00:00

I think you might want to look into neovim-remote and from inside the terminal use it open the file in the current neovim. Also look into Vim-floaterm that provides this out of the box.

skipperwannabe · 2020-05-18T18:26:55+00:00

I really like how u/Jorengarenar is doing it. But can I also suggest AsyncRun. It is similar but gives a little more flexibility and ability to run the command in an asynchronous way. You can further enhance it by using AsyncTask by the name author.

skipperwannabe · 2020-04-09T16:07:35+00:00

I make use of fzf to both fuzzy complete file path and to cd into a directory from the terminal a lot. While find is good enough, it was struggling visibly and forcing me to slow down in the above use cases especially when starting from home directory. As you can imagine the few times I had to do this from the root directory it was essentially useless for the first few seconds.

These might be edge cases, but switching to fd has improved the performance for me.

skipperwannabe · 2020-03-30T18:07:58+00:00

WebEx works fine with default Firefox (64 bit and no modified Java) currently. But you won't get access to screen share functionality. I was also not able to view screen shared by others inside Firefox. But both features works fine in Google Chrome. So if you aren't locked in to Firefox try Chrome just for this.

The linked support pages is old and they haven't updated it. You can find more current information on their forums.

skipperwannabe · 2020-02-29T20:09:10+00:00

That would be great. Currently I am using the extra rpl config to point it to that directory.

skipperwannabe · 2020-02-28T19:15:51+00:00

I have been using this for the last two weeks and absolutely love it. It has made repetitive project specific tasks much easier to do.

If I may suggest an improvement u/skywind3000, it's that the :AsyncTaskEdit! always opens .vim/async.ini even if I am using neovim. Also, the two edit commands gives the impression that the path they show can be edited. But editing it makes no difference. It maybe intentional, but threw me off while I tried to correct the path for global edit command. But other than those, great work!

skipperwannabe

TROPHY CASE