From: Rainer M Krug <Rainer@krugs.de>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Problem in tangle-mode -- WAS: Automatically adding local variables to tangled file
Date: Mon, 10 Jun 2013 12:12:25 +0200 [thread overview]
Message-ID: <8761xmgtpy.fsf_-_@krugs.de> (raw)
In-Reply-To: <87k3m21jhc.fsf@krugs.de> (Rainer M. Krug's message of "Mon, 10 Jun 2013 10:02:39 +0200")
[-- Attachment #1: Type: text/plain, Size: 2479 bytes --]
Rainer M Krug <Rainer@krugs.de> writes:
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>>>>
>>>> We already set the permission of tangled files to be executable when
>>>> they include a shebang line. Perhaps we could add an option (or change
>>>> the default) to set the permissions of tangled files to be read only.
>>>>
>>>> Perhaps this could be done using the post-tangle hook with something
>>>> like the following.
>>>>
>>>> ;; -*- emacs-lisp -*-
>>>> (defun org-babel-mark-tangled-as-read-only ()
>>>> "Mark the current file read only.
>>>> If it is executable keep it executable."
>>>> (if (= #o755 (file-modes (buffer-file-name)))
>>>> (set-file-modes (buffer-file-name) #o555)
>>>> (set-file-modes (buffer-file-name) #o444)))
>>>>
>>>> (add-hook 'org-babel-post-tangle-hook 'org-babel-mark-tangled-as-read-only)
>>>>
>>>
>>> I think that would be a good idea to add this in a way so that it is
>>> controled by a variable
>>
>> I've added a :tangle-mode header argument which may be used to control
>> the permissions of tangled files. See the manual for instructions on
>> it's usage.
>
>
> Thanks a lot. I will try it out today or tomorrow.
I did, and there is a problem with tangling multiple blocks into a
single file:
The following does not work:
,----
| #+PROPERTY: tangle-mode (identity #o444)
| #+PROPERTY: tangle ./tools.R
| * Two blocks
| Block 1
| #+begin_src R
| suitName <- function(species)
| {
| return( paste(species$layer, "suitability", sep="_") )
| }
| #+end_src
|
| Block 2
| #+begin_src R
| statDistName <- function(species){
| return( paste(species$layer, "disturbances_static", sep="_") )
| }
| #+end_src
`----
It seems that the second block can not be written, as the file is
already set to read-only.
For the moment, I exclude this setting again but will try it out as son
as it is fixed.
Cheers,
Rainer
>
> Cheers,
>
> Rainer
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-06-10 10:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 14:04 Automatically adding local variables to tangled file Rainer M Krug
2013-06-05 14:32 ` Darlan Cavalcante Moreira
2013-06-05 15:41 ` Vitalie Spinu
2013-06-05 16:15 ` Rainer M Krug
2013-06-06 7:53 ` Sebastien Vauban
2013-06-06 16:01 ` Eric Schulte
2013-06-07 7:57 ` Rainer M Krug
2013-06-07 8:32 ` Rainer M Krug
2013-06-07 10:57 ` [PATCH] Don't ask "File changed on disk" in org-babel-post-tangle-hook Vitalie Spinu
2013-06-07 13:23 ` Eric Schulte
2013-06-07 13:47 ` Rainer M Krug
2013-06-08 18:23 ` Automatically adding local variables to tangled file Eric Schulte
2013-06-08 20:59 ` Achim Gratz
2013-06-08 21:17 ` Eric Schulte
2013-06-10 8:02 ` Rainer M Krug
2013-06-10 10:12 ` Rainer M Krug [this message]
2013-06-10 15:58 ` Problem in tangle-mode -- WAS: " Eric Schulte
2013-06-11 7:25 ` BUG - Problem in tangle-mode Rainer M Krug
2013-06-11 13:09 ` Eric Schulte
2013-06-11 18:25 ` Rainer M Krug
2013-06-12 15:15 ` Rainer M Krug
2013-06-12 21:42 ` Eric Schulte
2013-06-13 7:28 ` Rainer M Krug
2013-06-10 11:32 ` SOLVED: Automatically adding local variables to tangled file Rainer M Krug
2013-06-05 17:10 ` Thorsten Jolitz
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=8761xmgtpy.fsf_-_@krugs.de \
--to=rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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).