From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Womick, Don" Subject: RE: C-c ' prepends , to shell comment lines Date: Sun, 5 Oct 2008 05:42:27 -0500 Message-ID: <6886503D1523ED41ACBD82F205B220EA03001470@ad01msxmb004.US.Cingular.Net> References: <6886503D1523ED41ACBD82F205B220EA03001455@ad01msxmb004.US.Cingular.Net> <386A2CC5-3A32-487A-87A5-A83B170C236A@uva.nl> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0138306930==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KmRGq-0005Sv-0w for emacs-orgmode@gnu.org; Sun, 05 Oct 2008 06:55:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KmRGn-0005Qa-Fp for emacs-orgmode@gnu.org; Sun, 05 Oct 2008 06:55:27 -0400 Received: from [199.232.76.173] (port=44712 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KmRGn-0005QI-B4 for emacs-orgmode@gnu.org; Sun, 05 Oct 2008 06:55:25 -0400 Received: from mail120.messagelabs.com ([216.82.250.83]:57209) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KmR4Q-0002Pl-Bb for emacs-orgmode@gnu.org; Sun, 05 Oct 2008 06:42:39 -0400 Content-class: urn:content-classes:message In-Reply-To: <386A2CC5-3A32-487A-87A5-A83B170C236A@uva.nl> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org This is a multi-part message in MIME format. --===============0138306930== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C926D7.0FF4B91F" This is a multi-part message in MIME format. ------_=_NextPart_001_01C926D7.0FF4B91F Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Carsten, thanks. That makes sense, once you know about it. =20 I don't think this behavior is documented. Can you add it the manual? Might prevent a stupid question or two... :-) =20 Regards, Don ________________________________ From: Carsten Dominik [mailto:carsten.dominik@gmail.com] On Behalf Of Carsten Dominik Sent: Sunday, October 05, 2008 5:05 AM To: Womick, Don Cc: emacs-orgmode@gnu.org Subject: Re: [Orgmode] C-c ' prepends , to shell comment lines =20 Hi Don, =20 this is on purpose. Putting a comma in front of such lines makes sure Org does not consider them as special, for example when searching for in-buffer options like #+STARTUP. The same thing happens for lines startin with a star, which Org could mistake for an outline heading. The parsers for startup options and for outline structure do not waste time on analyzing the structure of the document to distinguish lines inside and outside code blocks. =20 The commas admittedly look not so good in the Emacs buffer, but they will be stripped for editing with C-c ', and also for export. =20 Hope this explains it. =20 - Carsten =20 On Oct 4, 2008, at 4:17 PM, Womick, Don wrote: After running C-c ' (apostrophe) on a shell script between #+BEGIN_SRC and #+END_SRC tags and returning to the org file using C-c ' again, comments in the script have a , (comma) prepended. =20 If I have =20 #+BEGIN_SRC shell-script #! /bin/bash # some comments here... they'll be preceded by commas after C-c ' editing # ls cat myfile # inline comment here, isn't affected #+END_SRC =20 and do C-c ' to pull it into an edit buffer, then C-c ' again to go back to the org file, the result is =20 #+BEGIN_SRC shell-script ,#! /bin/bash ,# some comments here... they'll be preceded by commas after C-c ' editing ,# ls cat myfile # inline comment here, isn't affected #+END_SRC =20 Note the commas in front of each # (comment character). =20 This seems to happen to # characters regardless of the editing mode... I tried a Java snippet with the same results: =20 Before: =20 #+BEGIN_SRC java # hash comment // java comment here public class MyClass() { private String myVariable; // inline comment here } #+END_SRC =20 After: =20 #+BEGIN_SRC java ,# hash comment // java comment here public class MyClass() { private String myVariable; // inline comment here } #+END_SRC =20 I'm running the following: =20 Org-mode version 6.06b GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-08-19 on LENNART-69DE564 (patched) =20 Thanks for org-mode... I've been using this amazing piece of software almost as long as I've been using Emacs (a couple of years now). =20 Regards, Don Womick _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode =20 ------_=_NextPart_001_01C926D7.0FF4B91F Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Carsten, thanks. That makes sense, = once you know about it.

 

I don’t think this behavior = is documented. Can you add it the manual? Might prevent a stupid question = or two… J

 

Regards,

Don

From: = Carsten Dominik [mailto:carsten.dominik@gmail.com] On Behalf Of Carsten Dominik
Sent: Sunday, October 05, = 2008 5:05 AM
To: Womick, Don
Cc: = emacs-orgmode@gnu.org
Subject: Re: [Orgmode] = C-c ' prepends , to shell comment lines

 

Hi Don,

 

this is on purpose.  Putting a comma in front of such lines = makes sure Org does not consider them as special, for example when searching = for in-buffer options like #+STARTUP.  The same thing happens for lines startin with a star, which Org could mistake for an outline = heading.

The parsers for startup options and for outline structure do not = waste time on analyzing the structure of the document to distinguish lines = inside and outside code blocks.

 

The commas admittedly look not so good in the Emacs buffer, but = they will be stripped for editing with C-c ', and also for = export.

 

Hope this explains it.

 

- Carsten

 

On Oct 4, 2008, at 4:17 PM, Womick, Don = wrote:



After running C-c ‘ = (apostrophe) on a shell script between #+BEGIN_SRC and #+END_SRC tags and returning to = the org file using C-c ‘ again, comments in the script have a , (comma) = prepended.

 

If I = have

 

#+BEGIN_SRC shell-script

#! = /bin/bash

# some = comments here... they'll be preceded by commas after C-c ' = editing

#

ls

cat = myfile # inline comment here, isn't affected

#+END_SRC

 

and do C-c ‘ to pull it into = an edit buffer, then C-c ‘ again to go back to the org file, the = result is

 

#+BEGIN_SRC shell-script

,#! = /bin/bash

,# some = comments here... they'll be preceded by commas after C-c ' = editing

,#

ls

cat = myfile # inline comment here, isn't affected

#+END_SRC

 

Note the commas in front of each # (comment character).

 

This seems to happen to # = characters regardless of the editing mode… I tried a Java snippet with the = same results:

 

Before:<= font color=3Dblack>

 

#+BEGIN_SRC java

# hash = comment

// java = comment here

public = class MyClass() {

    private String myVariable; // inline comment = here

}

#+END_SRC

 

After:

 

#+BEGIN_SRC java

,# hash = comment

// java = comment here

public = class MyClass() {

    private String myVariable; // inline comment = here

}

#+END_SRC

 

I’m running the = following:

 

Org-mode version = 6.06b

GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-08-19 on LENNART-69DE564 = (patched)

 

Thanks for org-mode… = I’ve been using this amazing piece of software almost as long as I’ve = been using Emacs (a couple of years now).

 

Regards,=

Don = Womick

_______________= ________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists= .gnu.org/mailman/listinfo/emacs-orgmode

 

------_=_NextPart_001_01C926D7.0FF4B91F-- --===============0138306930== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============0138306930==--