From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Xebar Saram <zeltakc@gmail.com>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: comment org code block
Date: Sat, 27 Jun 2015 10:18:08 -0400 [thread overview]
Message-ID: <m2fv5di6an.fsf@vpn-128-237-147-78.library.vpn.cmu.edu> (raw)
In-Reply-To: <CAOQHXPoivs+RrNpLW7-RsZu8NKnaF_r9AhC3XnSZDBzECQsfuw@mail.gmail.com>
(defun comment-org-in-src-block ()
(interactive)
(org-edit-special)
(mark-whole-buffer)
(comment-dwim nil)
(org-edit-src-exit))
;)
Xebar Saram writes:
> wow wonderful!
> this works flawlessly when i select the region inside the code block and
> run the command.
> I wonder if any lisp wizards out there can modify Johns code and make it
> auto select all lines *inside* the current block and then comment it? could
> be useful to other people i assume.
>
> thx again
>
>
>
> On Sat, Jun 27, 2015 at 2:32 PM, John Kitchin <jkitchin@andrew.cmu.edu>
> wrote:
>
>> This seems to work for some toy examples:
>>
>> (defun comment-org-in-src-block ()
>> (interactive)
>> (org-edit-special)
>> (comment-dwim nil)
>> (org-edit-src-exit))
>>
>>
>> Xebar Saram writes:
>>
>> > Hi all
>> >
>> > i was wondering if anyone knew of a command or bind to quickly comment
>> the
>> > entire content of an org code block (with the correct comment syntax)?
>> >
>> > thx!
>> >
>> > Z
>>
>> --
>> 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
>>
--
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
prev parent reply other threads:[~2015-06-27 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 9:54 comment org code block Xebar Saram
2015-06-27 11:32 ` John Kitchin
2015-06-27 13:32 ` Xebar Saram
2015-06-27 14:18 ` John Kitchin [this message]
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=m2fv5di6an.fsf@vpn-128-237-147-78.library.vpn.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=zeltakc@gmail.com \
/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).