Hi Jeremy,

my bad, I thought that the update you mentioned was done some time ago and 
haven't updated TWc core repo; now I've done that and got much nicer 
results but there's still several issues about them.

   - now in tiddlywiki.com_and_builders in cooked/2.9.1/ subfolder there's 
   index.html and in test/ there's index.2.9.1.html which is the same file 
   namely classic.tiddlywiki.com's index.html with updated core
   - still, there's no empty.2.9.1.html in both subfolders
   - the output of bld.bat still has an error; it's a different one, though 
   (see the full output below). Looks like 
   tiddlywiki_externaljs_tiddlyspace.html.recipe was deleted 
   
<https://github.com/TiddlyWiki/tiddlywiki/commit/5a53e55d80d33db12599203e1847c14de456a837>
 
   in TiddlyWiki repo, but building tools are not aware of it
   - when building, still phantom_driver.js is shown in browser instead of 
   anything helpful
   - there's a number of failed tests shown in cooked/2.9.1/tests.html. 
   I've rebuild with the current TWc core and can see that there's only one 
   block of tests that are failed after my changes, over 20 blocks are failed 
   with the current core. Tests are defined in TiddlyWiki/test/, right? 
   Looks it's time to rebuild them (for instance 76.15 shows that slices with 
   spaces in slice name should be ignored which is no longer the case), 
   although that requires some time.
   
Any suggestions?

Best regards,
Yakov.

PS after I wrote this reply and tried to submit it to the group, it got 
deleted (I haven't even got a mail notification about it), so I had to 
rewrite it again. Any ideas why could that happen?

Full bld.bat output:

BUILD: clearing target folder: "cooked/2.9.1"
- - - - - - - - - - - - - - -
BUILD: assembling INDEX.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ./index.html.recipe
Executing command: rendertiddler 
$:/core/templates/tiddlywiki2.template.html 
D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/index.html 
text/plain
- - - - - - - - - - - - - - -
BUILD: assembling TESTS.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ../tiddlywiki/test/recipes/tests.html.recipe
Executing command: rendertiddler 
$:/core/templates/tiddlywiki2.template.html 
D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/tests.html 
text/plain
- - - - - - - - - - - - - - -
BUILD: creating TIDDLYWIKI_EXTERNALJS.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ../tiddlywiki/tiddlywiki_externaljs.html.recipe
Executing command: rendertiddler 
$:/core/templates/tiddlywiki2.template.html 
D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/tiddlywiki_externaljs.html
 
text/plain
- - - - - - - - - - - - - - -
BUILD: creating TIDDLYWIKI_EXTERNALJS_TIDDLYSPACE.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load 
../tiddlywiki/tiddlywiki_externaljs_tiddlyspace.html.recipe
Error: No tiddlers found in file 
"../tiddlywiki/tiddlywiki_externaljs_tiddlyspace.html.recipe"
- - - - - - - - - - - - - - -
BUILD: creating TWCORE.JS (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ../tiddlywiki/tiddlywikinosaver.html.recipe
Executing command: rendertiddler 
$:/core/templates/tiddlywiki2.externaljs.template.html 
D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/twcore.js 
text/plain
- - - - - - - - - - - - - - -
BUILD: copying TIDDLYSAVER.JAR
- - - - - - - - - - - - - - -
BUILD: copying JQUERY.JS
- - - - - - - - - - - - - - -
BUILD: copying JQUERY.TWSTYLESHEET.JS
- - - - - - - - - - - - - - -
BUILD: creating EMPTY.HTML and INDEX.XML from INDEX.HTML
- - - - - - - - - - - - - - -
BUILD: copying INDEX.HTML to TEST/INDEX.2.9.1.HTML
BUILD: copying EMPTY.HTML to TEST/EMPTY.2.9.1.HTML
- - - - - - - - - - - - - - -
BUILD: done

суббота, 11 ноября 2017 г., 21:12:18 UTC+3 пользователь Yakov написал:
>
> Hello Jeremy,
>
> I've played a bit with these tools and got a number of questions (and also 
> notes regarding how the .md file [1]).
>
> What I have done already:
>
>    - downloaded WinDiff, pulled TiddlyWiki/TiddlyWiki to 
>    somedir\TiddlyWiki, TiddlyWiki/tiddlywiki.com to 
>    somedir\tiddlywiki.com_and_builders, Jermolene/TiddlyWiki5 to 
>    somedir\TiddlyWiki5.
>       - actually, somedir\TiddlyWiki was somedir\TiddlyWiki Classic core 
>       at first, but running somedir\tiddlywiki.com_and_builders\bld.bat 
>       showed some errors and I've figured (judging by the bld.bat code) 
>       that path to the TiddlyWiki Classic repo must be ..\TiddlyWiki 
>       relatively to bld.bat and is not configurable
>       - (haven't downloaded curl and phantomjs since the .md says the 
>       former is needed to retrieve content from TiddlySpace and the latter is 
>       only used by the OS X/Linux batch files; and haven't pulled 
>       TiddlyWiki/tiddlywiki.github.com since I'm not publishing the build 
>       to tiddlywiki.com yet)
>       - edited somedir\tiddlywiki.com_and_builders\setenv.bat namely:
>       - TIDDLYWIKI_RELEASE=2.9.1
>       - TIDDLYWIKI5_DIR=%CD%\..\TiddlyWiki5
>       - SET BROWSER="C:\<path\to\Vivaldi>\vivaldi.exe"
>       - SET DIFF="<somedir>\WinDiff.exe" 
>       - run bld.bat from the somedir\tiddlywiki.com_and_builders. What 
>    happens:
>       - somedir\tiddlywiki.com_and_builders\cooked\2.9.1 is cleared as 
>       expected.
>       - what is created inside \2.9.1:
>          - jquery.js
>          - jQuery.twStylesheet.js
>          - tests.html
>          - TiddlySaver.jar
>          - tiddlywiki_externaljs.html
>          - tiddlywiki_externaljs_tiddlyspace.html
>          - twcore.js
>          - however, despite the .bat reports ... creating EMPTY.HTML and 
>       INDEX.XML from INDEX.HTML ... copying INDEX.HTML to 
> TEST/INDEX.2.9.1.HTML 
>       ... copying EMPTY.HTML to TEST/EMPTY.2.9.1.HTML, there's no 
>       INDEX.2.9.1.HTML and EMPTY.2.9.1.HTML inside the 
>       somedir\tiddlywiki.com_and_builders\test\ folder
>       - in browser (Vivaldi): 
>       somedir\tiddlywiki.com_and_builders\phantom_driver.js is opened and 
>       nothing else (no html)
>       - full output of bld.bat is below
>       - I'm puzzled: is there something I haved missed? Where should I 
>    look for the built TWc file? Can I build it before any tests just to see 
>    what's built? (the process description suggests that it should work this 
>    way but it seems something went wrong)
>    
> Some notes and questions regarding the .md file:
>
>    - it wasn't obvious that I have to pull tiddlywiki/tiddlywiki.com and 
>    look for setenv.bat and bld.bat there (not in TW5 repo)
>    - the repo describes the recommended directory structure but doesn't 
>    mention that it is required that the TWc repo must have path 
>    ../tiddlywiki relatively to bld.bat 
>    - there's 2 sections headed "Building classic.tiddlywiki.com on 
>    Windows". What's the difference? The first one is actually needed for both 
>    building TWc file and classic.tiddlywiki.com which is somewhat 
>    confusing (I'd change to Building classic.tiddlywiki.com and 
>    TiddlyWiki Classic on Windows)
>    - the overall hierarchy of sections/headers is somewhat confusing, 
>    too, but I'll be ready to propose distinct changes after I successfully 
>    build TWc, I think
>    
>
> Best regards,
> Yakov.
>
> [1] https://github.com/TiddlyWiki/tiddlywiki.com/blob/master/README.md
> full output of bld.bat (with the paths substituted with <somedir>):
> BUILD: clearing target folder: "cooked/2.9.1"
> - - - - - - - - - - - - - - -
> BUILD: assembling INDEX.HTML (v2.9.1)
> Boot log:
>   Startup task: load-modules
>   Startup task: info after: load-modules before: startup
>   Startup task: startup after: load-modules
>   Startup task: story after: startup
>   Startup task: commands platforms: node after: story
> Executing command: load ./index.html.recipe
> fs.js:642
>   return binding.open(pathModule._makeLong(path), stringToFlags(flags), 
> mode);
>                  ^
>
> Error: ENOENT: no such file or directory, open '<somedir
> >\tiddlywiki\content\split.recipe'
>     at Error (native)
>     at Object.fs.openSync (fs.js:642:18)
>     at Object.fs.readFileSync (fs.js:510:33)
>     at processRecipe ($:/plugins/tiddlywiki/classictools/recipe.js:63:34)
>     at exports.text/vnd.tiddlywiki2-recipe 
> ($:/plugins/tiddlywiki/classictools/recipe.js:71:2)
>     at $tw.Wiki.deserializeTiddlers (<somedir>
> \TiddlyWiki5\boot\boot.js:1249:23)
>     at $tw.loadTiddlersFromFile (<somedir>
> \TiddlyWiki5\boot\boot.js:1480:23)
>     at $tw.loadTiddlersFromPath (<somedir>
> \TiddlyWiki5\boot\boot.js:1530:22)
>     at Command.execute ($:/core/modules/commands/load.js:33:21)
>     at Commander.executeNextCommand ($:/core/modules/commander.js:115:14)
> - - - - - - - - - - - - - - -
> BUILD: assembling TESTS.HTML (v2.9.1)
> Boot log:
>   Startup task: load-modules
>   Startup task: info after: load-modules before: startup
>   Startup task: startup after: load-modules
>   Startup task: story after: startup
>   Startup task: commands platforms: node after: story
> Executing command: load ../tiddlywiki/test/recipes/tests.html.recipe
> Executing command: rendertiddler 
> $:/core/templates/tiddlywiki2.template.html 
> <somedir>\tiddlywiki.com_and_builders\cooked\2.9.1/tests.html 
> text/plain
> - - - - - - - - - - - - - - -
> BUILD: creating TIDDLYWIKI_EXTERNALJS.HTML (v2.9.1)
> Boot log:
>   Startup task: load-modules
>   Startup task: info after: load-modules before: startup
>   Startup task: startup after: load-modules
>   Startup task: story after: startup
>   Startup task: commands platforms: node after: story
> Executing command: load ../tiddlywiki/tiddlywiki_externaljs.html.recipe
> Executing command: rendertiddler 
> $:/core/templates/tiddlywiki2.template.html 
> <somedir>\tiddlywiki.com_and_builders\cooked\2.9.1/tiddlywiki_externaljs.html 
> text/plain
> - - - - - - - - - - - - - - -
> BUILD: creating TIDDLYWIKI_EXTERNALJS_TIDDLYSPACE.HTML (v2.9.1)
> Boot log:
>   Startup task: load-modules
>   Startup task: info after: load-modules before: startup
>   Startup task: startup after: load-modules
>   Startup task: story after: startup
>   Startup task: commands platforms: node after: story
> Executing command: load 
> ../tiddlywiki/tiddlywiki_externaljs_tiddlyspace.html.recipe
> Executing command: rendertiddler 
> $:/core/templates/tiddlywiki2.template.html 
> <somedir>\tiddlywiki.com_and_builders\cooked\2.9.1/tiddlywiki_externaljs_tiddlyspace.html
>  
> text/plain
> - - - - - - - - - - - - - - -
> BUILD: creating TWCORE.JS (v2.9.1)
> Boot log:
>   Startup task: load-modules
>   Startup task: info after: load-modules before: startup
>   Startup task: startup after: load-modules
>   Startup task: story after: startup
>   Startup task: commands platforms: node after: story
> Executing command: load ../tiddlywiki/tiddlywikinosaver.html.recipe
> Executing command: rendertiddler 
> $:/core/templates/tiddlywiki2.externaljs.template.html 
> <somedir>\tiddlywiki.com_and_builders\cooked\2.9.1/twcore.js 
> text/plain
> - - - - - - - - - - - - - - -
> BUILD: copying TIDDLYSAVER.JAR
> - - - - - - - - - - - - - - -
> BUILD: copying JQUERY.JS
> - - - - - - - - - - - - - - -
> BUILD: copying JQUERY.TWSTYLESHEET.JS
> - - - - - - - - - - - - - - -
> BUILD: creating EMPTY.HTML and INDEX.XML from INDEX.HTML
> - - - - - - - - - - - - - - -
> BUILD: copying INDEX.HTML to TEST/INDEX.2.9.1.HTML
> BUILD: copying EMPTY.HTML to TEST/EMPTY.2.9.1.HTML
> - - - - - - - - - - - - - - -
> BUILD: done
>
> воскресенье, 5 ноября 2017 г., 17:48:39 UTC+3 пользователь Jeremy Ruston 
> написал:
>>
>> Hi Yakov
>>
>> I've made a number of updates that should get the TW2 build process 
>> working again:
>>
>> 1. Fixing a regression in TW5 that had broken the "classictools" TW5 
>> plugin that we use for the build process
>> 2. Removing the old code associated with pulling the content down from 
>> TiddlySpace, and instead storing the content in the tiddlywiki repo
>> 3. Working around the removal of the editions/tw2 edition from TW5
>>
>>
>> https://github.com/Jermolene/TiddlyWiki5/commit/95b84dd0ca34d7ae4019d0f3c20a55eb5318096e
>>
>> https://github.com/TiddlyWiki/tiddlywiki/commit/c5d5c85eb7337a4f052f0d0151de0679be72e0ed
>>
>> https://github.com/TiddlyWiki/tiddlywiki.com/commit/46daaa4397d143b467bb5ba2deb938bd817ca642
>>
>> https://github.com/TiddlyWiki/tiddlywiki/commit/5a53e55d80d33db12599203e1847c14de456a837
>>
>> Anyhow, things are working for me now under Mac OS X. I haven't tested 
>> under Windows.
>>
>> The instructions for the build process can be found here:
>>
>> https://github.com/tiddlywiki/tiddlywiki.com
>>
>> Hopefully now Eric and I between us should be able to help you get up and 
>> running,
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>> On Thu, Nov 2, 2017 at 3:22 PM, Yakov <yakov.litv...@gmail.com> wrote:
>>
>>> Hi Jeremy,
>>>
>>> I'm not familiar with Ruby, too, and I have no preferences among the two 
>>> ways, actually I'm looking for an "at least this works" way. However, I'm 
>>> not familiar with the unit testing system used for TWc core and have no 
>>> idea if building with TW5 supports that. Also, I need some how-to 
>>> guide/help since I haven't found any. TiddlyWikiDev space [1] gives links 
>>> to [2] where I haven't found any instructions and to [3] which seems to be 
>>> an instruction to build classic.tiddlywiki.com and which looks quite 
>>> complicated (I can try to extract a recipe of how to build TWc from there, 
>>> but if there's something more brief, it will be lovely to know). Also 
>>> please keep in mind that for now I'm not very familiar with TW5.
>>>
>>> Best regards,
>>> Yakov.
>>>
>>> [1] 
>>> http://yakovl.bplaced.net/TW/TS_backups/TiddlyWikiDev.tiddlyspace.com%20(31.12.2016).html#Build
>>>  
>>> [2] http://tiddlywiki.com/dev/
>>> [3] https://github.com/TiddlyWiki/tiddlywiki.com/blob/master/README.md
>>>
>>> четверг, 2 ноября 2017 г., 14:12:22 UTC+3 пользователь Jeremy Ruston 
>>> написал:
>>>>
>>>> Hi BJ
>>>>
>>>> what version of the core can be used to build TWC?
>>>>
>>>>
>>>> One might need to do a git bisect to find the last working build. Some 
>>>> of the code is pretty hacky so may be better to slightly re-engineer.
>>>>
>>>> The current code is written as a deserialiser, but needs the file path 
>>>> of the file. The old hack for that no longer works. I think better to 
>>>> rewrite as a “load-classic-recipe” command
>>>>
>>>> Best wishes
>>>>
>>>> Jeremy
>>>>
>>>>
>>>> On Wednesday, November 1, 2017 at 6:03:54 PM UTC+1, Jeremy Ruston wrote:
>>>>>
>>>>> Hi Yakov
>>>>>
>>>>> Apologies for the late response.
>>>>>
>>>>> I'm afraid I can't help with cook/ginsu; I always found them difficult 
>>>>> to use because I'm not familiar with Ruby. That was what drove me to 
>>>>> rewrite the TWC build process with TW5 back in 2011.
>>>>>
>>>>> I've just tried to get the TW5-based build process running and found 
>>>>> that it is currently broken due to a minor change in TW5 since it was 
>>>>> last 
>>>>> used.
>>>>>
>>>>> I'm happy to get things fixed up again, or should I wait to see how 
>>>>> you get on with cook/ginsu?
>>>>>
>>>>> Best wishes
>>>>>
>>>>> Jeremy.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Oct 29, 2017 at 11:40 PM, Yakov <yakov.litv...@gmail.com> 
>>>>> wrote:
>>>>>
>>>>>> Hello everyone,
>>>>>>
>>>>>> not sure if it's worthy to post here since the thread is very old; 
>>>>>> still it seems to have almost every reference I've found so far, so...
>>>>>>
>>>>>> I'm on Windows (10) and I'd like to build TWc core. I've pulled 
>>>>>> TiddlyWiki Classic repo (my branch 
>>>>>> <https://github.com/YakovL/tiddlywiki/tree/YLTW> that I'd like to 
>>>>>> build and test), installed Ruby (v2.4.2 x64), pulled 
>>>>>> https://github.com/TiddlyWiki/cooker to a separate folder, tried run 
>>>>>> to biuld and got an error that takes place even if I just run cook.rb 
>>>>>> -h:
>>>>>>
>>>>>> <custom path to 
>>>>>> installations>/Ruby_2_4__x64/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
>>>>>>  
>>>>>> `require': cannot load such file -- recipe (LoadError)
>>>>>>         from <custom path to 
>>>>>> installations>/Ruby_2_4__x64/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
>>>>>>  
>>>>>> `require'
>>>>>>         from <path to TiddlyWiki Classic cook>/cook.rb:7:in `<main>'
>>>>>>
>>>>>> Can anybody help me with that? I'd like to take maintainance of TWc, 
>>>>>> but for that (and for my own needs) I have to learn how to build TWc 
>>>>>> core!
>>>>>>
>>>>>> Guidance regarding building TWC with TW5 is also appreciated, but it 
>>>>>> seems that using cook should be quite simple and there's either 
>>>>>> something 
>>>>>> that's broken or I'm missing some simple detail. I have no knowledge of 
>>>>>> Ruby yet, though.
>>>>>>
>>>>>> Best regards,
>>>>>> Yakov.
>>>>>>
>>>>>> суббота, 9 марта 2013 г., 14:24:06 UTC+3 пользователь Jeremy Ruston 
>>>>>> написал:
>>>>>>>
>>>>>>> Hi Tobias
>>>>>>>
>>>>>>> I've made a couple of pull requests that get the TW2 tests running 
>>>>>>> with the new build environment:
>>>>>>>
>>>>>>> https://github.com/TiddlyWiki/tiddlywiki/pull/119 - updates the 
>>>>>>> test recipe and tiddler format to the latest versions understood by the 
>>>>>>> new 
>>>>>>> tools
>>>>>>>
>>>>>>> https://github.com/TiddlyWiki/tiddlywiki.com/pull/10 - adds a line 
>>>>>>> to bld.sh to build the tests.html file
>>>>>>>
>>>>>>> (I also made some changes to TW5 to get things working, so you'll 
>>>>>>> need the latest version of that too).
>>>>>>>
>>>>>>> At the moment you can run the tests by opening tests.html in the 
>>>>>>> browser. The next step is to use phantom.js to run the tests 
>>>>>>> automatically.
>>>>>>>
>>>>>>> Best wishes
>>>>>>>
>>>>>>> Jeremy
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Mar 7, 2013 at 11:26 PM, Tobias Beer <beert...@gmail.com> 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thanks Jeremy,
>>>>>>>>
>>>>>>>> I'll try to...
>>>>>>>>
>>>>>>>>    - dig into this
>>>>>>>>    - see if I can get to set up my machine and build the thing
>>>>>>>>       - perhaps using both, the old and new process
>>>>>>>>    - see what I can bring over to TiddlyWikiDev 
>>>>>>>>       - I like things at one place (less scattered)
>>>>>>>>    
>>>>>>>> Cheers, Tobias.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -- 
>>>>>>> Jeremy Ruston
>>>>>>> mailto:jeremy...@gmail.com
>>>>>>>
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "TiddlyWikiDev" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to tiddlywikide...@googlegroups.com.
>>>>>> To post to this group, send email to tiddly...@googlegroups.com.
>>>>>> Visit this group at https://groups.google.com/group/tiddlywikidev.
>>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/d/msgid/tiddlywikidev/44bd4148-caf3-44b4-b552-1f82d641bf86%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/tiddlywikidev/44bd4148-caf3-44b4-b552-1f82d641bf86%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> Jeremy Ruston
>>>>> mailto:jeremy...@gmail.com
>>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "TiddlyWikiDev" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to tiddlywikide...@googlegroups.com.
>>>> To post to this group, send email to tiddly...@googlegroups.com.
>>>> Visit this group at https://groups.google.com/group/tiddlywikidev.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/tiddlywikidev/31de5d30-70bb-484a-a94e-6990e04ea447%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/tiddlywikidev/31de5d30-70bb-484a-a94e-6990e04ea447%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "TiddlyWikiDev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to tiddlywikide...@googlegroups.com.
>>> To post to this group, send email to tiddly...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/tiddlywikidev.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywikidev/c236d854-798c-4297-992f-7055a1af371a%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/tiddlywikidev/c236d854-798c-4297-992f-7055a1af371a%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> Jeremy Ruston
>> mailto:jeremy...@gmail.com
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/f52d648d-b6b6-4f89-aff3-fda3665d3018%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to