From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Chunyang Xu <mail@xuchunyang.me>
Cc: emacs-orgmode@gnu.org
Subject: Re: Asks user what to do with each tangle-file before overriding?
Date: Sun, 18 Jun 2017 09:23:29 +0200 [thread overview]
Message-ID: <87mv95daj2.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2o9toldr3.fsf@xuchunyang.me> (Chunyang Xu's message of "Fri, 16 Jun 2017 13:09:52 +0800")
Hello,
Chunyang Xu <mail@xuchunyang.me> writes:
> Currently 'C-c C-v C-t' ('org-babel-tangle') simply overrides existing
> tangle-file, I would like org to ask me what to do? such as
>
> a) yes (override)
> b) no (don't override)
> c) show the diff then ask again
>
> In addition, if there is no diff (i.e., having the same contents), user
> can choose (e.g., via a user option) to simply pass this tangle-file
> without overriding.
I don't think it is a good idea to have file that can be both edited
manually, and auto-generated (i.e., tangled). Or, to put it differently,
the idea behind tangling is that you only handle the code block, not the
file itself.
> I am asking for this feature because I am storing my dotfiles in a
> single Org file [1], and when I change my Bash configuration then
> tangle, I don't need to worry if Org is tangling other configuration
> correctly, especially ~/.ssh/id_rsa and ~/.authinfo.gpg. I would rather
> leave these unchanged files than override (even only file modification
> timestamps are updated).
You could add :tangle no on top of the sensitive blocks and remove the
flag only when you want to generate them.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-06-18 7:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 5:09 Asks user what to do with each tangle-file before overriding? Chunyang Xu
2017-06-18 7:23 ` Nicolas Goaziou [this message]
2017-06-18 11:21 ` Chunyang Xu
2017-06-18 17:12 ` Charles C. Berry
2017-06-19 4:57 ` Chunyang Xu
2017-06-19 5:06 ` numbchild
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv95daj2.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mail@xuchunyang.me \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.