Christoph Thiede
Christoph Thiede
Given the following SmalltalkInTex syntax: ```latex \begin{ExecuteSmalltalkScript} Transcript showln: 'foo ba' \end{ExecuteSmalltalkScript} ``` The compiled builder method will look like the following ```smalltalk foo Transcript showln: 'foo ba' ``` However,...
Minor, but still not perfect: The naming format for the (generated) PNG files is not yet consistent. Some are named `camelCase.png`, others `PascalCase.png`, and some even `Hyphen-case.png`. Would be nice...
 What would be the correct way to fix that? `\raisebox` seems suboptimal to me.
I would not be aware of any other relevant WebBrowser implementation in Squeak, so why don't set Scamper als default? The default setting is used in TextURL, for example.
**Steps to reproduce:** - Login with a password that contains a quote (`"`) **Expected result:** Login successfull (provided that you entered your real password). **Actual result:** Error: is not IMAP...
- `IMAPClient-Core` depends on `IMAPClient-UI`, which is generally a bad symptom:  Maybe this would be even worth a regression test (see also `PackageDependencyTest`). - `IMAPClient-Core` and `IMAPClient-Protocol` depend reciprocally...
This extension method shadows a method in the Trunk: https://github.com/hpi-swa-teaching/IMAPClient/blob/5437c6e6c9194ec38035562a12a9ae8d4b075764/packages/IMAPClient-UI.package/TextMorphForEditView.extension/instance/keyStroke..st This is usually a bad practice for several reasons, including but not limited to: - If the method gets updated...
Will provide steps to reproduce as soon as I'm able to reproduce it
I do know how to reproduce this exactly, but very often, after browsing my emails for a while, I received an infinite cascade of ConnectionClosed errors. The client should make...
Messages containing, for example, umlauts, will be displayed incorrectly in the client. Instead of `ö`, I would rather see `&APY-` at the moment.