localhost vs webpage: raw HTTP character entities
(1) By anonymous on 2025-03-18 23:28:14 [link] [source]
When I view https://fossil-scm.org/home/info/4ee3362aac8832aa in the comment I see:
... charaters "`*_\<&[" then ...
When I view my local repo http://localhost:8080/info/4ee3362aac8832aa I see the HTTP character entities as their raw encoding:
... charaters "`*_\<&[" then ...
Is this a misconfiguration on my system, or something within fossil causing the difference?
(2) By Richard Hipp (drh) on 2025-03-18 23:39:03 in reply to 1 [link] [source]
Are you running the very latest trunk check-in of Fossil on you local machine? Because the comments in that check-in are testing the very latest enhancements and fixes. I typically make a fix or enhancement then immediately do a new build and upload it to the server, which is particularly easy to do with Fossil since it is a stand-alone executable - I just have to scp the binary up to the server. #EatYourOwnDogFood.
(3) By anonymous on 2025-03-19 01:11:44 in reply to 2 [link] [source]
Are you running the very latest trunk check-in of Fossil on you local machine?
Oh, okay. No. I am about one day behind the latest.
I will try again later when a new local build is available.
(4) By Mike Swanson (chungy) on 2025-03-19 02:53:11 in reply to 2 [link] [source]
On my machine running Arch Linux and the latest trunk of fossil (the UI page footer reads This page was generated in about 0.006s by Fossil 2.26 [478a0fa79c] 2025-03-18 20:24:06), I also get the effect of the comment for check-in [6d05c66f87] reads:
special characters "\&<`[*_"
This seems to continue even after doing a ./fossil rebuild on the repository.
(5) By Richard Hipp (drh) on 2025-03-19 09:51:04 in reply to 4 [link] [source]
On the menu bar of your "fossil ui" screen, go to Setup→Timeline. Is "Plaintext comments on timeline" checked?
(6) By Mike Swanson (chungy) on 2025-03-19 17:01:06 in reply to 5 [link] [source]
It was, and changing that fixed the display. Thanks!
(7) By anonymous on 2025-03-20 00:04:59 in reply to 5 [link] [source]
On the menu bar of your "fossil ui" screen, go to Setup→Timeline. Is "Plaintext comments on timeline" checked?
I can't find this.
The closest I can find it Admin->Settings but there is no option that has the text "plain" (in any case) there.
(8) By Stephan Beal (stephan) on 2025-03-20 01:05:58 in reply to 7 [link] [source]
I can't find this
It's at /setup_timeline.
(9) By Martin Gagnon (mgagnon) on 2025-03-20 01:09:56 in reply to 7 [link] [source]
The closest I can find it Admin->Settings but there is no option that has the text "plain" (in any case) there.
What about Admin->Timeline ?
(10) By anonymous on 2025-03-20 09:32:38 in reply to 7 [link] [source]
I can't find this.
Thanks to everyone that pointed me to the right place. I found it now.
It has strange behaviour though:
If the "Plaintext comments on timelines" box is unticked, then the "timeline-plaintext" option is not present in /setup_settings
If the "Plaintext comments on timelines" box is ticked, then the "timeline-plaintext" option is present in /setup_settings
That looks like a bug to me. I can't see any reason for an option to disappear from /setup_settings
(11) By Richard Hipp (drh) on 2025-03-20 10:00:02 in reply to 10 [link] [source]
Because of recent complaints from users about having too many settings, I have started to tag some corner-case settings (such as timeline-plaintext) so that they are only shown if their value differs from the default. This is designed to help users focus on the settings that matter, and avoid confusing them with settings that are rarely used, or whose use is discouraged, or that are for legacy compatibility only.
So no is it not a bug. It is by design.
You can see all of the settings, if you click the "Extras" button the submenu bar of the setting page, or if you add the --extra option to the "fossil settings" command.
(12) By Florian Balmer (florian.balmer) on 2025-03-20 15:38:21 in reply to 11 [link] [source]
Because of recent complaints from users about having too many settings ...
As one of the (the only?) person(s) to complain about this:
I think having lots of settings with some of them hidden is much worse than having lots of settings.
With my (repeat) comments that Fossli has too many settings, I was hoping that we could remove or coalesce some of them, to make configuration of Fossil overall simpler and quicker, because it's easier for the user to keep the overview.
But with hiding settings, keeping the overview is getting much more difficult.
(14) By Andy Bradford (andybradford) on 2025-03-20 17:49:31 in reply to 12 [link] [source]
> But with hiding settings, keeping the overview is getting much more > difficult. What if instead the settings were grouped together in logically related chunks? I don't mind additional settings, and especially if they work and are documented, but a little more organization might be helpful. In fact, rather than "Extras", what about "Server", "Email", "Backoffice", "Chat", "All", etc... for the various categories?
(17) By Daniel Dumitriu (danield) on 2025-03-20 19:03:00 in reply to 14 [link] [source]
I also don't see the harm in options; on the contrary. They give one options, instead of the single, hard-coded "option" one'd have otherwise. If not wanted, they may be ignored.
Perhaps we could list them in two or three sections - if we manage to agree on how to make a partially order set out of that bag.
(18) By ravbc on 2025-03-20 21:37:25 in reply to 12 [link] [source]
But with hiding settings, keeping the overview is getting much more difficult.
If only settings that are set to their default values were hidden, then IMHO it shouldn't be too difficult to keep the overview (at least until too many settings become non-default).
I was hoping that we could remove or coalesce some of them
Hiding setting set to default is almost like removing this setting entirely, but keeping the default action, isn't it?
(13) By Richard Hipp (drh) on 2025-03-20 17:43:30 in reply to 5 [source]
Yikes!
I just discovered that since 2012, Fossil has been creating new repositories with timeline-plaintext turned on. I'd been working under the assumption that timeline-plaintext repositories were rare and unusual. But it seems instead that they are the default. I'm not sure how to fix that except to keep moving forward with the 13-year-old default...
(15.1) By Andy Bradford (andybradford) on 2025-03-20 18:09:56 edited from 15.0 in reply to 13 [link] [source]
> I'd been working under the assumption that timeline-plaintext > repositories were rare and unusual. I thought it was intentionally enabled by default for either security or other reasons. I always thought it was a sensible default. This seems to suggest that it was intentional: https://www.fossil-scm.org/home/info/ae63f485715c0989 Andy
(16) By Andy Bradford (andybradford) on 2025-03-20 18:04:54 in reply to 13 [link] [source]
Regarding the timeline-plaintext setting, this thread might shed some light on the matter: https://marc.info/?t=144565637100005&r=1&w=2 Andy
(19) By Mike Swanson (chungy) on 2025-03-21 02:25:18 in reply to 13 [link] [source]
I believe some settings are preserved across clones and syncs, am I correct? Could timeline-plaintext be one of those settings?
This way you don't necessarily need to change the default (though it may still be a good idea for new repositories), but project decisions on how to display check-in comments might propagate and avoid the issue that this thread highlighted.
(20) By Andy Bradford (andybradford) on 2025-03-21 16:28:24 in reply to 19 [link] [source]
> I believe some settings are preserved across clones and syncs, Project Configuration does synchronize. The only other settings that synchronize are actually those committed into the repository as "versionable" settings. And while you're right that this setting could become "versionable" would it actually make sense to promote timeline-plaintext as a "versionable" setting as it's too much a subjective decision and then we would have to allow for those who want it disabled in their local clone? Thanks, Andy
(21) By Florian Balmer (florian.balmer) on 2025-03-21 16:53:43 in reply to 20 [link] [source]
I don't think making this versionable has any advantages?
I see this more as a "set once and never change" setting, unless you want to break your own (previous) comments.
But users should get the setting from upsteam upon cloning, so that they can make sure to stick to the project's style.