From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: automatic tangle
Date: Wed, 11 Jan 2012 21:37:29 +0100 [thread overview]
Message-ID: <807h0y6kmu.fsf@somewhere.org> (raw)
In-Reply-To: CALPHr6z_vk3aojF=O6YqKs4VpahQzO1qDKCxcC9EtevbKPG9yw@mail.gmail.com
Hi András,
András Major wrote:
>> I have the impression it's already there: if you edit your code directly in
>> the Org buffer, without opening an indirect buffer, the only thing you have to
>> do is:
>
> That's precisely what I want to avoid. I'd like to use the
> language-specific indentation and highlighting using the indirect
> buffer. Basically, what I'm after is a quick keyboard command that
> tangles the entire file while I'm in the indirect buffer.
I do have:
- language-specific indentation and
- highlighting
in the Org buffer itself...
Just put this in your .emacs file:
#+begin_src emacs-lisp
;; fontify code in code blocks
(setq org-src-fontify-natively t)
;; preserve spaces and `tab' characters in source code blocks
(setq org-src-preserve-indentation t)
;; same effect for `tab' as in the language major mode buffer
(setq org-src-tab-acts-natively t)
#+end_src
>> Another option is the opposite: edit in your tangled file, and untangle when
>> you feel it's the right time.
>
> I don't think that's practical, since each file can be built up from
> several code blocks.
That's not a problem: if you turn on the "comments", you'll see every chunked
delimited in the tangled buffer.
> In any case, it would be too easy to lose code that way by accidentally
> tangling while there are changes in the source code file.
If you play within both files, yes, that's a real potential danger.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-01-11 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 19:21 automatic tangle András Major
2012-01-11 20:37 ` Sebastien Vauban [this message]
2012-01-14 17:41 ` Eric Schulte
2012-01-17 8:06 ` András Major
2012-01-20 17:54 ` Eric Schulte
-- strict thread matches above, loose matches on Subject: below --
2012-01-11 14:36 András Major
2012-01-11 15:18 ` Sebastien Vauban
2012-01-11 22:39 ` Eric S Fraga
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=807h0y6kmu.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).