From: Bernt Hansen <bernt@norang.ca>
To: emacs-orgmode@gnu.org, Bastien <bastienguerry@googlemail.com>,
Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Editing org source blocks enabled by org-src-fontify-natively?
Date: Fri, 21 Dec 2012 07:01:28 -0500 [thread overview]
Message-ID: <87txrfpqav.fsf@norang.ca> (raw)
My org-mode document http://doc.norang.ca/org-mode.org uses org source
blocks like the following for example:
--8<---------------cut here---------------start------------->8---
#+begin_src org :exports src
,* Health and Recreation
,* House Maintenance
#+end_src
--8<---------------cut here---------------end--------------->8---
My minimal emacs does not allow editing for this with C-c ' but when
org-src-fontify-natively is set to t it does.
This doesn't seem very intuitive to me -- it took me some time to
isolate what variable actually enables editing of org source blocks in
my setup.
Should it really act this way? I like editing org source blocks with
C-c ' but I think it should either be enabled all the time (so not
fontifying natively will still allow org-edit-special to edit the
block) or it should be enabled with a specific user setup similar to
--8<---------------cut here---------------start------------->8---
(add-to-list 'org-src-lang-modes (quote ("plantuml" . fundamental)))
--8<---------------cut here---------------end--------------->8---
I have the following bug reports to submit soon (hopefully later today)
related to editing source blocks:
1. source block editing on headings fail on 2nd source block
2. commas not removed
3. org-edit-special adds commas to the source repeatedly
4. Can't edit example blocks
5. Editing org src blocks doesn't work first time
Regards,
Bernt
next reply other threads:[~2012-12-21 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 12:01 Bernt Hansen [this message]
2012-12-24 0:27 ` Editing org source blocks enabled by org-src-fontify-natively? Bastien
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=87txrfpqav.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=bastienguerry@googlemail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).