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 v4 0/1] contrib/vscode/: debugging with VS Code and gdb
Date: Thu, 7 Apr 2022 22:40:00 +0200 [thread overview]
Message-ID: <20220407204001.112287-1-cogoni.guillaume@gmail.com> (raw)
In-Reply-To: <xmqqmtgwu9n7.fsf@gitster.g>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=[UTF-8], Size: 3948 bytes --]
Derrick Stolee <derrickstolee@github.com> writes:
> Cogoni: In conclusion, I think that if you remove the change to
> MyFirstContribution.txt, then your patch can be merged pretty
> quickly (probably, that's not my decision).
> I expect this discussion about a potential "WorkingOnGit" file to continue,
> but if it come to fruition, your section on VS Code would be welcome.
Yes, I got the same conclusion, from the discussion between you and
Ævar Arnfjörð Bjarmason. So, I remove the change to MyFirstContribution.txt.
It sounds like the best plan for now.
But, I agreed on some point with Ævar Arnfjörð Bjarmason, we have to try
to recommending also free alternatives.
And, yes, a new file is the best option. So, I keep my change somewhere, and
I will come again with a new patch but not in its thread because it seems to
be out of the scope now.
> Sounds like a good thing to have, but would there truly be hints and
> tips so specific to this project, I have to wonder. I do not think
> we are in the business of making "how to hack on and debug a project
> code that is mostly written in C and whose history is managed in
> Git" tutorial for each IDE, so I am not sure how well it would fly
> (not opposed to, but skeptical).
I think, it can help a newcomer, but not necessarily people with a
lot of experience on various projects. But, we can give it a try and
see where it goes.
Thanks everyone for your reviews, your ideas and help.
COGONI Guillaume (1):
contrib/vscode/: debugging with VS Code and gdb
contrib/vscode/README.md | 6 +++++-
contrib/vscode/init.sh | 1 -
2 files changed, 5 insertions(+), 2 deletions(-)
Diff-intervalle vs v3 :
1: 0600ab64f8 ! 1: 59de991a2d contrib/vscode/: debugging with VS Code and gdb
@@ Commit message
Add useful links in contrib/vscode/README.md to help the user to
configure VS Code and how to use the debugging feature.
- Add a mention to the README and the init.sh in Documentation/
- MyFirstContribution.txt and a part to convince a newcomer that VS Code
- can be helpful.
-
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.
- If you're using `git send-email`, you can use it the same way as before, but you
- should generate your diffs from `<topic>..<mybranch>` and base your work on
- `<topic>` instead of `master`.
-+
-+[[Bonus-useful-tools]]
-+== Bonus - useful tools
-+
-+=== 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.
-+
-+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
[Windows](https://code.visualstudio.com/docs/setup/windows),
--
2.25.1
next prev parent reply other threads:[~2022-04-07 20:46 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 ` [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 ` COGONI Guillaume [this message]
2022-04-07 20:40 ` [PATCH v4 " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220407204001.112287-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.
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 NNTP newsgroup(s).