Soren,
Thanks for responding so fast!
When I have more time I'll have to look for other rendering differences,
but the short answer is in hind-sight I now understand how custom CSS could
do everything I was seeing. Unfortunately, it didn't occur to me that you'd
used custom CSS to alter how the wikitext markup renders. My first instinct
was that something was wrong on my end because I was/am the learner. And
honestly now I'll go back and look at your stylesheet because I do like it.
Maybe a simple warning up front for people to not worry about it.
Yes, your tiddler on "Block Mode and Inline Mode" did help me have an "ah
ha!" moment in understanding how TiddlyWiki works. I do try to stick to
only using wikitext whenever I can even in tables with the exception of
<br>. The simpler I can keep things when things don't work it's less for me
to trouble shoot. I discovered the CodeMirror editor plugin for adding line
numbers to tiddlers in edit mode and that has help a ton, and I'm using
Notepad++ for the same reason when formatting larger blocks of text at once.
But I'm still confused as to what the differences are in how things behave
in different places. For example back to my spacing issues general input in
a tiddler in edit mode versus in a custom field. From what I've read it
makes it seem like they should behave the same but they don't. Again some
of the most basic things spaces and carriage returns. In tiddler edit mode
spaces are sometimes ignored and carriage returns by default can hide and
break things, but if I paste text into a custom field it seems to ignore
carriage returns. But they are both supposed to be just text fields so
shouldn't they behave the same? It's things like these that make me
perpetually think there is something possibly very basic I'm missing or not
understanding.
On Thursday, July 22, 2021 at 8:27:09 PM UTC-4 Soren Bjornstad wrote:
> Also, my comment should definitely say “vertical space,” not “horizontal
> space,” haha.
>
> On Thursday, July 22, 2021 at 7:26:02 PM UTC-5 Soren Bjornstad wrote:
>
>> Paul,
>>
>> 1. No matter what I do and what I've searched for has been able to
>>> explain why some things render differently for me. This has often caused me
>>> to stop and spend large quantities of time trying to figure out what is
>>> wrong. For example. In no version of TiddlyWiki (or browser or operating
>>> system) that I've downloaded does Heading 2 render with an underline.
>>> Doesn't happen. Ever. But it does in Grok TiddlyWiki.
>>>
>>
>> Ah! This is just because Grok TiddlyWiki has custom CSS rules that make
>> some things look different. In $:/sib/Stylesheet, you'll find:
>>
>> /* Add more horizontal space and a border for headings, except the title.
>> */
>> h2:not(.tc-title) {
>> /*margin-top: 6ex; -- for some bizarre reason Firefox and Chrome are
>> calculating ex-height differently, so eyeballed an appropriate number of
>> inches*/
>> margin-top: 0.4in;
>> padding-bottom: 5px;
>> *border-bottom: 0.05px solid <<color foreground>>;*
>> }
>>
>> Are you able to give some more examples of this? You're not the first
>> person who's been confused by the fact that Grok TiddlyWiki doesn't look
>> exactly like a stock TiddlyWiki because I've configured it differently.
>> Maybe I need to point that out somewhere.
>>
>>
>>> BTW, an article on where spaces are ignored and where they break things
>>> and why would be AMAZING.
>>>
>>
>> Does block mode and inline mode
>> <https://groktiddlywiki.com/read/#Block%20Mode%20and%20Inline%20Mode> help
>> at all? That's specifically about carriage returns, but those are usually
>> more confusing than actual spaces in my experience.
>>
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/99be54fd-fa77-4701-9faf-c08c751ad8c3n%40googlegroups.com.
