kangwonlee / config-windows Goto Github PK

• Add following to ~/.bashrc

git log --oneline --graph --all --decorate

• os.path.dirname or os.path.basename instead of os.path.split when possible
• os.path.split(__file__)[0] → os.path.dirname()
• os.path.split(__file__)[-1] → os.path.basename()

• Similar to .travis.yml?

• https://travis-ci.org/kangwonlee/config-windows/builds/543269803
• unable to import numpy
• was the configuration not successful?

• add followings to ~/.bashrc

git config --global --unset user.email
git config --global --unset user.name

• Anaconda 2018.12 python may experience problem importing pylab
• In the qtconsole (also available from Anaconda Navigator), import pylab works.
• After creating a new environment, import pylab works in python.

conda env export --file <.yml> --name <env>
conda env create --name <new env> --file <.yml>
conda activate <new env>

#7 error log

• It may just work now!

• https://github.com/kangwonlee/kpu-b105-issue-tracker/issues/25
• git-for-windows/git#2130
• petervanderdoes/gitflow-avh#393
• petervanderdoes/gitflow-avh#393 (comment) recommends running following commands

git config gitflow.prefix.hotfix "hotfix/"
git config gitflow.prefix.feature "feature/"
git config gitflow.prefix.bugfix "bugfix/"
git config gitflow.prefix.release "release/"
git config gitflow.prefix.support "support/"

• Running the commands above with --global adds following section in the ~/.gitconfig file

[gitflow "prefix"]
    hotfix="hotfix/"
    feature="feature/"
    bugfix="bugfix/"
    release="release/"
    hotfix="hotfix/"
    support="support/"

• gitflow 1.12.3 could resolve this issue. Until then, consider adding above section to ~/.gitconfig

• ~/.bashrc may have incorrect PATH such that ls or vi may not work
• Expected case

export PATH=<path 0>:<path 1>:<path 2>:$PATH

• Problem case 1

export PATH=<path 0>:<path 1>:<path 2>;$PATH

• Problem case 2

export PATH=<path 0>:<path 1>:<path 2>:$PAT

• A separate subtree repo

Configurations

• SW download
• SW install
• configuration after installation

Instructions

• bash
• git
• vi
• vscode

consider adding test + CI

• To implement uniform exercise environment
• What if to install containers to lab PCs and push using kubernetes?
• CI says that its Windows support Docker

Why?

• If python on PATH, current implementation does not update path
• However $CONDA/Library/bin needs update anyways

Plan

• Read .bashrc
• Locate ^export PATH=.* line
• Build a list of folders in $PATH
• See if desired paths such as $CONDA or $CONDA/Library/bin in the path
• If missing, add the desired paths
• Replace export PATH= line
• Update .bashrc

• As of 749c408, choco seemed having difficulties installing a different version of git
• As of 7764435, after changing to git.install, still the test could not finish

• Otherwise, in debug mode, input() would accept the activation command as first input

Expected environment

• has Anaconda3
• has MS VS Code
• has git-bash
• PowerShell.exe as the integrated terminal of MS VS Code
• python mostly not on path
• conda may not be active but not a must
• not certain if code is on path

Desired environment

• has Anaconda3
• has MS VS Code
• has git-bash
• git-bash as the (integrated) terminal of MS VS Code
• python on path in git-bash
• no conda message
• code on path in git-bash

For Windows

• Anaconda a85864c
• VS Code a346574
• VS Code Extension 6ead50a

Travis-CI

Anaconda

• For Travis-CI, Chocolatey has Anaconda
• Possible commandline:
  

choco install anaconda3 --params '"/JustMe /AddToPath /D:c:\MyTools"'

VS Code

• Chocolatey has vscode, too.

choco install vscode

VS Code Extension

• VS Code has commandline interface for extensions

git for Windows

choco install git.install --params "/GitAndUnixToolsOnPath /NoGitLfs /SChannel /NoAutoCrlf"