git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: COGONI Guillaume <cogoni.guillaume@gmail.com>
To: gitster@pobox.com
Cc: Matthieu.Moy@univ-lyon1.fr, avarab@gmail.com,
	cogoni.guillaume@gmail.com, derrickstolee@github.com,
	git.jonathan.bressat@gmail.com, git@vger.kernel.org
Subject: [PATCH v3 0/1] contrib/vscode/: debugging with VS Code and gdb
Date: Thu,  7 Apr 2022 01:39:45 +0200	[thread overview]
Message-ID: <20220406233946.45778-1-cogoni.guillaume@gmail.com> (raw)
In-Reply-To: <xmqqbkxex8oy.fsf@gitster.g>

On 4/6/2022 18:03 PM, Derrick Stolee wrote:

> Sorry for not getting to this in v1.

No problem, I take this opportunity to get a better view of the review 
process.

> Thanks for working on this!

Thanks for your help and reviewing.


COGONI Guillaume (1):
  contrib/vscode/: debugging with VS Code and gdb

 Documentation/MyFirstContribution.txt | 20 ++++++++++++++++++++
 contrib/vscode/README.md              |  6 +++++-
 contrib/vscode/init.sh                |  1 -
 3 files changed, 25 insertions(+), 2 deletions(-)

Diff-intervalle between v2 and v3 :
1:  367a478855 ! 1:  0600ab64f8 contrib/vscode/: debugging with VS Code and gdb
@@ Commit message
     MyFirstContribution.txt and a part to convince a newcomer that VS Code
     can be helpful.
     
-    Signed-off-by: COGONI Guillaume <cogoni.guillaume@gmail.com>
-    Co-authored-by: BRESSAT Jonathan <git.jonathan.bressat@gmail.com>
     Helped-by: Matthieu Moy <Matthieu.Moy@univ-lyon1.fr>
     Helped-by: Derrick Stolee <derrickstolee@github.com>
+    Co-authored-by: BRESSAT Jonathan <git.jonathan.bressat@gmail.com>
+    Signed-off-by: COGONI Guillaume <cogoni.guillaume@gmail.com>
     
     ## Documentation/MyFirstContribution.txt ##
     @@ Documentation/MyFirstContribution.txt: against the appropriate GitGitGadget/Git branch.
@@ Documentation/MyFirstContribution.txt: against the appropriate GitGitGadget/Git
+[[Bonus-useful-tools]]
+== Bonus - useful tools
+
-+=== VS Code
+=== Visual Studio Code (VS Code)
+
+The contrib/vscode/init.sh script creates configuration files that enable
+several valuable VS Code features. See contrib/vscode/README.md for more
+information on using the script.
+
+In particular, this script enables using the VS Code visual debugger, including
+setting breakpoints, logpoints, conditional breakpoints in the editor.
+In addition, it includes the ability to see the call stack, the line of code that
+is executing and more. It is possible to visualize the variables and their values
+and change them during execution.
+
-A script that creates the configuration files is available in contrib/vscode/init.sh. Useful links
-and explanation of how to use the script are available in contrib/vscode/README.md.
-Using the integrate debugger can be particularly helpful to understand how Git works internally.
-It can be used to isolate some parts of code, with this you may be able to ask more precises
-question when you are stuck. (See getting-help sections).
- \ No newline at end of file
+In sum, using the built-in debugger can be particularly helpful to understand
+how Git works internally.
+It can be used to isolate certain parts of code, with this you may be able to ask
+more precises question when you are stuck. (See getting-help sections).
     
     ## contrib/vscode/README.md ##
     @@ contrib/vscode/README.md: code editor which runs on your desktop and is available for
-- 
2.25.1


  reply	other threads:[~2022-04-06 23:40 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
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                           ` COGONI Guillaume [this message]
2022-04-06 23:39                             ` [PATCH v3 " 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=20220406233946.45778-1-cogoni.guillaume@gmail.com \
    --to=cogoni.guillaume@gmail.com \
    --cc=Matthieu.Moy@univ-lyon1.fr \
    --cc=avarab@gmail.com \
    --cc=derrickstolee@github.com \
    --cc=git.jonathan.bressat@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 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).