-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Noah Kantrowitz skrev 04. juni 2009 22:13:
Link to the last discussion on this (or at least one of the last)
http://groups.google.com/group/trac-dev/browse_thread/thread/f79a1cbb894fe079/8e7d047d0c9fcf16
--Noah
Thanks for the link -- didn't
On Mon, Jun 08, 2009 at 02:36:49PM +0200, Eirik Schwenke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Noah Kantrowitz skrev 04. juni 2009 22:13:
Link to the last discussion on this (or at least one of the last)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Hammel skrev 08. juni 2009 14:46:
On Mon, Jun 08, 2009 at 02:36:49PM +0200, Eirik Schwenke wrote:
Noah Kantrowitz skrev 04. juni 2009 22:13:
[ Note somehow icedove chokes on mutt's quoting, apologies if the
indendation/quotemarkers are
On Mon, Jun 08, 2009 at 03:06:13PM +0200, Eirik Schwenke wrote:
snip/
Its easier to write Trac wiki than ReST. I also find it more human
readable. As a big fan of markdown languages, I was very enamored
with ReST a few years ago. Now, I think its mostly awful, not that
there aren't
On Mon, Jun 8, 2009 at 7:46 AM, Jeff Hammeljham...@openplans.org wrote:
On Mon, Jun 08, 2009 at 02:36:49PM +0200, Eirik Schwenke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Noah Kantrowitz skrev 04. juni 2009 22:13:
Link to the last discussion on this (or at least one of the
On Mon, Jun 8, 2009 at 8:46 AM, Jeff Hammel jham...@openplans.org wrote:
I do agree that it would be nice to use something standard-ish, which is a
plus for ReST. That being said, I would miss Trac wiki syntax greatly. The
other alternative is to spin off Trac wiki (the markdown syntax, not
Eirik Schwenke wrote:
Christian Boos mentioned the WikiEngine refactoring which will make it
possible to generate structured output (e.g. Genshi events or docutils
nodes, so that we could hijack the docutils writers for generating the
static documentation)
Has this taken place in trunk ?
On Mon, Jun 8, 2009 at 8:51 AM, Eirik Schwenkeeirik.schwe...@nsd.uib.no wrote:
Olemis Lang skrev 08. juni 2009 15:24:
On Mon, Jun 8, 2009 at 7:46 AM, Jeff Hammeljham...@openplans.org wrote:
On Mon, Jun 08, 2009 at 02:36:49PM +0200, Eirik Schwenke wrote:
(...)
In fact I even use Trac wiki
Olemis,
I tried to look at your blog, but I think your formatter is broken or
something. Everything is coming out in some foreign language, I think
Spanish or something. Made it very hard to read and understand.
Perhaps you should look into using a different markup scheme?
Xenophobically
A little bit OT, oops !
On Mon, Jun 8, 2009 at 11:22 AM, Ariel Balterar...@arielbalter.com wrote:
Olemis,
I tried to look at your blog, but I think your formatter is broken or
something. Everything is coming out in some foreign language, I think
Spanish or something.
Dont get it, it's in
Interesting thread and also interesting to see how much everyone likes
Trac wiki syntax. I will add my $0.02 US and also take as IMHO:
While I agree that simple text and things like TODO and instruction
related documentation are relatively easy to do in markdown, I have
(and it may be due to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Boos skrev 08. juni 2009 16:26:
Eirik Schwenke wrote:
Christian Boos mentioned the WikiEngine refactoring which will make it
possible to generate structured output (e.g. Genshi events or docutils
nodes, so that we could hijack the
FYI, you link to your copyright on your web site points to a non-
existent file in your source control browser.
I'd like to read it. I was very interesting in your GraphViz plugin,
but based on your comments i am not scared off a bit, depending on
what you copyright actually says.
On Mon, Jun 8, 2009 at 3:37 PM, yoheebyoh...@gmail.com wrote:
FYI, you link to your copyright on your web site points to a non-
existent file in your source control browser.
I'd like to read it. I was very interesting in your GraphViz plugin,
but based on your comments i am not scared off
Eirik Schwenke wrote:
Christian Boos skrev 08. juni 2009 16:26:
There are several improvements I'd like to do in the specific case of
tables. One is to make it possible to use a wiki processor for big
cells, e.g.
{{{
#!td
any multiline wiki markup here ...
(much like #!div)
}}}
15 matches
Mail list logo
