emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Xavier Maillard <xavier@maillard.im>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Define org-capture-templates with variables via customize
Date: Sat, 04 Apr 2015 23:54:41 +0200	[thread overview]
Message-ID: <867ftr7e5a.fsf@kcals2.maillard.im> (raw)
In-Reply-To: <87ego2x4iq.fsf@nicolasgoaziou.fr>


Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Xavier Maillard <xavier@maillard.im> writes:
>
>> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>>
>>> Hello,
>>>
>>> Nick Dokos <ndokos@gmail.com> writes:
>>>
>>>> Trying to just read Xavier's email message in Gnus, I get the following
>>>> backtrace (with unprintable characters replaced by periods) - to me, this
>>>> looks like a bug somewhere, but not sure where:
>>>>
>>>> Debugger entered--Lisp error: (error "Before first headline at position 114 in buffer *fontification*<2>")
>>>
>>> Fixed in c1a744659d2b44c067ecb195b3e5d51e837bddd1. Thank you.
>>
>> Glad you fixed that bug. Now that I am visible, is there any way to achieve what I need
>> ? :D
>
> I don't think so. You are trying to mix two different concepts.
> Customize is self-contained and generally helps users to avoid Elisp.
> OTOH when you're defining a new variable, you embrace Elisp.

I do embrace Elisp from time to time but I do not want to clutter my
init files :)

Ok, sounds like there is something I can /hack/ to permit such thing
then.

Update: I finally got it running as I wanted to through an ugly hack.

Regards

-- Xavier.

  reply	other threads:[~2015-04-04 21:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30  4:07 Xavier Maillard
2015-03-30 14:49 ` Nick Dokos
2015-03-31 14:15   ` Nicolas Goaziou
2015-04-02  5:32     ` Xavier Maillard
2015-04-02  9:29       ` Nicolas Goaziou
2015-04-04 21:54         ` Xavier Maillard [this message]
2015-09-30 17:08           ` Nicolas Girard

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=867ftr7e5a.fsf@kcals2.maillard.im \
    --to=xavier@maillard.im \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=ndokos@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).