From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: C-c ' prepends , to shell comment lines Date: Sun, 5 Oct 2008 11:05:09 +0200 Message-ID: <386A2CC5-3A32-487A-87A5-A83B170C236A@uva.nl> References: <6886503D1523ED41ACBD82F205B220EA03001455@ad01msxmb004.US.Cingular.Net> Mime-Version: 1.0 (Apple Message framework v929.2) Content-Type: multipart/mixed; boundary="===============1515926488==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KmPYD-0002K7-Dq for emacs-orgmode@gnu.org; Sun, 05 Oct 2008 05:05:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KmPYC-0002Jv-LP for emacs-orgmode@gnu.org; Sun, 05 Oct 2008 05:05:17 -0400 Received: from [199.232.76.173] (port=33229 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KmPYC-0002Js-Dn for emacs-orgmode@gnu.org; Sun, 05 Oct 2008 05:05:16 -0400 Received: from ey-out-1920.google.com ([74.125.78.148]:41734) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KmPYB-0004Qm-J9 for emacs-orgmode@gnu.org; Sun, 05 Oct 2008 05:05:16 -0400 Received: by ey-out-1920.google.com with SMTP id 4so682399eyg.24 for ; Sun, 05 Oct 2008 02:05:14 -0700 (PDT) In-Reply-To: <6886503D1523ED41ACBD82F205B220EA03001455@ad01msxmb004.US.Cingular.Net> 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: "Womick, Don" Cc: emacs-orgmode@gnu.org --===============1515926488== Content-Type: multipart/alternative; boundary=Apple-Mail-25-77174159 --Apple-Mail-25-77174159 Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Hi Don, this is on purpose. Putting a comma in front of such lines makes sure =20= Org does not consider them as special, for example when searching for =20= in-buffer options like #+STARTUP. The same thing happens for lines =20 startin with a star, which Org could mistake for an outline heading. The parsers for startup options and for outline structure do not waste =20= time on analyzing the structure of the document to distinguish lines =20 inside and outside code blocks. The commas admittedly look not so good in the Emacs buffer, but they =20 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 =91 (apostrophe) on a shell script between #=20 > +BEGIN_SRC and #+END_SRC tags and returning to the org file using C-=20= > c =91 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 ' =20 > editing > # > ls > cat myfile # inline comment here, isn't affected > #+END_SRC > > and do C-c =91 to pull it into an edit buffer, then C-c =91 again to = go =20 > 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 ' =20 > 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=85 = =20 > I tried a Java snippet with the same results: > > Before: > > #+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=92m running the following: > > Org-mode version 6.06b > GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-08-19 on =20 > LENNART-69DE564 (patched) > > Thanks for org-mode=85 I=92ve been using this amazing piece of = software =20 > almost as long as I=92ve 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 --Apple-Mail-25-77174159 Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable 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:

If = I have
#! = /bin/bash
# = some comments here... they'll be preceded by commas after C-c ' = editing
cat = myfile # inline comment here, isn't = affected
and = do C-c =91 to pull it into an edit buffer, then C-c =91 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
cat = myfile # inline comment here, isn't = affected
# hash comment
// java comment = here
    private String = myVariable; // inline comment here
}
,# hash comment
// java comment = here
    private String = myVariable; // inline comment here
}
I=92m= 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)
Don = Womick
_______________________________= ________________
Emacs-orgmode mailing list
Remember: use `Reply = All' to send replies to the list.
Emacs-orgmode@gnu.org