emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: bbdb-info@lists.sourceforge.net
Cc: emacs-orgmode@gnu.org
Subject: for your amusement
Date: Thu, 02 Aug 2012 17:41:39 +0800	[thread overview]
Message-ID: <87ipd1d418.fsf@ericabrahamsen.net> (raw)


For a while I've had a function for creating textual citations of my
BBDB contacts, that relied on `bbdb-dwim-mail'. I expanded that to make
use of org's link syntax, so that you can insert a BBDB link on the
spot, without having to first visit your *BBDB* buffer and create a link
there. I find this pretty helpful.

If anyone can think of more formatting possibilities, "formats" could be
broken out into a variable.

Incidentally, I'm using `ido-everywhere', and would like to write this
function so that it didn't _rely_ on ido, but made use of ido when
`ido-everywhere' was true. Ie, I'd like to replace the
`ido-completing-read' calls with something more generic that still made
use of ido when it was turned on. Any suggestions?

Eric

--8<---------------cut here---------------start------------->8---
(defun cite-bbdb-contact (name)
  (interactive "sName (regexp): ")
  (let ((rec)
	(records (bbdb-search (bbdb-records) name name name nil nil))
	(formats '(("text" . bbdb-dwim-mail)
		   ("orglink" . (lambda (x)
				  (let ((name (bbdb-record-name x)))
				    (format "[[%s][%s]]"
					    (org-make-link "bbdb:" name) name)))))))
    (if (= (length records) 1)
	(setq rec (car records))
      (if (zerop (length records))
	  (error "No matching records")
	(setq rec
	      (let ((int-name
		     (ido-completing-read "Pick one: "
					  (mapcar 'bbdb-record-name records))))
		(car (bbdb-search (bbdb-records) int-name))))))
    (let ((func (cdr (assoc (ido-completing-read
			     "Format: " (mapcar #'car formats)) formats))))
      (insert (funcall func rec)))))
--8<---------------cut here---------------end--------------->8---


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/

             reply	other threads:[~2012-08-02  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02  9:41 Eric Abrahamsen [this message]
2014-02-20 10:55 ` for your amusement Nicolas Richard
2014-02-20 11:29   ` Eric Abrahamsen
2014-02-20 12:08     ` Nicolas Richard
2014-02-20 13:42       ` Eric Abrahamsen

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=87ipd1d418.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=bbdb-info@lists.sourceforge.net \
    --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).