Hi John,
thanks for the clarity, I will open an issue to track this problem.

 x-marked as it is not flexible enough for general tiddlywiki use, its use 
lies obviously in compatibility with systems outside tiddlywiki. (importing 
existing documents for instance) .
I would prefer to use an extended version of markdown than tiddlywikitext - 
it is just finding the right approach - I will probably experiment with 
making a version of tiddlywikitext that is more like markdown.

On Friday, January 1, 2016 at 12:37:54 PM UTC, John Doe wrote:
>
> Thanks for the reply BJ. I am sorry if i did not describe the problem 
> properly previously. Let me restate the problem again:
>
> Only the color highlighting feature from the codemirror is not working 
> with the x-marked.
> It was working perfectly with the x-markdown plugin that comes with 
> Tiddlywiki.
>
>  
> After playing around with it for a week i am considering whether to use 
> the x-marked or the default wikiText that Tiddlywiki provides. Since there 
> are some things i would like to have that are not provided by the x-marked 
> plugin. For eg. Linking to other Tiddlers, highlighting text using the 
> ==Text== syntax, quick css inside the text etc.
>
>
> On Friday, January 1, 2016 at 3:05:36 PM UTC+5:30, BJ wrote:
>>
>> I cannot produce a problem with my marked plugin when used with the 
>> codemirror plugin and the markdown plugin. This is what i did:
>>
>> 1.downloaded the tiddlywiki with the codemirror plugin pre-installed from 
>> tiddlywiki.com to form a local copy
>> 2.dragged the markdown plugin from tiddlywiki.com onto my local copy 
>> 3.cloned the tiddler `$:/config/EditorTypeMappings/text/vnd.tiddlywiki` 
>> and rename the clone to$:/config/EditorTypeMappings/text/x-markdown
>> 4.reloaded my local copy.
>> 5.observed the line numberings from the codemirror plugin when editing a 
>> tiddler with type set to text/x-markdown.
>>
>> 6.dragged the marked pluggin from bjtools onto my local copy
>> 7.cloned the tiddler `$:/config/EditorTypeMappings/text/vnd.tiddlywiki` 
>> and rename the clone to $:/config/EditorTypeMappings/text/x-marked
>> 8.reload and when editing a tiddler with type text/x-markdown or 
>> text/x-marked I see the line numbers from the markdown plugin
>>
>> do you have a different setup?
>>
>> w.r.t the highlight parser option for text/x-marked - this needs another 
>> javascript lib to be ported to tiddlywiki for anything to work, so is 
>> probably not useful for you.
>>
>> all the best BJ
>>
>> On Wednesday, December 30, 2015 at 4:29:56 PM UTC, John Doe wrote:
>>>
>>> Hi BJ,
>>>     The codemirror plugin was working with the Markdown plugin (
>>> http://tiddlywiki.com/plugins/tiddlywiki/markdown/). However once i 
>>> installed your plugin for x-marked, the highlighting has stopped working.
>>>
>>> On related note, can you please brief me on how to use the Flexitype 
>>> plugin to set some options of the marked plugin. I want to set highlight to 
>>> true. 
>>>
>>> Thanks in advance!
>>>
>>>
>>> On Wednesday, December 30, 2015 at 7:41:33 PM UTC+5:30, BJ wrote:
>>>>
>>>> I have not tried the codemirror plugin, have at look here:
>>>> https://github.com/Jermolene/TiddlyWiki5/issues/2059
>>>>
>>>> cheers
>>>> BJ
>>>>
>>>> On Tuesday, December 29, 2015 at 5:43:06 PM UTC, John Doe wrote:
>>>>>
>>>>> Thanks BJ for the excellent plugin and saving the day for me!!
>>>>>
>>>>> However, after using your plugin i noticed that codemirror syntax 
>>>>> highlighting has stopped working. Do you know that might be the reason?
>>>>> I suspect that i will have to set xhtml: false , but i dont know how 
>>>>> to set that.
>>>>>
>>>>> If anyone else can help me setup syntax highlighting with marked 
>>>>> plugin, that would really help! Thanks in advance!!
>>>>>
>>>>>
>>>>> On Monday, December 14, 2015 at 1:24:46 AM UTC+5:30, Richard Edwards 
>>>>> wrote:
>>>>>>
>>>>>> Thanks BJ!
>>>>>>
>>>>>> This is very useful to me.  It works very nicely.
>>>>>>
>>>>>> On Sunday, November 1, 2015 at 11:12:27 AM UTC-8, BJ wrote:
>>>>>>>
>>>>>>>
>>>>>>> thanks - I'll sort it out.
>>>>>>>
>>>>>>> On Sunday, November 1, 2015 at 4:51:16 PM UTC, Matabele wrote:
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> Thus the confusion -- screenshot from 
>>>>>>>> http://bjtools.tiddlyspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>> <https://lh3.googleusercontent.com/-2lKFapI3uLA/VjZCoQ1e2KI/AAAAAAAAAio/0W408e-K81A/s1600/151101-0001.png>
>>>>>>>>
>>>>>>>> regards
>>>>>>>>
>>>>>>>> On Sunday, 1 November 2015 18:42:54 UTC+2, BJ wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sunday, November 1, 2015 at 12:17:37 PM UTC, Matabele wrote:
>>>>>>>>>>
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> $:/plugins/bj/small/mdplusdemo/parsers/markapdaper.js throws a 
>>>>>>>>>> javascript error upon reload -- are we supposed to use this plugin 
>>>>>>>>>> or 
>>>>>>>>>> only $:/plugins/bj/small/mdplusdemo. 
>>>>>>>>>>
>>>>>>>>>> If so, with only the latter, your examples don't render. Perhaps 
>>>>>>>>>> this only works with flexitype installed?
>>>>>>>>>>
>>>>>>>>>> yes, you need to use $:/plugins/bj/plugins/marked 
>>>>>>>>>
>>>>>>>>>> regards
>>>>>>>>>>
>>>>>>>>>> On Sunday, 1 November 2015 13:44:15 UTC+2, BJ wrote:
>>>>>>>>>>>
>>>>>>>>>>> Sorry I didn't update the site properly, that's the wrong (old) 
>>>>>>>>>>> plugin. I have updated with new instructions,
>>>>>>>>>>> all the best 
>>>>>>>>>>> BJ
>>>>>>>>>>>
>>>>>>>>>>> On Sunday, November 1, 2015 at 5:02:45 AM UTC, Matabele wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi
>>>>>>>>>>>>
>>>>>>>>>>>> Doesn't render if I copy across the markdown plugin -- what 
>>>>>>>>>>>> tiddler type should I be using?
>>>>>>>>>>>>
>>>>>>>>>>>> regards
>>>>>>>>>>>>
>>>>>>>>>>>> On Saturday, 31 October 2015 23:53:04 UTC+2, BJ wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have put a 'marked' flavor markdown plugin on bjtools
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://bjtools.tiddlyspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tuesday, October 27, 2015 at 6:47:33 PM UTC, Richard 
>>>>>>>>>>>>> Edwards wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>>> Does anyone have or know of a markdown plugin for TiddlyWiki 
>>>>>>>>>>>>>> that handles code fence blocks; i.e. something CommonMark-ish or 
>>>>>>>>>>>>>> github-ish?
>>>>>>>>>>>>>> I might try to make something work, but it would be so much 
>>>>>>>>>>>>>> better if someone else already has done so!
>>>>>>>>>>>>>> What I really want is to create tiddlers from DITA content, 
>>>>>>>>>>>>>> and I'm poking about at markdown as an intermediate conversion 
>>>>>>>>>>>>>> format.
>>>>>>>>>>>>>> Thanks! -red
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Friday, February 6, 2015 at 11:08:47 AM UTC-8, BJ wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Guy,
>>>>>>>>>>>>>>> I am working with a different flavor of markdown from 
>>>>>>>>>>>>>>> https://github.com/chjj/marked,  with extensions for 
>>>>>>>>>>>>>>> tiddlywiki that I am writing, but it will be couple of weeks 
>>>>>>>>>>>>>>> until I 
>>>>>>>>>>>>>>> publish a plugin.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> cheers
>>>>>>>>>>>>>>> BJ
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Friday, February 6, 2015 at 2:49:30 AM UTC-6, Guy 
>>>>>>>>>>>>>>> Rutenberg wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I've installed the markdown plugin for TiddlyWiki5. I've 
>>>>>>>>>>>>>>>> also set the Maruku dialect in $:/config/markdown/dialect. 
>>>>>>>>>>>>>>>> However fenced 
>>>>>>>>>>>>>>>> code blocks (text surrounded by ``` or ~~~) do not seem to 
>>>>>>>>>>>>>>>> work.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Any ideas?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Guy
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>

-- 
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/348fc809-6816-4fc3-befa-8c8c649d9af3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to