From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: "Which function for creating the link?
Date: Thu, 02 Mar 2017 13:12:51 -0500 [thread overview]
Message-ID: <87innrsg2k.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 87y3wnhd62.fsf@mat.ucm.es
Uwe Brauer <oub@mat.ucm.es> writes:
> > Try
>
> > emacs -q -l /path/to/minimal.el
>
> I am not sure what minimal.el is supposed to be, but
> emacs -q I might try.
>
It may be a no-op or it may be a few lines of code, depending on how
you get your org-mode. For me, building from latest master every so
often, it's basically this:
--8<---------------cut here---------------start------------->8---
(add-to-list 'load-path "~/src/emacs/org/org-mode/lisp")
(require 'org-loaddefs)
;; not sure why I require org separately, but I guess I needed it
;; at some point - I should try without it.
(require 'org)
(add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode))
(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-cc" 'org-capture)
(global-set-key "\C-ca" 'org-agenda)
--8<---------------cut here---------------end--------------->8---
> > I don't know why you are seeing it now, but I don't think anything
> > has changed in the mairix space for years.
>
> Yes but there is a change proposed by John Kitchin which makes my suspicious
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2016-07/msg00047.html
>
I believe this was merged indeed and it may be that org-mairix.el was not updated
to follow the new convention: that may be the cause of the problem, but avoiding
the load of org-mairix should resolve it in any case.
--
Nick
next prev parent reply other threads:[~2017-03-02 21:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <97aef9c09931431a8f71427e73567741@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-02 12:19 ` "Which function for creating the link? Eric S Fraga
2017-03-02 13:20 ` Uwe Brauer
2017-03-02 15:57 ` the evil org-store-link-functions variable (was: "Which function for creating the link?) Uwe Brauer
2017-03-02 18:03 ` the evil org-store-link-functions variable Nick Dokos
2017-03-02 18:40 ` Uwe Brauer
2017-03-02 16:01 ` "Which function for creating the link? Nick Dokos
2017-03-02 16:11 ` Uwe Brauer
2017-03-02 18:12 ` Nick Dokos [this message]
2017-03-02 16:23 ` Uwe Brauer
2017-03-02 17:46 ` Eric Abrahamsen
2017-03-02 18:38 ` Uwe Brauer
2017-03-02 21:05 ` Eric Abrahamsen
[not found] ` <68f9b6ff8e1e435cb7318f4041a30c4b@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-02 16:38 ` the evil org-store-link-functions variable Eric S Fraga
2017-03-02 16:41 ` Eric S Fraga
2017-03-02 17:40 ` Uwe Brauer
2017-03-02 18:39 ` Uwe Brauer
[not found] ` <e1bc522b85a045338b8d74ef58c49c0c@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-03 6:41 ` Eric S Fraga
[not found] ` <0ad9ff963915495a8a3923603db96aac@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-02 14:24 ` "Which function for creating the link? Eric S Fraga
2017-03-02 11:38 Uwe Brauer
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=87innrsg2k.fsf@alphaville.usersys.redhat.com \
--to=ndokos@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).