... | ... | @@ -6,6 +6,9 @@ The typical most basic user-interface to WSL is a **terminal-window** which runs |
|
|
|
|
|
For using and programming with Dumux we keep with that setting. But the Linux-distribution like Ubuntu inside the WSL has to be equipped with all the tools to fetch and compile the code and you will likely need install some **native Windows applications** to edit or browsing the code, debug or handle the produced data of simulations.
|
|
|
|
|
|
We try to avoid to install graphical/gui linux applications inside the WSL, although possible to run those, one would often install easily several Gigabytes of libraries for one linux application.
|
|
|
Also startup times and main memory usage (RAM) for such applications can with limited resources become horrible.
|
|
|
|
|
|
You also have to be familiar with methods how to access files within the WSL from Windows, and sometimes also the other way around, i.e. accessing your windows drives from the Linux commandline in the terminal-window.
|
|
|
|
|
|
Usually one first checks out the code with tools like **git** directly or indirectly started with python-scripts like **installdumux.py** and for other parts with **installexternal.py**. You find hints to that when follwing [getting started](https://dumux.org/gettingstarted/) or the [DuMux-course](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux-course/-/blob/master/README.md).
|
... | ... | @@ -177,7 +180,7 @@ show now multiple instances of your shell. |
|
|
|
|
|
Klick on the logo of your terminal-window to get a menu. Click then on `Properties`. Under `Options` you can then enable `Use Ctrl+Shift+C/V as Copy/Paste`. With `Ctrl-Shift+C` you can copy something to clipboard and with `Ctrl+Shift+V` you can paste.
|
|
|
|
|
|
When you mark something with your mouse with hitting the key `<enter>` the marked text get copied also to your clipboard this might be shorter than `Ctrl+Shift+c`.
|
|
|
When you mark something with your mouse with hitting the key `<enter>` the marked text get copied also to your clipboard this might be shorter than `Ctrl+Shift+C`.
|
|
|
|
|
|
Klick then to `Font` in the logo-menu to make your settings for font. You might repeat the settings also for PowerShell instances.
|
|
|
|
... | ... | @@ -210,7 +213,33 @@ Another choice would be to install an editor inside Windows which runs there nat |
|
|
|
|
|
Or you can also use [Notepad++](https://en.wikipedia.org/wiki/Notepad%2B%2B) from the Windows store or from [this site](https://notepad-plus-plus.org/) or something else.
|
|
|
|
|
|
## Starting Windows native tools from within the WSL
|
|
|
## Starting Windows native tools from within the WSL
|
|
|
|
|
|
A link to kate might be in your start menu. I found out that it points to
|
|
|
seen from WSL /mnt/c/Users/david/AppData/Local/Kate/bin/kate.exe (note david is my username).
|
|
|
|
|
|
Thus I put an alias in my startup file for the bash which runs inside terminal-window:
|
|
|
I added the line at the end of the file `~/.bashrc` i.e. .bashrc in my home-directory:
|
|
|
|
|
|
```
|
|
|
alias kate="/mnt/c/Users/$USER/AppData/Local/Kate/bin/kate.exe"
|
|
|
```
|
|
|
|
|
|
With that defined I was able to start kate directly from the terminal-window in a way something like that:
|
|
|
```
|
|
|
kate filename.cc &
|
|
|
```
|
|
|
|
|
|
Similiar defined an alias for paraview (read about installation below) in my .bashrc within WSL:
|
|
|
|
|
|
```
|
|
|
alias paraview='/mnt/c/Program Files/Paraview 5.10.1-Windows-Python3.9-msvc2017-AMD64/bin/paraview.exe'
|
|
|
```
|
|
|
|
|
|
Please adapt that to your local installation. This made me possible easily to open result files from dumux within the terminal like:
|
|
|
```
|
|
|
paraview myresultfile.plt &
|
|
|
```
|
|
|
|
|
|
## Visualization or Plotting Tools
|
|
|
|
... | ... | |