From: John Kitchin <jkitchin@andrew.cmu.edu>
To: John Kitchin <jkitchin@andrew.cmu.edu>,
Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: uncommnet-region behavior in org-src blocks
Date: Sat, 19 Mar 2016 14:03:45 -0400 [thread overview]
Message-ID: <CAJ51ETr9P12fXHCpUtv6T4npH8wAYj5M3hb6X7xpbna=z5tDgg@mail.gmail.com> (raw)
In-Reply-To: <87k2ky8jwd.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
sure, that is true. I am still surprised that "uncommenting" adds a # which
in org is a comment. actually that seems to happen everywhere in the
org-file!
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Sat, Mar 19, 2016 at 1:20 PM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> On Saturday, 19 Mar 2016 at 12:44, John Kitchin wrote:
> > I noticed that you try to uncomment a region in a src block a # gets
> > inserted!
> >
> > #+BEGIN_SRC emacs-lisp
> > ; test
> > #+END_SRC
> >
> >
> > If you select ; test and run uncomment-region you get this:
> >
> > #+BEGIN_SRC emacs-lisp
> > # ; test
> > #+END_SRC
> >
> > It also does that in Python. Any ideas why?
>
> Because you're in org mode, not emacs-lisp or python? If you want to
> comment/uncomment codes within a src block, my guess is you would need
> to open up the blocks (C-c ') and then comment/uncomment...
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 25.0.91.1, Org release_8.3.4-626-gb62d55
>
[-- Attachment #2: Type: text/html, Size: 1870 bytes --]
next prev parent reply other threads:[~2016-03-19 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 16:44 uncommnet-region behavior in org-src blocks John Kitchin
2016-03-19 17:20 ` Eric S Fraga
2016-03-19 18:03 ` John Kitchin [this message]
2016-03-19 19:39 ` Eric S Fraga
2016-03-19 18:07 ` Ken Mankoff
2016-03-19 23:27 ` John Kitchin
2016-03-20 0:15 ` Ken Mankoff
2016-03-20 15:17 ` John Kitchin
2016-03-20 15:53 ` Ken Mankoff
2016-04-03 20:36 ` Adam Porter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ51ETr9P12fXHCpUtv6T4npH8wAYj5M3hb6X7xpbna=z5tDgg@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).