From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: src block: 'C-c C-c can do nothing useful here' if cursor on blank line
Date: Fri, 27 Jan 2017 14:29:17 -0800 [thread overview]
Message-ID: <alpine.OSX.2.20.1701271420350.2729@charles-berrys-macbook.local> (raw)
In-Reply-To: <87wpdgb4lz.fsf@kyleam.com>
On Fri, 27 Jan 2017, Kyle Meyer wrote:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> On Friday, 27 Jan 2017 at 18:44, John Hendy wrote:
>>> Perhaps this is the intended behavior, but I noticed that I go to
>>> execute a code block and get the message "C-c C-c can do nothing
>>> useful here" if I'm not on the actual src block definition or a line
>>> of code. If I'm on a blank line inside it, it doesn't execute. Here
>>> was my test:
>>
>> I have noticed this recently as well. Not sure if it was always the
>> case, mind you, but it would be nice if C-c C-c would work even when the
>> cursor is on a blank line (within a src block, that is).
>
> I think this changed with 0b6a2e241 (C-c C-c does nothing when at a
> blank line, 2013-02-15). I wasn't able to figure out the motivation for
> that change.
Nor I. Perhaps it was just an oversight.
FWIW, in `org-ctrl-c-ctrl-c'
: (looking-at-p "[ \t]*$")
could be
#+BEGIN_SRC emacs-lisp
(and
(looking-at-p "[ \t]*$")
(not (eq 'src-block (org-element-type (org-element-context))))))
#+END_SRC
without causing a lot of grief. I think `src-block' is the only
relevant case.
Chuck
next prev parent reply other threads:[~2017-01-27 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dfb1983ec7384aec9ca2172a9b27a66c@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-27 20:17 ` src block: 'C-c C-c can do nothing useful here' if cursor on blank line Eric S Fraga
2017-01-27 21:00 ` Kyle Meyer
2017-01-27 22:29 ` Charles C. Berry [this message]
2017-01-27 23:00 ` Nicolas Goaziou
2017-01-27 18:44 John Hendy
2017-01-27 20:35 ` John Kitchin
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=alpine.OSX.2.20.1701271420350.2729@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.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).