Or, to generally force one(!) line break, whenever a macro call is
immediately followed by that troublesome syntax, e.g. headers, tables,
etc... which would have to be "escaped" somehow, if the trailing
characters were not intended as such wiki-markup.

THUS...
<<macro>>!another header

WOULD RESULT IN:
***macro output***
Another Header


On 23 Jun., 22:38, Tobias Beer <beertob...@googlemail.com> wrote:
> Of course, I get it now... but that's a bit of a problem, markupwise.
> Because, for headers and tables, etc. a linebreak is required. Would
> it be good then, if there were some optional switch to remove any
> following linebreak, maybe like so:
> a) <<!<br>callFoo>>
> b) <<!br;callFoo>>
> c) etc...
>
> ???
>
> On 23 Jun., 21:16, FND <f...@gmx.net> wrote:
>
> > > Thanks for the idea. Unfortunately, it doesn't work, because the <br>
> > > is not enclosed by the newly created <span>?!? Doesn't that mean that
> > > the "macro-call" initiated via <<callFoo>> is somehow producing it?
>
> > If the macro call were producing it, it would be inside the SPAN
> > (provided the macro call is actually within the SPAN and not breaking
> > out of its place).
>
> > I think what you're seeing might just be the "natural" BR caused by a
> > line break following the macro call.
>
> > However, for the DcTableOfContentsPlugin you might try adding the
> > following to your StyleSheet:
> >      .dcTOC ul {
> >          margin-bottom: 0;
> >      }
>
> > > I saw you were one of the last to 'fiddle with' (I mean maintain :o)
> > > DcTableOfContentsPlugin.
>
> > I'd basically just uploaded it; Doug and Saq were working on the code.
>
> > -- F.
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To post to this group, send email to TiddlyWiki@googlegroups.com
To unsubscribe from this group, send email to 
tiddlywiki+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/TiddlyWiki?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to