From: "Loris Bennett" <loris.bennett@fu-berlin.de>
To: emacs-orgmode@gnu.org
Cc: info-gnus-english@gnu.org
Subject: Re: (gnus-icalendar-org-setup) not evaluated in .emacs?
Date: Thu, 14 Sep 2017 16:02:19 +0200 [thread overview]
Message-ID: <871sn91iqc.fsf@hornfels.zedat.fu-berlin.de> (raw)
In-Reply-To: 87wp517kut.fsf@t3610
Eric S Fraga <esflists@gmail.com> writes:
> On Thursday, 14 Sep 2017 at 09:56, Loris Bennett wrote:
>> Hi,
>>
>> I have the following in my .emacs:
>>
>> (require 'gnus-icalendar)
>> (gnus-icalendar-setup)
>> (gnus-icalendar-org-setup)
>
> I have one setting alongside these:
>
> (setq gnus-icalendar-org-capture-file "...path to my diary.org")
>
> I wonder whether gnus needs this to be defined for it to show all the
> buttons? Maybe check the value of this before and after?
>
> I always see all the buttons (I think).
Rereading this, I decided to move the settings out from the Customize
block to before call to gnus-icalendar-org-setup:
(require 'gnus-icalendar)
(setq gnus-icalendar-org-capture-file "~/git/org.git/gtd.org")
(setq gnus-icalendar-org-capture-headline (quote ("Exchange")))
(gnus-icalendar-setup)
(gnus-icalendar-org-setup)
Now I get all the buttons first time round and didn't have to resort to
a flaky hack, so thanks, Eric.
But should this kind of ordering dependency happen? Or should my
Customize block just be at the beginning of my .emacs rather than at the
end?
Cheers,
Loris
--
This signature is currently under construction.
next prev parent reply other threads:[~2017-09-14 14:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 7:56 (gnus-icalendar-org-setup) not evaluated in .emacs? Loris Bennett
2017-09-14 8:19 ` Eric S Fraga
2017-09-14 9:11 ` Loris Bennett
2017-09-14 9:29 ` Eric S Fraga
2017-09-14 12:34 ` Loris Bennett
2017-09-14 14:02 ` Loris Bennett [this message]
2017-09-15 18:00 ` Matt Lundin
2017-09-19 9:05 ` Eric S Fraga
2017-09-19 9:51 ` Loris Bennett
2017-09-19 22:11 ` Tim Cross
2017-09-20 7:33 ` Loris Bennett
2017-09-20 22:32 ` Nick Dokos
2017-09-20 13:49 ` Lars-Johan Liman
2017-09-20 19:25 ` Eric S Fraga
2017-09-20 19:34 ` Thomas S. Dye
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=871sn91iqc.fsf@hornfels.zedat.fu-berlin.de \
--to=loris.bennett@fu-berlin.de \
--cc=emacs-orgmode@gnu.org \
--cc=info-gnus-english@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).