Bug in bullets
Snaga
Found a glitch in the bullet script. I can't do upside-down bullets!
e.g.
*** Super-topic
** Secondary topic
* Main idea
** Derivative idea
*** Sub-thought...
Only the bullets that follow in sequence are parsed.
It seems the parser looks for bullets by levels, and anything that
deviates from a 1-2-3 sequence is ignored.
I would love to see bullets and numbering that are parsed on a case-by-
case basis, just like headers. That way I could mix bullets and
numbering, etc.
A related issue is that numbering is parsed the same way, and
numbering [u]restarts[/u] whenever the level is broken, e.g.
# 1.
# 2.
## 1.
# 1.
## 1.
## 2.
But what if I want to do this:
# 1.
## 1.
## 2.
# 2.
## 1.
## 2.
*** point
*** point
## 3.
# 3.
@@ a)
@@ b)
Would this be too hard to implement? In the case of bullets it seems
a [u]simplification[/u] is called for, but this seems harder and more
complex. It requires the parser to group Level One numbering in
continuing sequence until a double line break, and Level Two numbering
in continuing sequence only until a Level One number is encountered.
Or a linebreak of course. Intervening bullets and alphanumerics are
ignored. Or parsed separately. ::headache::
Thing of it is, what I am proposing is [b]the way I usually think[/
b]. I sure would like a mind-map that matches my mind LOL.
[i]
"That's the worst of girls," said Edmund to Peter and the Dwarf.
"They never carry a map in their heads."
"That's because our heads have something inside them," said Lucy.
[/i]
C.S. Lewis, "The Chronicles of Narnia -- Prince Caspian", p.119
While you are at it, why not a blank indent? That is a feature I
sorely miss in HTML as opposed to a word processor. Supplying it in
wiki syntax would be helpful. I use it a lot (or wish I could use it)
to render poetry. How about a syntax like:
> One 5-space indent
>> 10 spaces
>>> 15
> etc.
?
Finally, are we going to see (perhaps with v.1.0) the ability to
choose between single formatting characters and the double-character
syntax used in Creole, Wikipedia, TiddlyWiki, etc.?
e.g.
/italic/
parses the same as
//italic//
Well, forgive my dictiontery, and thank you
S.
_legolas558_
about bugs), but bugs have to be formally entered in the bug tracker. My
idea is that this way you can monitor the bug tracker and get an email
when the bug status changes.
> Thing of it is, what I am proposing is [b]the way I usually think[/
> b]. I sure would like a mind-map that matches my mind LOL.
>
> [i]
> "That's the worst of girls," said Edmund to Peter and the Dwarf.
> "They never carry a map in their heads."
> "That's because our heads have something inside them," said Lucy.
> [/i]
> C.S. Lewis, "The Chronicles of Narnia -- Prince Caspian", p.119
>
> While you are at it, why not a blank indent? That is a feature I
> sorely miss in HTML as opposed to a word processor. Supplying it in
> wiki syntax would be helpful. I use it a lot (or wish I could use it)
> to render poetry. How about a syntax like:
>
>
>> One 5-space indent
>>
>>> 10 spaces
>>>
>>>> 15
>>>>
>> etc.
>>
> ?
>
I don't quite understand this right now, will examine it later.
> Finally, are we going to see (perhaps with v.1.0) the ability to
> choose between single formatting characters and the double-character
> syntax used in Creole, Wikipedia, TiddlyWiki, etc.?
>
> e.g.
> /italic/
> parses the same as
> //italic//
>
Yes, although there will be only 1 WoaS syntax. The different syntax
will be provided with "dialects".
> Well, forgive my dictiontery, and thank you
>
> S.
>
No problem, thank you for writing!
Daniele C.
--
WoaS Project Manager and Lead Developer