summaryrefslogtreecommitdiff
path: root/Messages/Concurrent.hs
Commit message (Collapse)AuthorAge
* fix build w/o concurrent-outputGravatar Joey Hess2016-02-15
|
* quiet warning on windowsGravatar Joey Hess2016-02-15
|
* Work around problem with concurrent-output when in a non-unicode locale by ↵Gravatar Joey Hess2016-02-14
| | | | | | | | | | | | avoiding use of it in such a locale. Instead -J will behave as if it was built without concurrent-output support in this situation. Ie, it will be mostly quiet, except when there's an error. Note that it's not a problem for a filename to contain invalid utf-8 when in a utf-8 locale. That is handled ok by concurrent-output. It's only displaying unicode characters in a non-unicode locale that doesn't work.
* fix build warning when built w/o concurrent-outputGravatar Joey Hess2015-11-10
|
* Concurrent progress bars are now displayed when using -J with a command that ↵Gravatar Joey Hess2015-11-06
| | | | moves file contents around.
* don't display console regions untill there is output in themGravatar Joey Hess2015-11-05
|
* join back threads before ending concurrent output so display worksGravatar Joey Hess2015-11-05
| | | | | I didn't really want to put allowConcurrentOutput in CmdLine.Action, but there were dep loops and that was the best place available.
* add regions to concurrent outputGravatar Joey Hess2015-11-04
| | | | still no progress displays when getting files etc, but a big improvement
* concurrent-output, first passGravatar Joey Hess2015-11-04
Output without -Jn should be unchanged from before. With -Jn, concurrent-output is used for messages, but regions are not used yet, so it's a mess.