This makes it be displayed in the error-messages field with
--json-error-messages. And with --quiet, it will let it be displayed,
which makes sense because it's telling the user why what they requested
to do has failed to happen.
(lck, inprogress) <- prep tfile createtfile mode
if inprogress && not ignorelock
then do
- showNote "transfer already in progress, or unable to take transfer lock"
+ warning "transfer already in progress, or unable to take transfer lock"
return observeFailure
else do
v <- retry 0 info metervar $
--- /dev/null
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2021-10-27T18:40:48Z"
+ content="""
+Aha, that makes sense! addurl constructs a url-based Key to use while
+downloading, and the key transfer machinery prevents redundant downloads
+of the same Key at the same time.
+
+Arguably, the problem is not where the message gets put, but that
+it fails when adding an url to two different paths.
+
+I have, though, moved that message so it will appear in error-messages.
+"""]]