Add sudo apt-get install texlive-science to latex installation.

[a-t-0]

      <div class="snippet-clipboard-content position-relative"><pre><code>\usepackage[ruled,vlined,linesnumbered]{algorithm2e}

  <svg aria-hidden="true" viewBox="0 0 16 16" version="1.1" data-view-component="true" height="16" width="16" class="octicon octicon-check js-clipboard-check-icon color-text-success d-none m-2">
<path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 010 1.06l-7.25 7.25a.75.75 0 01-1.06 0L2.22 9.28a.75.75 0 011.06-1.06L6 10.94l6.72-6.72a.75.75 0 011.06 0z"></path>

[mohitsaxenaknoldus]

Where is the default latex installation?

[a-t-0]

Thank you for asking for clarification! With the default latex installation I meant the script that installs latex in this productivity setup. The file that manages this installation is located in: https://github.com/HiveMinds/Productivity-setup/blob/main/src/apt_texlive_xetex.sh

That file in turn calls sub-scripts that execute separated functions. In this case the managing script calls:

declare -a arr=("apt_0_update"
                "apt_1_upgrade"
                "apt_9_install_texlive_xetex"
                )

So I think it would be nice to add a function to apt_9_install_texlive_xetex, (or to rename it to apt_9_1_install_texlive_xetexand to create a new file namedapt_9_2_install_texlive_science` and to include that command in there.

It would be nice to also include a test that tests that apt_9_2_install_texlive_science file.

However, currently I feel it would be more valuable to focus on quality than on new features. My bottleneck in increasing the code quality of all my projects is currently in: https://github.com/Simple-Setup/Self-host-GitLab-Server-and-Runner-CI/issues/27 The GitLab CI works now on my device, and it automatically runs CI on a single repository. I still need to:

• [ ] make a function that runs it over all repositories of a user,
• [ ] Ensure it works on arbitrary computes. (In essence ensure it does not rely on the specific ssh-keys and credentials I have

In the meantime @rashim30 is working at applying Google Shell Style guide compliance on src/helper_gitlab_modify.sh and I hope to soon join @rashim30 on working on Google Shell Style guide compliance on the other files. Once that CI works, it will be able to verify that applying the Google Shell Style guide compliance to other repositories such as these, do not break the code. And I hope it allows me to implement quality checks such as code coverage and shellcheck compliance.

So if you happen to like nitpicking it would be wonderful to see the Google Shell Style guide compliance being applied to that self-hosted GitLab-CI deployment repository. I do acknowledge that is is nicer to work on the things you pick yourself, so If you feel like tackling this latex thingy, please feel free, either way your effort is greatly appreciated!

[mohitsaxenaknoldus]

Thank you for asking for clarification! With the default latex installation I meant the script that installs latex in this productivity setup. The file that manages this installation is located in: https://github.com/HiveMinds/Productivity-setup/blob/main/src/apt_texlive_xetex.sh

That file in turn calls sub-scripts that execute separated functions. In this case the managing script calls:

declare -a arr=("apt_0_update"
                "apt_1_upgrade"
                "apt_9_install_texlive_xetex"
                )

So I think it would be nice to add a function to apt_9_install_texlive_xetex, (or to rename it to apt_9_1_install_texlive_xetexand to create a new file namedapt_9_2_install_texlive_science` and to include that command in there.

It would be nice to also include a test that tests that apt_9_2_install_texlive_science file.

However, currently I feel it would be more valuable to focus on quality than on new features. My bottleneck in increasing the code quality of all my projects is currently in: Simple-Setup/Self-host-GitLab-Server-and-Runner-CI#27 The GitLab CI works now on my device, and it automatically runs CI on a single repository. I still need to:

• [ ] make a function that runs it over all repositories of a user,
• [ ] Ensure it works on arbitrary computes. (In essence ensure it does not rely on the specific ssh-keys and credentials I have

In the meantime @rashim30 is working at applying Google Shell Style guide compliance on src/helper_gitlab_modify.sh and I hope to soon join @rashim30 on working on Google Shell Style guide compliance on the other files. Once that CI works, it will be able to verify that applying the Google Shell Style guide compliance to other repositories such as these, do not break the code. And I hope it allows me to implement quality checks such as code coverage and shellcheck compliance.

So if you happen to like nitpicking it would be wonderful to see the Google Shell Style guide compliance being applied to that self-hosted GitLab-CI deployment repository. I do acknowledge that is is nicer to work on the things you pick yourself, so If you feel like tackling this latex thingy, please feel free, either way your effort is greatly appreciated!

Ok! Thanks for the clarification on the situation! In that case, let's keep this issue aside for now and let me help you with the Google Shell Style changes on that repo. See you there!