View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001547 | Double Commander | Default | public | 2016-09-21 07:16 | 2025-06-19 08:17 |
| Reporter | dandv | Assigned To | Alexx2000 | ||
| Priority | high | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Projection | none | ETA | none | ||
| Platform | Linux | ||||
| Product Version | 0.7.5 | Product Build | beta | ||
| Summary | 0001547: Provide some visible indication of commands executing in the background | ||||
| Description | If I type a command in the command line (Shift+F2), I have no idea whether it's executing or not, what the output was, or the exit code. | ||||
| Steps To Reproduce | 1. Go to the command line 2. Run a command that takes a while and may or may not succeed, e.g. `git@github.com:moment/moment.git` and assume you might not have access to clone that repo 3. Nothing seems to happen, but after a while, files start appearing in the current directory 4. You don't know when the operation has completed | ||||
| Additional Information | NDN (http://ndn.muxe.com/) behaves much better in this regard. The command executes synchronously, the output is displayed, and can later be accessed with Ctrl+O. | ||||
| Tags | No tags attached. | ||||
| Fixed in Revision | |||||
| Operating system | Linux | ||||
| Widgetset | GTK2 | ||||
| Architecture | 64-bit | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-09-21 07:16 | dandv | New Issue | |
| 2016-09-21 07:57 | Alexx2000 | Note Added: 0001904 | |
| 2016-09-21 07:57 | Alexx2000 | Status | new => feedback |
| 2016-09-21 08:01 | Alexx2000 | Note Edited: 0001904 | |
| 2025-06-19 08:17 | Alexx2000 | Assigned To | => Alexx2000 |
| 2025-06-19 08:17 | Alexx2000 | Status | feedback => closed |
| 2025-06-19 08:17 | Alexx2000 | Resolution | open => no change required |
