summaryrefslogtreecommitdiff
path: root/test-project
diff options
context:
space:
mode:
authorZephyr Shannon <earthlingzephyr@gmail.com>2021-09-09 23:15:15 -0700
committerZephyr Shannon <earthlingzephyr@gmail.com>2021-09-09 23:15:15 -0700
commitaad506dfb2bf5dc1234c6dce5971d75051576490 (patch)
tree7d872c19f4b414e156de87c7939567e4462cd7d4 /test-project
parent494d59f92cbe12533eb89b202fc4f5342afcd543 (diff)
downloadrust-mode-aad506dfb2bf5dc1234c6dce5971d75051576490.tar.gz
Fix cargo compilation regex starting match
Previously this regex attempted to match the entire cargo output including the name of the thread that panicked and the entire panic message. In addition it was required that there be whitespace before the start of the word "thread" in that output. I don't know if this was the previous format, but in current Rust compilers "thread" comes at the beginning of the first line. However, there were two problems with this approach. One is that making that leading whitespace mandatory caused the regex to not match correctly. The second problem is that multiline regex matching in emacs is a bit iffy, and even matching the start correctly, if the panic message contained enough characters the full multiline regex could not be matched and the same problem would occur. This commit changes and vastly simplifies the regex to search for the guaranteed portion of the cargo output, starting with the ending `', `. This does come with an increased risk of accidentally matching input that is not actually a panic message, but I think in practice this will be fairly rare.
Diffstat (limited to 'test-project')
0 files changed, 0 insertions, 0 deletions