Command line interface for performing Git hosting service operations.

This tool is a provider-independent version of Hub and Lab.

The current focus is implementing Gitlab functionalities (0.3.x series).

Everything is tracked in detail via issues and milestones.

The functionalities currently supported are:

• Github/Gitlab:
  • create label
  • list issues, labels, milestones, MR/PRs
  • merge MR/PR
  • open repository
• Github:
  • comment PR
  • create gist, issue, milestone, PR

Geet requires the API token environment variable to be set, eg:

export GITHUB_API_TOKEN=0123456789abcdef0123456789abcdef    # for GitHub
export GITLAB_API_TOKEN=0123456789abcd-ef0-1                # for GitLab

All the commands need to be run from the git repository.

Basic creation of an issue:

$ geet issue create

The default editor will be used for title/description:

Labels, milestone and assignees will be asked with menu selection:

Please select the label(s): (Use arrow keys, press Space to select and Enter to finish, and alphanumeric/underscore characters to filter)
‣ ⬡ bug
  ⬡ enhancement
  ⬡ not_an_issue
  ⬡ requires_design

Labels, milestone and assignees can be directly specified with the respective parameters:

$ geet issue create --labels bug,wip --assignees johncarmark --milestone 1.0

After creation, the issue page will be automatically opened in the default browser.

Basic creation of a PR:

$ geet pr create

The default editor will be used for title/description:

More advanced PR creation, with label and reviewers, assigned to self:

$ geet pr create --labels "code review" --reviewers kevin,tom,adrian

After creation, the issue page will be automatically opened in the default browser.

List the open issues, in default order (inverse creation date):

$ geet issue list
> 16. Implement issue opening (https://github.com/saveriomiroddi/geet/issues/16)
> 14. Update README (https://github.com/saveriomiroddi/geet/issues/14)
> 8. Implement milestones listing/show (https://github.com/saveriomiroddi/geet/issues/8)
> 4. Allow writing description in an editor (https://github.com/saveriomiroddi/geet/issues/4)
> 2. Support opening PR into other repositories (https://github.com/saveriomiroddi/geet/issues/2)

List the open PRs, in default order (inverse creation date):

$ geet pr list
> 21. Add PRs listing support (https://github.com/saveriomiroddi/geet/pull/21)

$ geet milestone list
> 9. 0.2.0
>   4. Allow writing description in an editor (https://github.com/saveriomiroddi/geet/issues/4)
> 6. 0.2.1
>   69. Display warning when some operations are performed on a forked repository (https://github.com/saveriomiroddi/geet/issues/69)
>   60. Update Create PR test suite; the UTs are not inspecting some of the changes (https://github.com/saveriomiroddi/geet/issues/60)
>   51. Services should take repository in the initializer (https://github.com/saveriomiroddi/geet/issues/51)
> 7. 0.2.2
>   43. PR Merging: upstream support (https://github.com/saveriomiroddi/geet/issues/43)
>   35. Improve design of repository-independent actions (https://github.com/saveriomiroddi/geet/issues/35)

$ geet label list
> - bug (#ee0701)
> - enhancement (#84b6eb)
> - technical_debt (#ee0701)
> - top_priority (#d93f0b)

Create a private gist:

$ geet gist create /path/to/myfile

Create a public gist, with description:

$ geet gist create --public /path/to/myfile 'Gist description'

Menus can be used for selecting attributes (labels, collaborators, milestones…).

This is an example of multiple choice selection:

Please select the label(s): (Use arrow keys, press Space to select and Enter to finish, and alphanumeric/underscore characters to filter)
‣ ⬡ bug
  ⬡ enhancement
  ⬡ not_an_issue
  ⬡ requires_design

Typing alphanumeric keys and underscore will enable filtering:

Please select the label(s): (Filter: "b")
‣ ⬡ bug
  ⬡ technical_debt

When a filter is active, use Backspace to cancel the last character, and Canc to reset it.

Display the help:

$ geet [command [subcommand]] --help

Examples:

$ geet --help
$ geet pr --help
$ geet pr create --help

Command line interface for performing Git hosting service operations.

This tool is a provider-independent version of Hub and Lab.

The current focus is implementing Gitlab functionalities (0.3.x series).

Everything is tracked in detail via issues and milestones.

The functionalities currently supported are:

• Github/Gitlab:
  • create label
  • list issues, labels, milestones, MR/PRs
  • merge MR/PR
  • open repository
• Github:
  • comment PR
  • create gist, issue, milestone, PR

Geet requires the API token environment variable to be set, eg:

export GITHUB_API_TOKEN=0123456789abcdef0123456789abcdef    # for GitHub
export GITLAB_API_TOKEN=0123456789abcd-ef0-1                # for GitLab

All the commands need to be run from the git repository.

Basic creation of an issue:

$ geet issue create

The default editor will be used for title/description:

Labels, milestone and assignees will be asked with menu selection:

Please select the label(s): (Use arrow keys, press Space to select and Enter to finish, and alphanumeric/underscore characters to filter)
‣ ⬡ bug
  ⬡ enhancement
  ⬡ not_an_issue
  ⬡ requires_design

Labels, milestone and assignees can be directly specified with the respective parameters:

$ geet issue create --labels bug,wip --assignees johncarmark --milestone 1.0

After creation, the issue page will be automatically opened in the default browser.

Basic creation of a PR:

$ geet pr create

The default editor will be used for title/description:

More advanced PR creation, with label and reviewers, assigned to self:

$ geet pr create --labels "code review" --reviewers kevin,tom,adrian

After creation, the issue page will be automatically opened in the default browser.

List the open issues, in default order (inverse creation date):

$ geet issue list
> 16. Implement issue opening (https://github.com/saveriomiroddi/geet/issues/16)
> 14. Update README (https://github.com/saveriomiroddi/geet/issues/14)
> 8. Implement milestones listing/show (https://github.com/saveriomiroddi/geet/issues/8)
> 4. Allow writing description in an editor (https://github.com/saveriomiroddi/geet/issues/4)
> 2. Support opening PR into other repositories (https://github.com/saveriomiroddi/geet/issues/2)

List the open PRs, in default order (inverse creation date):

$ geet pr list
> 21. Add PRs listing support (https://github.com/saveriomiroddi/geet/pull/21)

$ geet milestone list
> 9. 0.2.0
>   4. Allow writing description in an editor (https://github.com/saveriomiroddi/geet/issues/4)
> 6. 0.2.1
>   69. Display warning when some operations are performed on a forked repository (https://github.com/saveriomiroddi/geet/issues/69)
>   60. Update Create PR test suite; the UTs are not inspecting some of the changes (https://github.com/saveriomiroddi/geet/issues/60)
>   51. Services should take repository in the initializer (https://github.com/saveriomiroddi/geet/issues/51)
> 7. 0.2.2
>   43. PR Merging: upstream support (https://github.com/saveriomiroddi/geet/issues/43)
>   35. Improve design of repository-independent actions (https://github.com/saveriomiroddi/geet/issues/35)

$ geet label list
> - bug (#ee0701)
> - enhancement (#84b6eb)
> - technical_debt (#ee0701)
> - top_priority (#d93f0b)

Create a private gist:

$ geet gist create /path/to/myfile

Create a public gist, with description:

$ geet gist create --public /path/to/myfile 'Gist description'

Menus can be used for selecting attributes (labels, collaborators, milestones…).

This is an example of multiple choice selection:

Please select the label(s): (Use arrow keys, press Space to select and Enter to finish, and alphanumeric/underscore characters to filter)
‣ ⬡ bug
  ⬡ enhancement
  ⬡ not_an_issue
  ⬡ requires_design

Typing alphanumeric keys and underscore will enable filtering:

Please select the label(s): (Filter: "b")
‣ ⬡ bug
  ⬡ technical_debt

When a filter is active, use Backspace to cancel the last character, and Canc to reset it.

Display the help:

$ geet [command [subcommand]] --help

Examples:

$ geet --help
$ geet pr --help
$ geet pr create --help

• Python Version – 3.9.x
• Recommendation (Optional)
  • Create a virtual environment for python 3.9 incase you have a different version installed using the below command
    • conda create --name py39 python=3.9
• Install dependencies using the following command (Requirements.txt is in the root folder)
  • pip install -r requirements.txt
• Create a folder meta in the application root directory, This is where the indexes cached for quick queries!

• Run app.py
  – python3 app.py
  – Eg. python3 app.py test-data
• On querying, Application attempts to return top 10 relevant documents with their titles, filename, similarity score

Since the actual data is huge. I created a medium size version which contain 500 files. along with indexes cached.
Files in meta folder can be removed to reconstruct the indexes. If you attempt to create a new index with much bigger clinical trails data.
Use the link below to download the original dataset and delete the index files in meta/, so the index is re created.

1. Meta folder is already present in the folder. You could use the already constructed index of original set or recreate by not
   using the meta folder.
2. Original dataset (3095 files) – https://drive.google.com/drive/folders/1UaO7pIfw8eSMYnussKsNpG6yeT9UmCva?usp=sharing

• nltk
  • punkt
  • wordnet
  • stopwords
• pandas

• Tokenization
  • tags extracted from XML
    1. brief_title
    2. official_title
    3. brief_summary
    4. location_countries/country
    5. detailed_description
    6. Phase
    7. intervention/description
    8. intervention/intervention_type
    9. Condition
    10. Keyword
• Remove stop words
• Perform normalization (covid — covid19)

• inverted index
• Document id to document name index

• Save index for future use

• Ranked retrieval using tfidf for terms

https://clinicaltrials.gov/ct2/about-studies/glossary
https://clinicaltrials.gov/ct2/html/images/info/public.xsd
https://clinicaltrials.gov/ct2/results/map?cond=COVID-19&map=
http://www.trec-cds.org/2019.html#documents

• Python Version – 3.9.x
• Recommendation (Optional)
  • Create a virtual environment for python 3.9 incase you have a different version installed using the below command
    • conda create --name py39 python=3.9
• Install dependencies using the following command (Requirements.txt is in the root folder)
  • pip install -r requirements.txt
• Create a folder meta in the application root directory, This is where the indexes cached for quick queries!

• Run app.py
  – python3 app.py
  – Eg. python3 app.py test-data
• On querying, Application attempts to return top 10 relevant documents with their titles, filename, similarity score

Since the actual data is huge. I created a medium size version which contain 500 files. along with indexes cached.
Files in meta folder can be removed to reconstruct the indexes. If you attempt to create a new index with much bigger clinical trails data.
Use the link below to download the original dataset and delete the index files in meta/, so the index is re created.

1. Meta folder is already present in the folder. You could use the already constructed index of original set or recreate by not
   using the meta folder.
2. Original dataset (3095 files) – https://drive.google.com/drive/folders/1UaO7pIfw8eSMYnussKsNpG6yeT9UmCva?usp=sharing

• nltk
  • punkt
  • wordnet
  • stopwords
• pandas

• Tokenization
  • tags extracted from XML
    1. brief_title
    2. official_title
    3. brief_summary
    4. location_countries/country
    5. detailed_description
    6. Phase
    7. intervention/description
    8. intervention/intervention_type
    9. Condition
    10. Keyword
• Remove stop words
• Perform normalization (covid — covid19)

• inverted index
• Document id to document name index

• Save index for future use

• Ranked retrieval using tfidf for terms

https://clinicaltrials.gov/ct2/about-studies/glossary
https://clinicaltrials.gov/ct2/html/images/info/public.xsd
https://clinicaltrials.gov/ct2/results/map?cond=COVID-19&map=
http://www.trec-cds.org/2019.html#documents

This is a k6 extension using the
xk6 system.

To build a k6 binary with this extension, first ensure you have the prerequisites:

• Go toolchain
• Git

Then:

1. Install xk6:

go install go.k6.io/xk6/cmd/xk6@latest

2. Build the binary:

xk6 build --with github.com/grafana/xk6-exec@latest

To make development a little smoother, use the Makefile in the root folder. The default target will format your code, run tests, and create a k6 binary with your local code rather than from GitHub.

make

Once built, you can run your newly extended k6 using:

 ./k6 run examples/script.js 

Possible options

• dir specify working dir
• continue_on_error contintue script when return code is not zero
• include_stdout_on_error exposes stdout when return code is not zero
• combine_output combines stdout and error in output
• env specify enviroment variables

see examples/script.js for details

// script.js
import exec from 'k6/x/exec';

export default function () {
  console.log(exec.command("date"));
  console.log(exec.command("ls",["-a","-l"]));
}

Result output:

$ ./k6 run examples/script.js

          /\      |‾‾| /‾‾/   /‾‾/   
     /\  /  \     |  |/  /   /  /    
    /  \/    \    |     (   /   ‾‾\  
   /          \   |  |\  \ |  (‾)  | 
  / __________ \  |__| \__\ \_____/ .io

  execution: local
     script: examples/script.js
     output: -

  scenarios: (100.00%) 1 scenario, 1 max VUs, 10m30s max duration (incl. graceful stop):
           * default: 1 iterations for each of 1 VUs (maxDuration: 10m0s, gracefulStop: 30s)

INFO[0000] vie 29 ene 2021 12:53:28 CET                  source=console
INFO[0000] total 27040
drwxrwxr-x 6 dgzlopes dgzlopes     4096 ene 29 12:52 .
drwxrwxr-x 3 dgzlopes dgzlopes     4096 ene 29 12:46 ..
-rw-rw-r-- 1 dgzlopes dgzlopes     8399 ene 29 12:45 builder.go
-rw-rw-r-- 1 dgzlopes dgzlopes     1871 ene 29 12:45 builder_test.go
drwxrwxr-x 3 dgzlopes dgzlopes     4096 ene 29 12:45 cmd
-rw-rw-r-- 1 dgzlopes dgzlopes     6842 ene 29 12:45 environment.go
drwxrwxr-x 8 dgzlopes dgzlopes     4096 ene 29 12:45 .git
drwxrwxr-x 3 dgzlopes dgzlopes     4096 ene 29 12:45 .github
-rw-rw-r-- 1 dgzlopes dgzlopes      118 ene 29 12:45 .gitignore
-rw-rw-r-- 1 dgzlopes dgzlopes      923 ene 29 12:45 .golangci.yml
-rw-rw-r-- 1 dgzlopes dgzlopes       85 ene 29 12:45 go.mod
-rw-rw-r-- 1 dgzlopes dgzlopes     1020 ene 29 12:45 .goreleaser.yml
-rw-rw-r-- 1 dgzlopes dgzlopes      183 ene 29 12:45 go.sum
-rwxrwxr-x 1 dgzlopes dgzlopes 27598848 ene 29 12:52 k6
-rw-rw-r-- 1 dgzlopes dgzlopes    11357 ene 29 12:45 LICENSE
-rw-rw-r-- 1 dgzlopes dgzlopes     1805 ene 29 12:45 platforms.go
-rw-rw-r-- 1 dgzlopes dgzlopes     3370 ene 29 12:45 README.md
drwxrwxr-x 3 dgzlopes dgzlopes     4096 ene 29 12:45 vendor  source=console

running (00m00.0s), 0/1 VUs, 1 complete and 0 interrupted iterations
default ✓ [======================================] 1 VUs  00m00.0s/10m0s  1/1 iters, 1 per VU

     data_received........: 0 B 0 B/s
     data_sent............: 0 B 0 B/s
     iteration_duration...: avg=2.3ms min=2.3ms med=2.3ms max=2.3ms p(90)=2.3ms p(95)=2.3ms
     iterations...........: 1   55.736622/s

ArbreBinUI est un script python permettant l’affichage de manière graphique (librairie Tkinter) d’un arbre binaire.

Ce script fait appel à un autre script permettant la saisie en console d’un arbre binaire ainsi que sa représentation par une classe Arbre. Le script saisie.py à été développé par Pierre Lartigau en 2016.

Pour utiliser correctement ce script vous avez besoin de

• Python 2.*
• Tkinter (Librairie de base, elle est normalement installée avec Python)

Pour tester ArbreBinUI, vous pouvez lancer directement le fichier affiche_arbre.py qui vous demandera 3 arbres:

$ python affiche_arbre.py

Pour l’utiliser dans des projets:

# -*- coding: utf-8 -*-
from affiche_arbre import TreeDrawer
from saisie import *

treeDrawer = TreeDrawer() # Il est important de créer cet objet avant toute tentative de dessin

arbre = entrerArbre(1)

# Mes opérations sur l'arbre ici..

treeDrawer.dessiner_arbre(arbre) # On dessine ici notre arbre, on peut l'appeler autant que l'on veut.
# Attention cette méthode est asynchrone, si vous voulez attendre je conseil de mettre une pause comme une attente clavier !

# Éventuellement d'autres opérations..

# On attend la fermeture des fenêtres avant de quitter le programme.
# Cette méthode est obligatoire avant la fin du programme.
treeDrawer.wait()

• Gestion multi-fenêtre pour chaque dessin
• Passage de la fonction de dessin de synchrone à asynchrone

• Changement de librairie, passage de Pillow à Tkinter
• Amélioration de la taille de la fenêtre en fonction de la hauteur de l’arbre
• Meilleur fonctionnement multi OS

• La taille de l’image est générée en fonction de la hauteur de l’arbre
• L’image peut être sauvegardée si demandée

• Affichage d’arbres binaires
• TODO: Générer la taille de l’image en fonction de la hauteur de l’arbre

Note: Game is undergoing redesign at the moment.

To see source as it was in ep 4 “Creating Minecraft”, view here:

https://github.com/Hopson97/HopsonCraft/tree/e803ca5fbf51df134cfa7e87c14275c6c73fce8e

When I made this, I was highly inexperienced at programming (Less than 2 years), and the code is mostly pretty messy and game crashes a lot.

I have kept it on my GitHub for historical reasons, seeing as I have videos about this on my YouTube channel.

This game has gone through major rewrites and refactors overtime.

To see the source code as it was in episodes 1, 2 and 3 of “Creating Minecraft in C++/ OpenGL” videos, look at an older commit here:

https://github.com/Hopson97/HopsonCraft/tree/90a5d596d07dfe71b5dbf47ec76c0b0802ec9dfa

The project requires these libraries: SFML (minimum 2.4), GLEW 2.0+ (OpenGL 3.3+), and OpenGL Maths Library (GLM).

Compile using compiler flags:

Windows -> -std=c++14 -O3 -s -lglew32s -lglu32 -lopengl32 -lsfml-graphics -lsfml-audio -lsfml-system -lsfml-window

Linux -> -std=c++14 -O3 -s -lGLEW -lGLU -lGL -lsfml-graphics -lsfml-audio -lsfml-system -lsfml-window

All the libraries for Linux (At least, on Ubuntu) can be installed with

sudo apt-get install libsfml-dev

sudo apt-get install libglew-dev

sudo apt-get install libglm-dev

An easy way to contribute is to look for the ///@TODO parts in the code. please actually test before doing a pull request.

You can view the code style in contributing.md

You can view useful implementation details in implementation.md

Also, checkout the TRELLO! https://trello.com/b/P8ZbobQH/hopsoncraft

Simple Minecraft clone written using C++.

Matthew Hopson, https://github.com/Hopson97/

Matthew Hopson, https://github.com/Hopson97/

Matthew Hopson, https://github.com/Hopson97/

Anton Golov, https://github.com/jesyspa

Zoltan Fazekas, https://github.com/zfazek

This project was bootstrapped with Create React App.

In the project directory, you can run:

Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.

The page will reload when you make changes.
You may also see any lint errors in the console.

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify
“# TheConspiracyWorld”

This workspace folder works on Mac, Windows, and Linux. Both debugging and compiling work properly. Make sure you read the prerequisite steps below before trying to use this thing. To use this workspace folder open it as your highest folder in Visual Studio Code. To add a program to this workspace folder make a subfolder to put its source files in. After finishing the prerequisite setup stuff things should magically work. In the future when there is more time I will make a few similar workspace folders, one for C++ and one that uses makefiles.

• How to download:

• To Build: Select any source file in the program folder of the program you want to debug and then hit the keys CTRL + SHIFT + B.

• To Debug: Place a breakpoint were you want the debugger to start debugging and then hit the f5 key. To place a breakpoint hold you mouse to the left of the line number for the line you want to start debugging on. If your program takes command line arguments hardcode those args into the args section in the launch.json file. If you want to find where your program crashes run the debugger without placing a breakpoint.

• To Run a Program: After successfully building there should be an executable with the same name as the folder it was compiled placed in the folder that is was compiled in. On Mac or Linux this executable would be called program_folder_name, on Windows program_folder_name.exe. To run the executable right-click on it and pick the option “Open in Integrated Terminal”. Next if you are on Mac or linux run ./program_folder_name, on Windows .\program_folder_name.exe.

For this workspace folder to work YOU MUST HAVE gcc & gdb on your path.

You must also have the C/C++ VScode extension from microsoft installed. Uninstall any other extension having to do with C/C++ as these extensions might fight with the one from Microsoft, exp the extension from Austin, or that extension called “CodeRunner”…

You must also have your Workspace folder structured to have a separate sub-folder for each program you want to compile. Each program-folder can only have one source file with a main() function.

• Windows:

  • Download mingw-w64 gcc/gdb from http://mingw-w64.org/doku.php/download/mingw-builds
  • Next run the installer and install mingw-w64 at the default location or some location you won’t forget.
  • Next add mingw-w64 to the PATH.
  • For a detail guild on this: (read steps 3 and 4)https://code.visualstudio.com/docs/cpp/config-mingw

  After putting mingw-w64 on the path restart VScode so that it gets an updated PATH.

• Linux & Windows Subsystem for Linux:

  • Debain based install:

    sudo apt-get update

    sudo apt-get install gcc gdb make

  • Arch based install:

    sudo pacman -Syu

    sudo pacman -Sy gcc gdb make

  After installing gcc & gdb restart VScode so that it gets an updated PATH.

• Mac:

  • To install: xcode-select --install
  • After installing restart VScode so that it gets an updated PATH, you might need to re-login.
  • The xcode-select --install command actually installs clang & lldb, not gcc & gdb. On mac if you have clang installed the gcc command runs clang, don’t worry about this since the two compilers for your proposes are probably the same. If you really want gcc this video shows you how to get it: https://www.youtube.com/watch?v=0z-fCNNqfEg

To check if you successfully got gcc & gdb on your path run gcc -v and gdb -v

GCC from some sources will not work on windows. If you have problems with gcc not accepting some args such as -Og and *.c, uninstall your trash gcc and install mingw-w64-builds gcc.

It is possible to get a very nice setup where you can easily change between compiling and debugging on native windows and WSL. This setup is the most optimal for windows users since it’s very useful to have easy access to some very powerful Unix exclusive tools. I do not feel like typing up the instructions to get this setup working, but hopefully will at some point. In general the additional things you have to do are, install WSL, install the WSL extension, click on the green button in the lower left then select Remote-WSL: Reopen folder in WSL, then install the C/C++ extension a second time while VScode is in WSL mode.

• Do not have more than one source file with a main() function in the same program folder.
• Do not put this workspace folder inside a workspace folder, in other words do not have this workspace folder be a subfolder. This workspace folder must be the highest folder open in VScode for it to work.
• A program folder should be a subfolder of this workspace folder, do not nest program folders as this might cause activity that might confuse you.
• Do everything specified in the prerequisite setup setups…
• If stuff is not working before complaining or giving up double check and make sure you have the CodeRunner extension not installed.
• On Linux and probably Mac you can not run programs on a normal USB stick without doing some odd stuff. In other words if you have this workspace folder on a USB stick take it off before using it with Linux or Mac.

• On Mac sometimes the compiler puts the executable in an odd spot thus causing the debugger problems.
• On mac the error and warning highlighting can sometimes be of, mac uses clang to compile. As a temp fix in the tasks.json file change line 141 to be “$clang” from “$gcc”, line 141 specifies the problem matcher.
• TDM-gcc gcc does not work and will give the error gcc: error: *.c: Invalid argument , mingw-w64-builds gcc

If you find an issues that can be fixed or improved submit a pull request