orgweb/Changes: broken formatting of code blocks

orgweb/Changes: broken formatting of code blocks

[Julian Gehring]

[-- Attachment #1: Type: text/plain, Size: 385 bytes --]

Hi,

at the changes page of the orgmode website, some of the code block 
formatting seems to be broken (see http://orgmode.org/Changes.html#sec-3).

Can anyone please check if the attached patch would fix this?  With my 
local setup, this yields a proper display of the code blocks.  Or do the 
commas in front of the code lines have a meaning that I am simply missing?


Best
Julian


[-- Attachment #2: 0001-Changes.org-fix-code-block-formatting.patch --]
[-- Type: text/x-patch, Size: 2368 bytes --]

From 72e27909e8a01bdd44a85f05826a052e1dbe698a Mon Sep 17 00:00:00 2001
From: Julian Gehring <julian.gehring@googlemail.com>
Date: Tue, 10 Apr 2012 21:44:35 +0200
Subject: [PATCH] Changes.org: fix code block formatting

---
 Changes.org |   80 +++++++++++++++++++++++++++++------------------------------
 1 file changed, 40 insertions(+), 40 deletions(-)

diff --git a/Changes.org b/Changes.org
index 409fa95..adc1438 100644
--- a/Changes.org
+++ b/Changes.org
@@ -241,60 +241,60 @@ combines with =visual-line-mode=.
 This results in the following behavior.
 
 #+begin_src org
-  ,#+property: var  foo=1
-  ,#+property: var+ bar=2
+  #+property: var  foo=1
+  #+property: var+ bar=2
   
-  ,#+begin_src emacs-lisp
-  ,  (+ foo bar)
-  ,#+end_src
+  #+begin_src emacs-lisp
+    (+ foo bar)
+  #+end_src
   
-  ,#+results:
-  ,: 3
+  #+results:
+  : 3
   
-  ,#+begin_src emacs-lisp
-  ,  (org-entry-get (point) "var" t)
-  ,#+end_src
+  #+begin_src emacs-lisp
+    (org-entry-get (point) "var" t)
+  #+end_src
   
-  ,#+results:
-  ,: foo=1 bar=2
+  #+results:
+  : foo=1 bar=2
   
-  ,* overwriting a file-wide property
-  ,  :PROPERTIES:
-  ,  :var:      foo=7
-  ,  :END:
+  * overwriting a file-wide property
+    :PROPERTIES:
+    :var:      foo=7
+    :END:
   
-  ,#+begin_src emacs-lisp
-  ,  foo
-  ,#+end_src
+  #+begin_src emacs-lisp
+    foo
+  #+end_src
   
-  ,#+results:
-  ,: 7
+  #+results:
+  : 7
   
-  ,#+begin_src emacs-lisp
-  ,  (org-entry-get (point) "var" t)
-  ,#+end_src
+  #+begin_src emacs-lisp
+    (org-entry-get (point) "var" t)
+  #+end_src
   
-  ,#+results:
-  ,: foo=7
+  #+results:
+  : foo=7
   
-  ,* appending to a file-wide property
-  ,  :PROPERTIES:
-  ,  :var+:      baz=3
-  ,  :END:
+  * appending to a file-wide property
+    :PROPERTIES:
+    :var+:      baz=3
+    :END:
   
-  ,#+begin_src emacs-lisp
-  ,  (+ foo bar baz)
-  ,#+end_src
+  #+begin_src emacs-lisp
+    (+ foo bar baz)
+  #+end_src
   
-  ,#+results:
-  ,: 6
+  #+results:
+  : 6
   
-  ,#+begin_src emacs-lisp
-  ,  (org-entry-get (point) "var" t)
-  ,#+end_src
+  #+begin_src emacs-lisp
+    (org-entry-get (point) "var" t)
+  #+end_src
   
-  ,#+results:
-  ,: foo=1 bar=2 baz=3
+  #+results:
+  : foo=1 bar=2 baz=3
 #+end_src
 
 *** =org-agenda-custom-commands= has a default value ([[git:b3de2dbb953dcadacafeb179899ab9df184da4ff][git]])
-- 
1.7.10

Re: orgweb/Changes: broken formatting of code blocks

[Bastien]

Hi Julian,

Julian Gehring <julian.gehring@googlemail.com> writes:

> at the changes page of the orgmode website, some of the code block
> formatting seems to be broken (see
> http://orgmode.org/Changes.html#sec-3).

I recently pushed a fix for this.  It looks okay to me know.

Can you check again?

> Can anyone please check if the attached patch would fix this?  With my
> local setup, this yields a proper display of the code blocks.  Or do the
> commas in front of the code lines have a meaning that I am simply missing?

The content of the #+begin_src block is inserted as an example, which
looks the right thing to do to me.

Thanks,

-- 
 Bastien

Re: orgweb/Changes: broken formatting of code blocks

[Julian Gehring]

Hi Bastien,

thanks, the formatting of the code block example looks fine now.


Best
Julian


On 04/11/2012 12:19 PM, Bastien wrote:
> Hi Julian,
>
> Julian Gehring<julian.gehring@googlemail.com>  writes:
>
>> at the changes page of the orgmode website, some of the code block
>> formatting seems to be broken (see
>> http://orgmode.org/Changes.html#sec-3).
>
> I recently pushed a fix for this.  It looks okay to me know.
>
> Can you check again?
>
>> Can anyone please check if the attached patch would fix this?  With my
>> local setup, this yields a proper display of the code blocks.  Or do the
>> commas in front of the code lines have a meaning that I am simply missing?
>
> The content of the #+begin_src block is inserted as an example, which
> looks the right thing to do to me.
>
> Thanks,
>