Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[moin]TOC not work #143

Open
GoogleCodeExporter opened this issue Apr 18, 2015 · 4 comments
Open

[moin]TOC not work #143

GoogleCodeExporter opened this issue Apr 18, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

sed -i "s/'[[TableOfContents]]'/<<TableOfContents>>/g" /usr/bin/txt2tags

OK!

Original issue reported on code.google.com by zhangmingyuan240 on 11 May 2012 at 8:20

@GoogleCodeExporter
Copy link
Author

It seems they changed the syntax. It's fixed now. Thank you for your report.

Original comment by eforg...@gmail.com on 11 May 2012 at 10:38

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

ISTM that MoinMoin 1.6 has changed some things in the syntax. We should be sure 
about that to do a global fix and two different targets if necessary.

Original comment by fgalla...@gmail.com on 17 May 2012 at 3:07

@GoogleCodeExporter
Copy link
Author

Original comment by fgalla...@gmail.com on 17 May 2012 at 3:08

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

I've reviewed the moin syntax page. It seems to be correct with the current 
version.
The only thing we could change is for monospace, because it should be 
`monospace`, while we're using {{{monospace}}}, but the later syntax is also 
for code (which is often displayed as monospaced).

I think it's easier to parse {{{monospace}}} than `monospace` (if an user 
wishes to alter the generated code), and it's also better not to break the 
current txt2tags behavior which isn't faulty so I propose to change nothing.

The moinmoin website is also no very informative about the modified syntax.

http://hg.moinmo.in/moin/1.6/file/9178bd7e91be/docs/CHANGES
http://moinmo.in/RickVanderveer/UpgradingFromMoin15ToMoin16

I think we should stick with the latest moin syntax, otherwise it will be too 
complicated for us, and maybe we could close this issue?


Original comment by eforg...@gmail.com on 13 May 2013 at 3:21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant