)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"cb96eac17488d08cf6d00976e41b58c6cc69d420","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"c556983e_a82346c0","updated":"2026-01-18 22:19:28.000000000","message":"I see! That\u0027s definitively my fault.\nAlso path that include whitespaces were broken and fixed by this change.\nWe can have curly brackets in path (`{}`), and this patch is not enough.\n\nLet\u0027s merge this in mean time, but I think we need to think over how text is reported by OpenOCD Tcl commands.","commit_id":"711468380a90074607393174f56f303300817e97"},{"author":{"_account_id":1000853,"name":"zapb","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"8a918b5e029c579edfc30918d98459f45e7fa9af","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"da9d4148_1b610b98","in_reply_to":"c556983e_a82346c0","updated":"2026-01-19 07:59:21.000000000","message":"I agree in general, we need an escape function, for example, in case a string contains whitespaces etc...\nBut can you provide an example for this case. In what circumstances contains the driver **name** Windows paths or similar (as indicates in the commit message)? Asking also because this makes it even more nasty to parse ;)","commit_id":"711468380a90074607393174f56f303300817e97"},{"author":{"_account_id":1002386,"name":"Ahmed Haoues","email":"ahmed.haoues@st.com","username":"ahmed-haoues"},"change_message_id":"415efff911ff792b6c6c4ecca9e63345af1d4d6f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"47af0cce_4c7b0c83","in_reply_to":"da9d4148_1b610b98","updated":"2026-01-19 11:23:33.000000000","message":"You’re right, in the general case we definitely need an escape mechanism for strings (whitespaces, special characters, etc.).\n\nIn our specific case, the issue occurs when we reuse the external loader path as the flash bank name. Internally, when we later query flash list and compare the reported flash bank name against the expected loader name in the target .cfg, we see that the backslashes are effectively lost or mangled.\n\nThis is why I mentioned Windows paths in the commit message: the path is directly reused as an identifier, and any special characters make the parsing fragile and error‑prone.\n\nI fully agree that this makes parsing even nastier, and that’s exactly the point: using raw paths (or any unescaped string with special characters) as identifiers pushes complexity into every place that needs to parse or compare these names.\n\nI also agree that, in our use case, we can work around this either by using / for Windows paths, or by changing the .cfg file to use a different name for the flash bank.","commit_id":"711468380a90074607393174f56f303300817e97"}]}