Cannot type in a server name in the Remote SSH text box

[eldar]

Lapce Version

lapce-0.4.0+0ddc216

System information

Fedora 40 KDE Plasma Desktop

Describe the bug

I am trying to connect to a remote Linux server by clicking on "Connect to SSH host" which opens a text box on top of the editor, however I cannot type any text in the said textbox - it remains empty.

Additional information

Here is a screenshot demonstrating the issue

[dzhou121]

Can you please try to disable "custom titlebar" in settings.

[eldar]

I disabled custom title bar, restarted Lapce which made the OS title bar to appear, but I still could not type into the remote SSH text box.

[simoniz0r]

This is the same as #2857. Certain input boxes do not take focus correctly. If you click on something like the button to collapse Open Editors, you should be able to type in there. Same sort of thing happens for the commit input box, the command palette, and a few other things.

[amrit-citrusleaf]

Bump. The same issue is happening on macOS 14.3.1.
Not sure but looks like Lapce is unable to read the ~/.ssh/config file.

[panekj]

Bump. The same issue is happening on macOS 14.3.1.
Not sure but looks like Lapce is unable to read the ~/.ssh/config file.

Lapce does not read ~/.ssh/config at all, also please don't post comments like that since they ping people unnecessarily

[amrit-citrusleaf]

@panekj - I tried contributing with the little knowledge I had. I really like Lapce and want it to grow. I will refrain myself from using it further and contributing with my "useless comments". :)
Apologies for "unnecessarily pinging people" 🙏🏼

[eldar]

The documentation https://docs.lapce.dev/get-started/remote-development says that Lapce uses ~/.ssh/config. I managed to get the textbox into focus, but I am confused how to specify credentials for a remote server. I have remote servers configured in the said file including proxy jumps - it would be easier to be able to reuse those settings.

[amrit-citrusleaf]

Bump. The same issue is happening on macOS 14.3.1.
Not sure but looks like Lapce is unable to read the ~/.ssh/config file.

Lapce does not read ~/.ssh/config at all, also please don't post comments like that since they ping people unnecessarily

@panekj - update the documentation if Lapce does not use ~/.ssh/config file. https://docs.lapce.dev/get-started/remote-development

[panekj]

The documentation docs.lapce.dev/get-started/remote-development says that Lapce uses ~/.ssh/config.

The documentation states that you can use hostname you configured in ~/.ssh/config. Lapce doesn't use that config, it's not going to show you anything from that file. Lapce will "use" the hostname, because it's invoking ssh command which reads t that file.

I am confused how to specify credentials for a remote server

You can type in palette just the name or <user>@<hostname> to connect

it would be easier to be able to reuse those settings.

It will use SSH config to connect since it's using OpenSSH you have installed on your machine.

[amrit-citrusleaf]

The documentation docs.lapce.dev/get-started/remote-development says that Lapce uses ~/.ssh/config.

The documentation states that you can use hostname you configured in ~/.ssh/config. Lapce doesn't use that config, it's not going to show you anything from that file. Lapce will "use" the hostname, because it's invoking ssh command which reads t that file.

Got it. So essentially it still "reads" the config file, but only the host name part.
So the real issue is that the host names are not appearing in the UI.

[panekj]

So the real issue is that the host names are not appearing in the UI.

There was never any intention for reading SSH config into Lapce or having it display anything more than recent connections (hosts connected to recently), so it's not an issue.
The real issue is that titlebar steals focus from palette input when clicked on.

[panekj]

I see that the screenshot in the documentation being right under statement of SSH config, can confuse people as to what exactly is happening and I didn't noticed that mistake, this should be updated shortly.
We also had placeholder value when palette input is empty when using SSH connection, but it got lost in UI refactoring.

[panekj]

Duplicate of #2857