On Feb 16, 2008, at 7:23 AM, Trent Mick wrote:
You get the idea. This mostly becomes a problem when writing
technical
docs with frequent chunks of embedded code, and the solution would
appear to be to have different markup for begin-block and end-block.
This is the approach that the Trac wiki
On Feb 16, 2008 4:07 AM, Pedro Melo [EMAIL PROTECTED] wrote:
On Feb 16, 2008, at 7:23 AM, Trent Mick wrote:
This is also the approach of the Google Code wiki syntax. As well, the
language for language-specific syntax highlighting can be specified
via:
Python}
print hello world
On Feb 16, 2008, at 7:23 AM, Trent Mick wrote:
This is also the approach of the Google Code wiki syntax. As well, the
language for language-specific syntax highlighting can be specified
via:
Python}
print hello world
}}}
Maybe I'm misunderstanding: does the Google
You get the idea. This mostly becomes a problem when writing technical
docs with frequent chunks of embedded code, and the solution would
appear to be to have different markup for begin-block and end-block.
This is the approach that the Trac wiki syntax takes, using
{{{
chunk of code here
Le 2007-12-04 à 16:29, Thomas Nichols a écrit :
I've been using the ~~~ syntax for marking code blocks for a few
weeks,
and it's certainly an improvement over the existing four-space indent.
However, it can be difficult to see at a glance where one code block
begins and another ends, as in
On Dec 4, 2007 4:29 PM, Thomas Nichols [EMAIL PROTECTED] wrote:
I've been using the ~~~ syntax for marking code blocks for a few weeks,
and it's certainly an improvement over the existing four-space indent.
However, it can be difficult to see at a glance where one code block
begins and another
On Dec 4, 2007 4:29 PM, Thomas Nichols [EMAIL PROTECTED] wrote:
Bruce Phillips wrote on 2007/10/11 2:05:
Date: Tue, 09 Oct 2007 22:41:41 -0400
From: Michel Fortin [EMAIL PROTECTED]
Here are our options: ... Any opinion? Should we look into non-ASCII
characters too?
Personally, my
It should also be pointed out that if you are defining the language
used in each block, that helps as well:
some text...
{.python}
some python code
more text
{.python}
more code
We know the lang def only goes on the beginning marker, not the end,
so that helps keep things
On Dec 4, 2007 11:52 PM, John Gabriele [EMAIL PROTECTED] wrote:
[snip]
I tend to like:
---{code}---
code goes here
and here too
---{/code}---
[snip]
* Most everyone putting a block of code in a document probably knows
that if foo starts something, then /foo ends it. If not, it's a
pretty
On Dec 5, 2007 12:08 AM, Waylan Limberg [EMAIL PROTECTED] wrote:
On Dec 4, 2007 11:52 PM, John Gabriele [EMAIL PROTECTED] wrote:
[snip]
I tend to like:
---{code}---
code goes here
and here too
---{/code}---
[snip]
* Most everyone putting a block of code in a document probably
Date: Tue, 09 Oct 2007 22:41:41 -0400
From: Michel Fortin [EMAIL PROTECTED]
Here are our options: ... Any opinion? Should we look into non-
ASCII characters too?
Personally, my preference still goes to tilde.
After comparing various characters in a real document, I also prefer
the tilde.
I'm not sure the indentation feature is so useful. After all, you can use
the old syntax if you want indentation. What do you think?
I'd prefer to keep it simple and leave out the indentation feature.
I'm not against option 2, but I don't see it as a replacement to option 1
(for the
Figures, I respond to the old discussion, then see the new one. Oh
well, Micheal covered my points in more detail here.
On 10/7/07, John MacFarlane [EMAIL PROTECTED] wrote:
[snip]
On (b): Non-extended markdown parsers will make a mess of the
new code blocks with either syntax, since they won't
13 matches
Mail list logo
