emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Alan E. Davis" <lngndvs@gmail.com>
To: org-mode <emacs-orgmode@gnu.org>
Subject: elisp: link type isn't working
Date: Tue, 24 Jan 2012 18:00:44 -0800	[thread overview]
Message-ID: <CAF-1L2TZ0G-wJ4bKFjVxfyhyioX-CBTHB1KCnkLJn6Zf7uuiuQ@mail.gmail.com> (raw)

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

I've been using an elisp function to open an encrypted file.  I borrowed
this setup from, I think, Sacha Chua's blog.  It's worked unfailingly for
at least a couple of years, until tonight.   I keep some sensitive
information in a file, "junk.org."  when encrypted using bcrypt, the file
is renamed "junk.org.bfe."

In my init files is a little function that runs bcrypt on the file,
prompting for the password:

(defun open-encrypted-file (fname)
  (interactive "FFind file: \n")
  (let ((buf (create-file-buffer fname)))
    (shell-command
     (concat "echo " (read-passwd "Decrypt password: ") " | bcrypt -o "
fname)
     buf)
    (set-buffer buf)
    (kill-line)(kill-line)
    (toggle-read-only)
    (not-modified)b)
  )

I use a file of links as a directory to some of my projects.   In this file
is a headling that stores this link (an org file):

[[elisp:(open-encrypted-file "~/WB/org/junk.org.bfe")][PassWord]]

Anymore, as of today, when I try to run this link, the following is
received:

" Symbol's function definition is void: org-in-clocktable-p"

I don't do anything with clocks.

Can someone suggest what might be going on?

Alan Davis

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

             reply	other threads:[~2012-01-25  2:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25  2:00 Alan E. Davis [this message]
2012-01-25  4:28 ` elisp: link type isn't working Nick Dokos
2012-01-25  5:33   ` Nick Dokos

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=CAF-1L2TZ0G-wJ4bKFjVxfyhyioX-CBTHB1KCnkLJn6Zf7uuiuQ@mail.gmail.com \
    --to=lngndvs@gmail.com \
    --cc=emacs-orgmode@gnu.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).