Anthony Thyssen

Yes I believe we have noticed heartbeat not timing out for users that are coming via a VPN from home. Not really a major issue, as it will terminate (timeout)...

I have tested 4.10.0. Ran my heartbeat check and waited for it to time out. Same as before, heartbeat only restarted on editing a new file, or reloading browser tab....

Just tried version 4.12.0 I had a while a loop actively running on the a code-server shell command line, producing output, and the mouse moving in and out of the...

I used v4.13.0 heartbeat starts. I did a few things edits files, etc. then moved away. heartbeat stopped a few minutes later. This is fine... an expected... On editing a...

The last tests was while I was at work, so no VPN involved. Though there was still a nginx ingress proxy to the container running code-server. May be it is...

Okay the the problem persists, exactly as previously described. The heartbeat stops, and only restarts on editing a new file, or reloading the tab. No other actions seems to get...

> Run `autoreconf -fi` first. It'll generate `configure` script for you. Except that is NOT in the spec file, so the provided spec file does not build from this tar...

> You can probably accomplish this by sourcing this > > ```shell > _fzf_complete_host_notrigger() { FZF_COMPLETION_TRIGGER='' _fzf_host_completion; } > ``` > > somewhere, as described in https://github.com/junegunn/fzf/wiki/Examples-(completion)#bash-custom-trigger-less-completion Nice... didn't know...

Rather than use the the function `_known_hosts_fzf()` in the above script to replace `_known_hosts_real()` function, you can use it to set the completion for specific commands. This is actually what...

You may like to have a look at... https://github.com/junegunn/fzf/issues/2316 You can then DIY your own hostname completion handler, using fzf via normal BASH TAB hostname completion.