Marco De Donno

I will give it a try.

Some thoughts: 1. If implemented, how useful will the 'track' option be? 2. Is it a good idea to stuff the command the `s:branch_actions` variable, or should we add an...

> > If implemented, how useful will the 'track' option be? > > I think if we find a way to make this work for all cases that option could...

Base upon the failed test of the commit 15a35b508d4b9c381679c45d412a1b371caa42b6, I dont know how to allows the users to use the `inset_new_bullet()` function from the outside. I think we should eigher...

Thanks for the feedback! I will check that out and make the modifications. I will force push the new branch here, so we can keep the discussion if it's ok...

> really happy to see this work being done. any updates @dkarter or @mdedonno1337? Thanks for the interest! Still on my todo list... If you have any feedback, let us...

yeaa, impossible as well for me with clang13, and not trivial to port the patches here. I compile with clang14, seems to work, dont know why.

I will consolidate the docker-related files in one directory. All stages in one directory is OK for you? Also the bash files related to docker?

This isse seems to be the same as the one mentionned here @kramred in https://github.com/Eloston/ungoogled-chromium/pull/1850#issuecomment-1057811420 . The fix in https://github.com/kramred/ungoogled-chromium-portablelinux/commit/a84a62f24b1884ac44c41e4aeeb398d1009fcca7 seems to work. A PR done with the mentionned commit...

Correct. This is related to the issues regarding clang13; the patch is not ported at the moment in this repository. I compile with clang14, seems to work fine (**https://github.com/mdedonno1337/ungoogled-chromium-portablelinux/tree/llvm14**)