all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: xiliuya via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 62795@debbugs.gnu.org
Subject: bug#62795: 29.0.90; eglot: gdscript default port is 6005
Date: Sat, 15 Apr 2023 21:28:45 +0800	[thread overview]
Message-ID: <875y9x2qk7.fsf@aliyun.com> (raw)
In-Reply-To: <CALDnm53Q_nLet5qn47hKmXtUz3-SRm4_yCFxZF3DshQUtmwDFw@mail.gmail.com>


João Távora <joaotavora@gmail.com> writes:

> I see.  So it's not an inferior process to Emacs. Then
> maybe a function can be crafted in Elisp -- and housed
> in gdscript-mode -- that somehow discovers if the Godot
> Engine is running and finds the correct port.  Then
> gdscript-mode can add that function to eglot-server-programs.

Yeah, that's a great idea.
Execute shell command `ss -lnpt | grep godot | awk -F':' '{print $2}' | awk '{print $1}'`
Will output:

     6006
     6005

The default port 6006 is an LSP port.
The default port 6005 is the Debug Adapter port.

> And are you sure that port has never been 6008?  If
> that was just a mistake, then I think we should change,
> yes.  But please let's not change this back and forth
> every 3 months, or add alternatives for every positive
> integer.


I checked the historical submission of Godot and found that
the default LSP port has been changed from 6005 to 6008,
which was submitted in Dec 5, 2021:
https://github.com/godotengine/godot/commit/de7873c2d87c3ee8af8c27e35f49767fcc384e75


-- 
xiliuya :)





  reply	other threads:[~2023-04-15 13:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 10:33 bug#62795: 29.0.90; eglot: gdscript default port is 6005 xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-15  8:07 ` Eli Zaretskii
2023-04-15  8:17   ` João Távora
2023-04-15 12:19     ` xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-15 13:13       ` João Távora
2023-04-15 13:28         ` xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-04-15 14:04           ` xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-16  3:48         ` xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-16  5:49           ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-16  6:16             ` xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-16  7:36               ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-16  8:57                 ` xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-16 11:08             ` João Távora
2023-04-16 12:29               ` xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-17  7:33                 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-17  8:43                   ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-17 13:22                     ` xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-16 11:16             ` João Távora

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875y9x2qk7.fsf@aliyun.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=62795@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=xiliuya@aliyun.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.