Fossil: View Ticket

2014-02-24
09:26		[202edc2c1c]: Make 'th1-setup' a textarea in settings UI. check-in: cec85224c1 user: jan.nijtmans tags: branch-1.28
2014-02-17
19:48		[202edc2c1c]: Make 'th1-setup' a textarea in settings UI. check-in: 5447125d34 user: jan.nijtmans tags: trunk
12:43		[202edc2c1c]: Make `th1-setup` a textarea in settings UI. Fixed by making it a versionable setting (just as "tcl-setup", for consistancy) and moving it to the second column of the setup page. Remark: Making "th1-setup" versionable is not a good idea: It would mean that any Web-page access must do an additional check for the presence of a versionable setting file. Therefore putting it aside. check-in: 28429acb2b user: jan.nijtmans tags: setup-textarea
12:41		• Closed ticket [202edc2c1c]: Make `th1-setup` a textarea in settings UI plus 4 other changes artifact: 8dd4104658 user: jan.nijtmans
2014-02-16
23:13		• New ticket [202edc2c1c]. artifact: eb5af84c0c user: anonymous

Ticket Hash:	202edc2c1c71bcce5df10e9f34031edebd7b29da
Title:	Make `th1-setup` a textarea in settings UI
Status:	Closed	Type:	Feature_Request
Severity:	Minor	Priority:
Subsystem:		Resolution:	Fixed
Last Modified:	2014-02-17 12:41:48 12.12 years ago	Created:	2014-02-16 23:13:33 12.12 years ago
Version Found In:	1.28

User Comments:

nobody added on 2014-02-16 23:13:33:

I'm utilizing th1-setup for preparing some userland TH1 functions, e.g. th1x.tcl

Now it's usually multi-line when injected via fossil setting th1-setup "$(cat th1)". In the fossil web UI it's displayed as <input type=text> however, where most browsers will turn linebreaks into spaces. Subsequently editing any setting via fossil ui will break th1-setup.

Hence I'd prefer if it became a <textarea> input field as well (like binary-glob etc.), so it retains formatting and doesn't break the TH1 code due to comments or lack of semicolons.

jan.nijtmans added on 2014-02-17 12:41:48:

Fixed in [28429acb2b]. Thanks!