Q: drop the timeline-block-markup setting?
(1) By Richard Hipp (drh) on 2025-03-21 09:36:31 [source]
Ever since check-in 2020-06-02T17:38, the timeline-block-markup setting has been ignored. Rendering of the timeline has always behaved as if that setting was on, even though it defaults to off, and even if it is explicitly set to "off". You can see this, for example, in check-in 2024-02-04T04:42 which shows block markup, even though timeline-block-markup is off on the Fossil repository.
What To Do:
Fix this so that timeline-block-markup works again.
Get timeline-block-markup working again but make it default to "on" instead of "off". Thus default behavior is unchanged from the past several years, but you have the option to change it if you want.
Take this as an opportunity to reduce the number of settings by simply omitting the timeline-block-markup setting, since nobody has complained that it doesn't work for nearly five years, so it must not be important to anybody.
Please share your thought...
(2) By Stephan Beal (stephan) on 2025-03-21 11:12:41 in reply to 1 [link] [source]
Take this as an opportunity to reduce the number of settings by simply omitting the timeline-block-markup setting
Tough call, but my instinct says #3 is correct (for this project, anyway).
(3) By Andy Bradford (andybradford) on 2025-03-21 16:11:39 in reply to 1 [link] [source]
> the timeline-block-markup setting has been ignored. I've never even heard of that setting. If it's in use in my repositories I don't know what effect it has. Sounds like in this case getting rid of it is alright. Andy
(4) By Richard Hipp (drh) on 2025-03-21 16:32:04 in reply to 3 [link] [source]
I don't know what effect it has.
That's my point: Since 2020-06-02, it has been a no-op. It has had no effect on the output.
So we now have two yeses, and no noes. So unless there is an objection soon, I'll go ahead and remove the setting.
(5) By DB (ACB) on 2025-03-21 20:25:48 in reply to 4 [link] [source]
I guess that explains why I've not yet been able to understand what it does.1 I've toggled it and didn't notice any difference. I figured it added a CSS class that would be used by a skin, and perhaps the skin(s) I tried didn't make use of it.
It sounds like people who stick only/mainly to the command line will not miss it.
Will this remove the ability to include "paragraph brakes, tables, lists, headings, etc" in the timeline? I just tested that I could include images on the timeline too, I hope that doesn't go away.
I'm not saying either yes or no to the question. Just trying to learn what I am missing, and might not return.
- ^ I readily admit I've only barely begun to scratch the surface of what fossil can do.
(7) By Thomas Hess (luziferius) on 2025-03-22 17:21:55 in reply to 5 [link] [source]
This is about the removal of (or fixing) the toggle option, not the removal of the Markdown rendering in the timeline feature as a whole.
The setting currently is ineffective and markdown rendering is always on regardless of the setting value. You are currently unable to disable it.
(9) By DB (ACB) on 2025-03-22 20:56:27 in reply to 7 [link] [source]
Yes, I misunderstood. I guess I was being pedantic in thinking the feature was going away.
I did notice on the timeline and forum an updated wiki syntax was in the works.
(10) By Richard Hipp (drh) on 2025-03-22 21:03:54 in reply to 9 [link] [source]
an updated wiki syntax was in the works.
Those plans are cancelled. The changes are abandoned on a branch.
(6) By Zakero (zakero) on 2025-03-21 21:39:27 in reply to 4 [link] [source]
The timeline-block-markup setting works for me and I do use it in almost all of my repos.
In the Timeline settings, I have 'Allow block-markup in timeline' enabled and 'Plaintext comments on timelines' disabled. When 'Plaintext comments on timelines' is enabled it seems to override the block-markup setting. Perhaps this is the issue?
Maybe the better fix would be to remove the 'Plaintext comments on timelines' such that it is the default and keep the block-markup setting?
(8) By Richard Hipp (drh) on 2025-03-22 17:45:15 in reply to 6 [link] [source]
Ever since version 2.12 (we are currently on 2.25, and the next release will be 2.26) Fossil has behaved as if timeline-block-markup where turned on, even when it was turned off. So it was doing what you wanted all along. And nobody complained, so presumably it was doing what everybody else wanted, too.
As of this morning, I have removed the timeline-block-markup setting. Fossil now always allows block markup in checkin comments, and display those comments using that block markup as such as long as timeline-plaintext is off.
So unless you are upgrading from version 2.11 or earlier (circa 2020), you should not notice any change in behavior when you upgrade to 2.26, regardless of what you had timeline-block-markup set to before.