On my first run of ./stamp.sh, I answered the "description" question with a string containing bare double quotes; the result was (what I think is) a broken CMakeLists.txt:
include(infra/cmake/enable-experimental-import-std.cmake)
project(
beman.my_project
DESCRIPTION "My description containing "
quoted" characters"
LANGUAGES CXX
VERSION 0.1.0
)
…
I re-ran ./stamp.sh and escaped the quotes with \, which fixed the CMakeLists.txt file:
include(infra/cmake/enable-experimental-import-std.cmake)
project(
beman.my_project
DESCRIPTION "My description containing \"quoted\" characters"
LANGUAGES CXX
VERSION 0.1.0
)
…
but now README.md contains this:
# beman.my_project: My description containing \"quoted\" characters
which is a context where the double quotes don't need escaping.
I can fix this manually and people can just not put quotes in their descriptions, but more robust handling would be sweet (presumably this is "just" escaping quote characters when generating the CMakeLists.txt file…).
On my first run of
./stamp.sh, I answered the "description" question with a string containing bare double quotes; the result was (what I think is) a brokenCMakeLists.txt:I re-ran
./stamp.shand escaped the quotes with\, which fixed theCMakeLists.txtfile:but now
README.mdcontains this:# beman.my_project: My description containing \"quoted\" characterswhich is a context where the double quotes don't need escaping.
I can fix this manually and people can just not put quotes in their descriptions, but more robust handling would be sweet (presumably this is "just" escaping quote characters when generating the
CMakeLists.txtfile…).