Valentin Lorentz bee98f6711 Conditional: Do not use noReply() after running the command.
As the command already calls reply() or noReply(), calling noReply()
there had disastrous effects:

* if reply() was called, noReply() erases the argument
* if noReply() was called, calling noReply() a second time erases **the next argument** (because the current argument was already erased).

This was 'caused' by the change of behavior of noReply() in 543edccd416f5a45b2a2ee2cc6218264d220bc49.
2017-10-26 09:55:52 +02:00
..
2015-08-22 14:36:00 +00:00
2015-08-11 16:50:23 +02:00
2015-08-11 16:50:23 +02:00
2015-08-11 16:50:23 +02:00
2015-08-11 16:50:23 +02:00
2015-08-11 16:50:23 +02:00
2015-08-11 16:50:23 +02:00
2015-12-04 13:39:28 +01:00
2015-08-11 16:50:23 +02:00
2016-10-31 19:06:35 +01:00
2015-08-11 16:50:23 +02:00
2015-08-11 16:50:23 +02:00
2015-08-11 16:50:23 +02:00
2015-08-11 16:50:23 +02:00
2015-08-11 16:50:23 +02:00
2017-10-21 17:11:21 +02:00
2015-09-15 21:00:31 +02:00
2015-08-11 16:50:23 +02:00
2015-08-11 16:50:23 +02:00
2016-02-07 09:44:08 +01:00