git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Bressat <git.jonathan.bressat@gmail.com>
To: Derrick Stolee <derrickstolee@github.com>
Cc: Matthieu Moy <Matthieu.Moy@univ-lyon1.fr>,
	"git@vger.kernel.org" <git@vger.kernel.org>,
	Cogoni Guillaume <cogoni.guillaume@gmail.com>
Subject: Re: contrib/vscode/: debugging with vscode and gdb
Date: Sat, 26 Mar 2022 15:11:07 +0100	[thread overview]
Message-ID: <CANteD_yZ8de2i54EUWW=d6eVzpiKm5NNHGVEKrXOmo5KXnXUVQ@mail.gmail.com> (raw)
In-Reply-To: <c1f255d7-6637-b6ac-0a64-1f64404a6f6c@github.com>

On 3/25/2022 2:27 PM, Matthieu Moy wrote:

> I couldn't understand what exactly the option was supposed to do. If I
> understand correctly, it should launch another window to show the git
> program output, but I don't know which window actually (xterm?
> x-terminal-emulator? a terminal program that isn't installed on my system?).

In VS Code settings, it seems to be x-terminal-emulator.


On 3/25/2022 8:01 PM, Derrick Stolee <derrickstolee@github.com> wrote :
> >> - "externalConsole": true,
> >> + "externalConsole": false,
> I'd actually remove the line completely, to mean "let VSCode decide what to do", i.e. either VSCode's default, or the user's configuration ("launch" section in settings.json, see e.g. https://code.visualstudio.com/docs/getstarted/settings ). If some user has a > non-broken externalConsole: true VSCode and likes this behavior, then the best place to configure it is in a user-wide config file IHMO.
>
> I confirmed that deleting the line works just fine.

Yes, we agree with both of you, remove the line completly is better
because it let the user choices his preferences.
And it also work for us.

> Reported-by: Jonathan Bressat <git.jonathan.bressat@gmail.com>
> Reported-by: Cogoni Guillaume <cogoni.guillaume@gmail.com>
> Helped-by: Matthieu Moy <Matthieu.Moy@univ-lyon1.fr>
> Signed-off-by: Derrick Stolee <derrickstolee@github.com>
> ---
> contrib/vscode/init.sh | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/contrib/vscode/init.sh b/contrib/vscode/init.sh
> index 27de94994b5..f139fd86444 100755
> --- a/contrib/vscode/init.sh
> +++ b/contrib/vscode/init.sh
> @@ -271,7 +271,6 @@ cat >.vscode/launch.json.new <<EOF ||
> "stopAtEntry": false,
> "cwd": "\${workspaceFolder}",
> "environment": [],
> - "externalConsole": true,
> "MIMode": "gdb",
> "miDebuggerPath": "$GDBPATH",
> "setupCommands": [
> --
> 2.35.1.138.gfc5de29e9e6
>
>

https://code.visualstudio.com/docs/editor/debugging
https://code.visualstudio.com/docs/getstarted/settings
Maybe, It would be nice to add these two links in
contrib/vscode/readme.md, this may be relevant to
help new users that want to use vscode debugger. And add some explanations
like "How to use it".

Except that, your patch sounds good for us.

Thanks,

Guillaume and Jonathan.

  reply	other threads:[~2022-03-26 14:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24  8:16 contrib/vscode/: debugging with vscode and gdb Jonathan Bressat
2022-03-25 13:19 ` Derrick Stolee
     [not found] ` <2a7eecb4a0b247ef8f855f1c4fb5d510@SAMBXP02.univ-lyon1.fr>
2022-03-25 18:27   ` Matthieu Moy
2022-03-25 19:01     ` Derrick Stolee
2022-03-26 14:11       ` Jonathan Bressat [this message]
2022-04-03 20:18         ` Guillaume Cogoni
     [not found]         ` <7b139f2c480e4ebc8dc6615b44cd5f24@SAMBXP02.univ-lyon1.fr>
2022-04-05  9:43           ` Matthieu Moy
2022-04-05 22:45             ` [PATCH V1 0/1] contrib/vscode/: debugging with VS Code " COGONI Guillaume
2022-04-05 22:45               ` [PATCH V1 1/1] " COGONI Guillaume
2022-04-06  8:47                 ` Ævar Arnfjörð Bjarmason
2022-04-06 11:59                 ` Matthieu Moy
2022-04-06 13:35                 ` Matthieu Moy
2022-04-06 15:18                   ` [PATCH v2 0/1] " COGONI Guillaume
2022-04-06 15:18                     ` [PATCH v2 1/1] " COGONI Guillaume
2022-04-06 18:03                       ` Derrick Stolee
2022-04-06 20:23                         ` Junio C Hamano
2022-04-06 23:39                           ` [PATCH v3 0/1] " COGONI Guillaume
2022-04-06 23:39                             ` [PATCH v3 1/1] " COGONI Guillaume
2022-04-07 11:17                               ` Ævar Arnfjörð Bjarmason
2022-04-07 13:09                                 ` Derrick Stolee
2022-04-07 16:43                                   ` Junio C Hamano
2022-04-07 20:40                                     ` [PATCH v4 0/1] " COGONI Guillaume
2022-04-07 20:40                                       ` [PATCH v4 1/1] " COGONI Guillaume
     [not found]                 ` <66f08cb2e81647e29a080af05d7c867e@SAMBXP02.univ-lyon1.fr>
2022-04-07  8:59                   ` [PATCH V1 " Matthieu Moy

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to='CANteD_yZ8de2i54EUWW=d6eVzpiKm5NNHGVEKrXOmo5KXnXUVQ@mail.gmail.com' \
    --to=git.jonathan.bressat@gmail.com \
    --cc=Matthieu.Moy@univ-lyon1.fr \
    --cc=cogoni.guillaume@gmail.com \
    --cc=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    /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 public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).