Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A few issues when no network filename is given #719

Open
isty2e opened this issue Jun 8, 2020 · 1 comment
Open

A few issues when no network filename is given #719

isty2e opened this issue Jun 8, 2020 · 1 comment

Comments

@isty2e
Copy link

isty2e commented Jun 8, 2020

Other than local engines, I sometimes connect to engines on cloud instances via ssh, with commands stored in script files. In that case, the network file name is missing since the command in config.txt is something like ../gtp_katago.sh, and this causes two problems:

  1. In menu-engines, since the names of engines are automatically fixed to the network file name, it is hard to distinguish between them. Supporting aliases for engines will resolve this problem.
  2. Settings pane won't open.
@kaorahi
Copy link
Contributor

kaorahi commented Oct 21, 2020

#787 may solve 1. I cannot reproduce 2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants