emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Torsten Wagner <torsten.wagner@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>,
	Charles Berry <ccberry@ucsd.edu>
Subject: Re: Where does org-mode elisp hacking go?
Date: Fri, 15 Mar 2013 14:50:55 +0100	[thread overview]
Message-ID: <CAPaq-gM1z8MamOO-gZ2Ua_bPkbo_tMVq5kMgZS1uDfmB0GJr0A@mail.gmail.com> (raw)
In-Reply-To: <87ppz1da97.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]

Hi Eric,

sorry for the last two spams. Believe it or not, I fell asleep last night,
during typing an answer and somehow managed to send twice a message ;)
People should not take there smartphones to bed.

Sounds dangerous to me.  I often place init.el files into
> sub-directories which require project specific customization.  You may
> also want to look at (info "(elisp)Directory Local Variables") for
> adding setting based on the working directory.
>
>
Why does this sound dangerous. Encrypted babel blocks could not be modified
and even not been read without user authentication. Furthermore, even if I
use a org-file from someone else, I would have to authorize the execution
by decryption of the block. Thus, its unlikely someone executes something
by accident.
Beside of the autostart, encrypted source code blocks might make sens too,
if sensitive data might be part of the block. E.g. username and login
credentials to login into a certain service.

I do not want to hijack this thread. It was just an idea which sounded to
me rather easy to implement, since the core features are all there already.
Feel free, to set it on the crazy ideas list, if you feel that it is not a
good idea  ;)

All the best

Torsten

[-- Attachment #2: Type: text/html, Size: 1730 bytes --]

      reply	other threads:[~2013-03-15 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 19:53 Where does org-mode elisp hacking go? Lawrence Bottorff
2013-03-13 22:38 ` Charles Berry
2013-03-14  9:52   ` Torsten Wagner
2013-03-14 19:57     ` Eric Schulte
2013-03-15 13:50       ` Torsten Wagner [this message]

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=CAPaq-gM1z8MamOO-gZ2Ua_bPkbo_tMVq5kMgZS1uDfmB0GJr0A@mail.gmail.com \
    --to=torsten.wagner@gmail.com \
    --cc=ccberry@ucsd.edu \
    --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).