A simple way to compile your latex files without installing a latex-distribution is the usage of a docker-container. Thanks to https://github.com/blang/latex-docker it is easier than ever.
Within your directory with your
docker run --rm -i --user="$(id -u):$(id -g)" --net=none -v "$PWD":/data blang/latex xelatex article.tex
The current directory is mounted into the container and thus the latex executable within the container can access the source files (
xelatex article.tex) and the results are placed in the current directory too.
Thanks to https://github.com/djmaze/tiddlywiki-docker it is easy to launch a TiddlyWiki as nodejs-server from a docker image. Here is my setup, which simplifies the workflow by some bash-aliases.
# /Users/MyUserName/wikipath defines the mounted wiki directory
alias starttiddly="docker run -d --name tiddlycontainer -p 127.0.0.1:10000:8080 -v /Users/MyUserName/wikipath:/var/lib/tiddlywiki mazzolino/tiddlywiki"
alias stoptiddly="docker container stop tiddlycontainer && docker container rm tiddlycontainer"
- Start a bash-terminal and invoke
starttiddly to start the server
- Open your browser at http://localhost:10000 and work with tiddlywiki (the default login is user/wiki)
- After usage shutdown the container by invoking
Update: Of course you can also use
docker run -rm...to remove the container after running. This will shorten the stoptiddly-script.
Based on the post even fixed-width columns can be aligned.
% Centered fixed-width column
% Right-aligned fixed-width column
Ein etwas langer Text, der sicherlich umbrochen wird & a\\
oder kurz & b\\
Back in my NetBeans times I wrote several articles (1, 2) about using Zeroturnarounds JRebel to develop NetBeans plugins faster by not restarting nor reloading the whole target-platform. JRebel is a Java agent, so it can be used with nearly every Java-based application. Even for developing IDEA plugins. And here is how you do it:
- Buy a JRebel license or get a free one for your open-source plugin at myRebel
- Install the JRebel plugin for IDEA from the plugin manager (for bundling JRebel, a configuration UI and debugging support)
- Activate the plugin using the license from step 1
- Update the your Run- or Debug configuration with the Java agent configuration – based on the standard documentation)
- Run / debug your plugin using the configuration created above – JRebel should show its banner and an IDEA instance should load
- Edit your Java sources as normal and when you want to get the changes reloaded then compile the project/all the changed files (thus the sources are compiled into class-files and JRebel can pick up the changes)
- Reinvoke your plugins actions (or what ever) in the target platform – your changes should be picked up
Note 1 Not all changes will be picked up. JRebel does not have yet official support for this usage scenario. Especially changes in the plugin.xml won’t be picked up. But within existing or new Java classes you can code and refactor as much as you like!
Note 2 If you are on Mac OS consider to install JRebel separately. I had issues to set the Java agent with the bundled JRebel from the JRebel IDE plugin. Do you see the culprit in
-agentpath:/Users/markiewb/Library/Application Support/IntelliJIdea2017.2/jr-ide-idea/lib/jrebel6/lib/libjrebel64.dylib? The whitespace!
Note 3 Of course this also works when you write plugins for the other Java based IntelliJ platform IDEs like WebStorm, PHPStorm and so on.
Within the last two days I wrote a new plugin, which allows you to jump faster between files of GWT services.
Using IDEAs “Related symbols” action you can jump from the async method in the interface to its implementation and vice-versa – all based on filename conventions and it is nice example of a GotoRelatedProvider.
Here you jump between files:
Here you jump between methods of files:
This plugin requires the community edition of IntelliJ IDEA.
The most important part is the binding of the plugin to a Maven phase.