diff options
| author | Michele Calgaro <michele.calgaro@yahoo.it> | 2020-02-24 14:33:07 +0900 |
|---|---|---|
| committer | Michele Calgaro <michele.calgaro@yahoo.it> | 2020-02-24 14:33:07 +0900 |
| commit | 7fea3c42ee6179edaa3e9f36c794540ae73fcc95 (patch) | |
| tree | 4cea28ad693ec218f0c17b4702fe6b01cb2fa79e /BUGS | |
| parent | 70194b269e22711c3bbbc18d339b69aab028371e (diff) | |
| download | tdedocker-7fea3c42ee6179edaa3e9f36c794540ae73fcc95.tar.gz tdedocker-7fea3c42ee6179edaa3e9f36c794540ae73fcc95.zip | |
Completed kdocker -> tdedocker renaming effort.
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'BUGS')
| -rw-r--r-- | BUGS | 20 |
1 files changed, 10 insertions, 10 deletions
@@ -1,12 +1,12 @@ Known issues ------------ -1. Error messages are not transmitted from the previous instance of KDocker to -the latest instance. So, if you already have KDocker running and you start -another instance of KDocker saying "kdocker blah", you wont receive any error +1. Error messages are not transmitted from the previous instance of TDEDocker to +the latest instance. So, if you already have TDEDocker running and you start +another instance of TDEDocker saying "tdedocker blah", you wont receive any error message. -2. Problem with relative paths if new instance of KDocker and old instance of -KDocker are started from different directories (the current directory +2. Problem with relative paths if new instance of TDEDocker and old instance of +TDEDocker are started from different directories (the current directory information is not transmitted across instances) Reporting Bugs @@ -14,16 +14,16 @@ Reporting Bugs Bugs and wishes to gramakri at uiuc dot edu. Follow the guidelines below , if possible and send it to me at gramakri at uiuc dot edu. -* Add the following line in kdocker.pro (in fact just uncomment it) +* Add the following line in tdedocker.pro (in fact just uncomment it) DEFINES += ENABLE_TRACING * Now do a "make clean" and "then make". -* Launch KDocker. Recreate the problem. +* Launch TDEDocker. Recreate the problem. - Right Click on the tray icon. -- Choose "About KDocker" +- Choose "About TDEDocker" - You should see a button called "Show Trace". Please note that this button will appear only when compiled with tracing -- If you send SIGUSR1 to the KDocker process, it will dump all the trace to - ~/kdocker.trace. Send that file to me. +- If you send SIGUSR1 to the TDEDocker process, it will dump all the trace to + ~/tdedocker.trace. Send that file to me. May the force be with you. |