Update tex on Mac:
tlmgr needs sudo on OSX

Da wir entschieden haben Trello und Slack nicht mehr zu benutzen, sollten die nützlichen Sachen von Trello hier oder auf der Mailingliste gepostet werden.

The windows installer now has many more steps, including choosing the default editor, line endings, ssl library, ....

On the mainpage is still a link to the old install page under the section „Vorbereitung“.

Install manual for OSX:
When using El Capitan the Locale is not set correctly.
This will cause python to raise "unknown locale errors".
Add:

export LANG=en_US.UTF-8
export LC_ALL=en_US.UTF-8

to ~/.profile to resolve.
en_US must be set to the correct system encoding , eg. de_DE for german.

UPDATE 30.09.16
I googled a bit more and this is always given as the solution.
Not sure, how this is handled in e.g. Ubuntu

Could be wrong in the installation instructions.

I saw #158 and wondered if toolbox-workshop as a submodule would make this whole upload/update materials easier (or even more automatic with some CI)

I found these two Plugins:
TexLab LSP-Client
latex-syntax

The first one is a client to the TexLab LSP-Server.
On a first glance, the completion seems to work quite well.
The second one seems to be designed to work well with the first one, but is not necessary.

See, #103 (comment)

• Windows
• macOS
• Linux

There were changes after the Workshop 2018 in the windows subsystem.
I tried the installation guide recently and everything worked.

If something misbehaves check the two links below, send to me by Lars from E2
https://www.omgubuntu.co.uk/2019/07/ubuntu-wsl-metapackage-install
https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack

On the installation page we are recommending to source anaconda in the bashrc. Do we really want to recommend that? This can be potentially problematic since the python version of cmake does not always function like normal cmake which can lead to major headaches when one tries to compile a cmake based project. At least when you don't know what anaconda is doing behind your back. And there is no real way (i think) to get rid of this cmake version (by redirecting to another cmake executable) while staying in the anaconda environment, without "breaking" some python packages.
Example:

➜  ~ which cmake   
/usr/bin/cmake
➜  ~ conda activate 
(base) ➜  ~ which cmake
/home/vukan/.local/anaconda3/bin/cmake

Since we got very unspecified questions about problems with the installation,
i suggest we could write a page about how to ask when there are problems.

On this page we could collect fixes to known bugs and a little instruction on E-Mail Requests.
A bulletpoint list may be the best idea, like

• write to this e mail address
• name your OS
• which programm causes the problem
• add the error code or a screenshot

Just recently I added the following condition to my wsl .bashrc:

if ! xhost >& /dev/null ; then 
echo -e "\033[31;1mDisplay ($DISPLAY) not found\033[0m: You might want to turn on the XServer" ; 
fi

If the XServer is not running it will show as the first line in every new terminal:

The red/bold formatting is just my personal preference.

Should we add this to the Win10-instructions?

The html versions of the python notebooks dont contain the graphics.
Especially the numpy graphics would be usefull to have.

Maybe we should put those into the materials section on the website as well.

This issue is meant to be a heads up, more than anything.
This is not a complicated fix, I am going to take a look at it today or tomorrow.

Triggert by the email to the emaillist today I discovered the following:

Windows seems to put the Desktop-Folder into a OneDrive-Folder.
I am not sure if this is opt-in or opt-out but I assume the latter.

This is a problem for the Windows10 instructions since you have to navigate to
the Desktop at some point.

The testing of the installation is basically the same on all systems, only opening a terminal is different.

Did anyone check the windows 11 beta yet?
For users of a Mac M1 we should also include a working manual.
Probably the installation manual will change a bit on the new windows system.
I suppose until September a couple of people will have an updated windows system.

If we should ever decide to change from the WSL1 to the WSL2, we have to fix the DISPLAY config.

Currently we use

echo "export DISPLAY=localhost:0.0" >> ~/.bashrc

to setup the connection to the XDisplay.
Since the WSL2 <superficial knowledge> has its own kernel and is not just a layer of some kind it has its own IP address and
</superficial knowledge> we cant use localhost anymore.

I found this neat grep command to get the IP address from a file in the WSL2 filesystem:

grep -oP "(?<=nameserver ).+" /etc/resolv.conf

This localhost in the above settings can be substituted by this grep command to fix the problem:

echo "export DISPLAY='$(grep -oP "(?<=nameserver ).+" /etc/resolv.conf):0.0'" >> ~/.bashrc

I had to look up this grep command so here is a small summary of the full story if someone is interested as well:

• -o shows only the matched characters and not the whole line
• -P switches to perl-regex
• (?<=nameserver ).+ is a regex called positve lookbehind (only available with perl-regex)
  it matches anything (.+: atleast on character) after an occurance of nameserver without matching it as well
• /etc/resolve.conf contains the IP address, the line of interest contains nameserver 123.45.678.9

⇒ the result of the grep command is 123.45.678.9

This looks really ugly:

Im Moment sieht CHS2 gut aus, da ist in den zwei Wochen nichts.

Ich versuche mal, Prof. Tolan darum zu bitten, den Raum für uns zu reservieren.

https://toolbox.pep-dortmund.org/about.html

My suggestion:

• Christian Beckmann
• Sebastian Lütge
• Maximilian Nöthe
• Joshua Luckey

Although, I really did not organize very much, so I do not insist on staying on this list,
if we want to leave it at three people.

Since 2020 is happening when installing tex the Path includes a texlive/2020/bin and the filename in Anaconda changes from Anaconda3-2019.07-Linux to Anaconda3-2020.02-Linux.
Also the tex settings require an init-usertree command in the beginning.
Furthermore the Biber installation does not seem to work. After reinstalling everything and changing path as mentioned Biber does not start.
Thanks for help!

website isn't working at the moment.
Getting "403 Forbidden" for non pdf files (html and zip).

Zeitgleich zum aktuell angesetzten Termin findet für die Medizinphysiker das Klinikpraktikum statt (15. bis 25.09). Da der Termin vom kooperierenden Krankenhaus vorgegeben ist, können wir daran auch nichts drehen. Haben wir eine reelle Chance, unseren Termin zu verschieben?

I am currently setting up my Toolbox User, when testing the python installation I stumbled upon this error resulting from using %matplotlib in the ipython console:

(base) toolbox@TP-L460:~$ ipython
Python 3.7.3 (default, Mar 27 2019, 22:11:17) 
Type 'copyright', 'credits' or 'license' for more information
IPython 7.6.1 -- An enhanced Interactive Python. Type '?' for help.

In [1]: %matplotlib                                                                           
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-1-a49a4afc47c5> in <module>
----> 1 get_ipython().run_line_magic('matplotlib', '')

~/.local/anaconda3/lib/python3.7/site-packages/IPython/core/interactiveshell.py in run_line_magic(self, magic_name, line, _stack_depth)
   2311                 kwargs['local_ns'] = sys._getframe(stack_depth).f_locals
   2312             with self.builtin_trap:
-> 2313                 result = fn(*args, **kwargs)
   2314             return result
   2315 

</home/toolbox/.local/anaconda3/lib/python3.7/site-packages/decorator.py:decorator-gen-108> in matplotlib(self, line)

~/.local/anaconda3/lib/python3.7/site-packages/IPython/core/magic.py in <lambda>(f, *a, **k)
    185     # but it's overkill for just that one bit of state.
    186     def magic_deco(arg):
--> 187         call = lambda f, *a, **k: f(*a, **k)
    188 
    189         if callable(arg):

~/.local/anaconda3/lib/python3.7/site-packages/IPython/core/magics/pylab.py in matplotlib(self, line)
     97             print("Available matplotlib backends: %s" % backends_list)
     98         else:
---> 99             gui, backend = self.shell.enable_matplotlib(args.gui.lower())
    100             self._show_matplotlib_backend(args.gui, backend)
    101 

AttributeError: 'NoneType' object has no attribute 'lower'

In [2]: 

Can anybody reproduce this?

A solution to this, is to specify the name of the backend manually, e.g.
%matplotlib qt and %matplotlib tk worked for me.

add instructions to the windows installation for choosing wsl in Codium
with screenshots

I think the section would be a perfect use case for http://getbootstrap.com/javascript/#collapse. However, it would require JavaScript. What do you think?

pacman -S winpty

und eventuell

alias ipython="winpty ipython"

in die bashrc packen

We had one system where localhost:0.0 was not working, and found that:

export DISPLAY=$(route.exe print | grep 0.0.0.0 | head -1 | awk '{print $4}'):0.0

works

remove/change link for wsl overview
or
make clear that in general no external links are needed

use options to reduce the size

The image to be displayed beneath the line

Wir brauchen TeXworks nicht:

is missing.

ConEmu build: 180626 x64
OS version: Windows 10 x64
Used shell version: CMD

Python 2.7's pip fails when CMD runs under ConEmu:

C:\Users\zeev.kotzer>pip install Kivy --upgrade
Collecting Kivy
Downloading https://files.pythonhosted.org/packages/f7/98/d74b2c19eb28dcf36450c979c19676741891ca8
a54af0a7069e445552663/Kivy-1.10.1-cp27-cp27m-win_amd64.whl (4.3MB)
1% |Could not install packages due to an EnvironmentError: [Errno 42] Illegal byte sequence

This can be worked around by adding "--progress-bar off", but inconvenient, and problematic for novice users ...

Students switched to different versions in the guide and got stuck because things didn't work.
Maybe we should split the guide or use colors to indicate which version we are looking at.

Default profile can be choosen in Settings via Dropdown list

Switch VS Code in for Atom

Trying to install the dependencies you get the following error for the package nodejs-legacy:

❯ sudo apt install nodejs-legacy                                         (base) 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package nodejs-legacy is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  nodejs:i386 nodejs

E: Package 'nodejs-legacy' has no installation candidate

Installing the given replacement packages nodejs:i386 nodejs seems to work.
Yet I'm not sure for what purpose this dependency is needed and what to look for. 🤔

The „How to change the PATH on Windows“-BulletList here does not display right in the browser (atleast for me). On Github it displays as intended, probably needs an empty line before the start of the list.
I will fix it tomorrow if I find the time to do it. 😉

• Mac: Atom
• Linux: Atom?

Mir stinkts gerade gewaltig.

1. Bevor man alles über den Haufen wirft, spricht man sich ab!
2. Die Änderungen widersprechen dem, was im PeP Vorstand von uns zum LaTeX Kurs besprochen worden ist:
   • minimalistische Präambel
   • einfache, für jeden nachvollziehbare Makefiles
   • nur die nötigen Grundlagen auf Basis moderner Pakete, dann den Umgang üben.
3. Mir missfällt der arrogante und geringschätzende Tonfall der sich durch die Folien zieht.
4. Mindestens 1/3 der neuen Folien sind für einen Grundlagenkurs unnötig, unübersichtlich, verschreckend oder absoluter Overkill. Oft mehreres von den genannten auf einmal.
5. Die LuaLaTeX Doku empfiehlt Polyglossia statt Babel
6. Die Schrift ist viel zu klein.
7. Niemand braucht diese N Flussdiagramme zu den verschiedenen Programmteilen.

Ich schlage vor, dass sich hierzu erstmal alle Beteiligten zu Wort melden. So geht's nicht weiter. Wir widersprechen mit unseren FIles dem, was wir beschlossen hatten den Leuten beizubringen.

In section install/osx:

after anaconda install, the terminal must be restarted or the .bashrc sourced. otherwise anaconda/bin is not in path and pip won't be found.

Change:
Falls der Workshop digital stattfindet, werden wir Zoom (und Discord) verwenden.

To:
Der Workshop wird digital stattfinden, für die Durchführung werden wir Zoom (und Discord) verwenden.

Do we want to somehow normalise command names?
On Linux (and probably OS X), Anaconda installs python, python2 and python2.7 links.
For 3, python, python3 and python3.3 are installed.
On Windows, only python exists, both for 2 and 3.
On Arch, python is python3, and all of python2, python2.7, python3 and python3.3 exist.

ipython is always only ipython in Anaconda. It is ipython2 in Arch.

My preference would be to have python2 (and optionally python3) existing everywhere. This is also standardised as PEP 394.

This can be accomplished using the mklink command on Windows.

http://toolbox.pep-dortmund.org/links.html#editoren
List of editors features (only!) emacs?

The integrated terminal of vscode does something to the PATH variable, with the effect of placing anaconda at the end of the path. Therefore the python version used by the terminal wont be the anaconda one.

There is a workaround, taken from this github issue:
This entry has to be added to the settings.json file:

"terminal.integrated.env.osx": {
		"PATH": ""
}

~/.pam_environment can be used to set environment variables for the full user session, not just the shell like when setting them in .bashrc or .zshrc.

This will e.g. help in letting VS Code find LaTeX exectables.

Was genau bringt uns das, außer eine unklare Rechtslage?

Some students didn't know, that commands must be entered by pressing "enter".