Package Details: emacs-org-mode 9.1.11-1

Git Clone URL: (read-only)
Package Base: emacs-org-mode
Description: Emacs Org Mode
Upstream URL:
Keywords: emacs org-mode
Licenses: GPL
Submitter: tgirod
Maintainer: haawda
Last Packager: haawda
Votes: 101
Popularity: 0.000259
First Submitted: 2008-07-02 18:45
Last Updated: 2018-04-23 15:00

Latest Comments

haawda commented on 2018-04-02 15:35

Adopted and updated.

drdissector commented on 2017-03-02 01:06

Hi all,

Updated to 9.0.5 (latest version).


drdissector commented on 2017-02-10 01:38

Thanks Milouse for your enquiry,

I will update at the end of next week.

Work gets in the way of life.

Have a great day!


milouse commented on 2017-02-08 21:14

Is there any reason you don't bump yet to the version 9.0.4?

milouse commented on 2014-08-20 07:10

Thanks @domanov for your comment on 2014-08-06 07:39. I was seeing the same thing as @cedricmc, but was too lazy to asks. Much clear now why we see this warning.

And of course thanks for your awesome packaging work and reactivity :)

domanov commented on 2014-08-19 11:24

Bumped to the 8.2.7c. Enjoy!

abstracity commented on 2014-08-19 10:44

Emacs 8.2.7c is out, "a bugfix release:"

domanov commented on 2014-08-06 07:39

Yes @cedricmc, this warning is ignorable since it is only due to the presence of compiled lisp, for building which the original source directory needs to be stored in some lisp variable at compile time (think about autogenerated makefiles) and then gets logged in the .elc files.
The 2 autogenerated files "org-version" and "org-loaddefs" take care of this. Every emacs package having .elc files will give out this warning, nothing to do about it, and completely safe.

cedricmc commented on 2014-08-06 01:47

With a fully updated system, I get:

WARNING: Package contains reference to $pkgdir

In fact, ``grep -R "$(pwd)/pkg" src/'' gives

src/org-8.2.7b/lisp/org-version.el:(defvar org-odt-data-dir "$(pwd)/pkg/emacs-org-mode/usr/share/emacs/etc/org"
src/org-8.2.7b/lisp/org-loaddefs.el:(defvar org-odt-data-dir "$(pwd)/pkg/emacs-org-mode/usr/share/emacs/etc/org" "\

Is this normal?

domanov commented on 2014-07-25 18:28

Well, I've always used makepkg --source to do my stuff, I missed that now there is need for .AURINFO and that mkaurball takes care of that. I found it out as I tried to upload the srcball to AUR.

I then just did a "pacman -Ss mkaurball" and nothing came up. Then "packer -Ss mkaurball and it gave me "pkgbuild-introspection-git" - so I just installed that.

haawda commented on 2014-07-25 18:22

pkgbuild-introspection from [community] did not work?

domanov commented on 2014-07-25 10:06

Bumped to the "new" 8.2.7b. Also had to install pkgbuild-introspection-git from AUR to get "mkaurball". I somehow missed that. Enjoy!

ckruse commented on 2014-07-25 08:13

Could you do an upgrade to 8.2.7b?

kgunders commented on 2014-05-20 17:09

I think the version you get from melpa or's ELPA archive is the developement version. So if you want stable you may well be better off using the arch/aur package. AUR and pacman also provide better package management w.r.t. managing version rollbacks. Since org is Emacs built-in, once you uprade via ELPA there's no way to roll back, other than manually deleting the updated package from e.g. ~/.emacs.d/elpa/

In short, ELPA is kind of lame as a package management system. RSM is anal about license (I'm into FOSS but not a license nazi, MIT, BSD, Apache - it's all good) and dead tree copyright assignments so many .el authors don't bother with the hassle of submitting to gnu's elpa archives. So rather than elpa being authoritative source for one stop shopping, it's outdated and pretty much useless. Hence most .el authors are opting for second party repos such as MELPA & Marmalade. The main benefit of Emacs package system, as far as I can discern, is for users who don't have requisite permissions for installing packages system wide. Also, that having all your emacs extensions/tweaks under e.g. ~/.emacs.d makes them more portable for end user - just copy that dir and subdir to any machine.

I'm far from emacs guru so take all of above with dose of salt. I did, however, inquire about this packaging mess on #emacs recently and it seems the gurus' eschew elpa, etc. and just manage their packages manually, most of which seem to have github repos, in an appropriate subdir under git control. This seems like a lot of work if you have lots of stuff but I guess on reason the gurus are gurus is that they live in emacs.

Hope this helps some.

domanov commented on 2014-04-22 14:41

Bumped to the new 8.2.6. Enjoy!

donniezazen commented on 2013-11-08 15:15

Thanks @domanov. Great explanation.

domanov commented on 2013-11-08 15:04

@donnie: I personally prefer to try and keep all of the installed software on my different (arch) machines under control of pacman. At least if you need to install the packages system-wide, and not only in user's home. That's the beauty of arch: you then run "pacman|packer|yaourt -Syu" and you live happily everafter, everything gets updated in one place. For me this is a great added value since I have 4 or 5 arch machines that need to be kept in line. This may be of course different for you.

The ELPA org package itself, what you would install from inside emacs, is in the end just the same, I guess, only pacman doesn't know anything about it and you probably need to update it manually (from inside emacs, or with a specific batch command or...) at every release. For me that would be just cumbersome, adding more complexity to my ecosystem. I never used ELPA, though, so here I might be wrong.

donniezazen commented on 2013-11-08 14:23

What do you think about "M-x package-install RET org" vs installation through this package? I am new to Emacs/Org.

domanov commented on 2013-11-08 10:37

Bumped to the brand new bug-fix release 8.2.2. Enjoy!

troydwill commented on 2013-07-15 18:57

July 15, 2013 - I updated to version 8.0.6 by changing pkgver and md5sums in the PKGBUILD.

domanov commented on 2013-05-31 10:09

@abstracity Thnaks for pointing that out. I updated to the new version and changed the emacs-org-mode.install according to the new load mechanism. It now displays a message for noth new installs and for updates.

abstracity commented on 2013-05-31 01:35

(require 'org-install) is no longer necessary since 7.9.3:

abstracity commented on 2013-05-14 18:06

Thanks for updating!

domanov commented on 2013-04-19 11:19

And welcome to the new major 8.0 release of org-mode! Huge improvements, new f-a-n-t-a-s-t-i-c exporter, lots of changes and lots of incompatible changes: read the changelog, abandon remember.el, help the devs testing and squashing bugs away. Enjoy and keep orging!

domanov commented on 2013-03-18 16:43

Bumped to 7.9.4. Enjoy!!

domanov commented on 2013-02-21 16:06

Bumped to the 7.9.3e version, just as release number 2. Now it compiles again. Also taken care of the right version shipped with current emacs (thanks delexi for pointing that out).

Anonymous comment on 2013-01-19 22:36

After installation with pacman finishes a note is displayed containing the wrong org-mode version shipped with emacs. It says:

NOTE: info documentation for emacs-org-mode goes now as 'orgmode' in /usr/share/info,
It does NOT replace the 'org' info files shipped with emacs:
$ info orgmode ## this version
$ info org ## emacs' org version (currently 6.21)

But it should be "emacs' org version (currently 7.8.11)". It's just a minor thing but i wanted to point it anyway.

domanov commented on 2012-09-19 15:57

Thanks CanerCandan for the suggestion. Fixed the /usr/share issue; also bumped to the latest 7.9.1. I had to change a little the PKGBUILD to achieve the info documentation to be stored under "orgmode" and not overwrite the "org" info shipped with emacs.
I only did a quick testing (not at all on i686).


CanerCandan commented on 2012-09-15 13:11

To fix this temporal issue, you just need to replace at the line 27, this line:

make prefix="${pkgdir}/usr" install || return 1

by this:

make prefix="${pkgdir}/usr/share" install || return 1

chneukirchen commented on 2012-09-10 13:29

Why does this package install into /usr/emacs? Everything should go to /usr/share/emacs instead.

domanov commented on 2012-08-30 02:24

Bumped the 7.9 version, which is out since last week. Disclaimer: I just quickly changed the PKGBUILD to reflect the new naming of tar file, but didn't have time to test the otherwise numerous changes. I am further away from home for the next 2 weeks. So please help in testing and reporting problems, or just be patient to wait until I am back from holiday! Keep orging.

domanov commented on 2012-08-30 02:23

Bumped the 7.9 version, which is out since last week. Disclaimer: I just quickly changed the PKGBUILD according to reflect the change in naming of tar file, but didn't have time to test otherwise the numerous changes, since I am away for the next 2 weeks. So please help in testing and reporting it, or just be patient to wait until I am back from holiday! Keep orging.

listx commented on 2012-07-10 15:48

@domanov: Sorry to respond so late (forgot to click on "Notify"...), but here is my makepkg.conf:

I guess it's sort of a non-issue now, since you've changed it to $srcdir.


domanov commented on 2012-05-21 14:00

@listdata, I had checked on 4 different systems, i686 as well as x86_64, and had no problem with the old "${startdir}/src".
Have you got exotic makeflags?
In every case, I replaced the old expression with $srcdir and $pkgdir as advised in the PKGBUILD man page.

listx commented on 2012-05-21 08:57

I have to change the "${startdir}/src" to "${srcdir}" for build() and package() to work. Is it just me?

domanov commented on 2012-04-03 09:38

Thank you exaos! Fixed.

Anonymous comment on 2012-04-02 23:33

One error:

domanov commented on 2012-04-02 16:21

Upgraded to 7.8.08.

PLEASE NOTE: From now on I'll purposedly wait one or two days from the upstrem release to upgrade the AUR packages, since these fix-only releases upstream - like the .07 - are regularly very quickly superseded. The purpose of this package is to provide stable releases.

So, please, don't mark the package immediately outdated!

Anonymous comment on 2012-03-21 13:05

It was simply a coincidence. I happened to attempt to upgrade from 7.8.03 to 7.8.04 when 7.8.04 was no longer available. Thanks for updating the PKGBUILD.

haawda commented on 2012-03-20 22:56

Wow, you are quick. Git merge was 6 hours ago.

Anonymous comment on 2012-03-20 22:05

I just flagged this out of date. I don't really care that much about running the very latest org-mode version, but 7.8.04 no longer builds. curl gives me a 404 when trying to download the source, and I suspect that this is because the upstream version is now 7.8.06 and they don't provide downloads of 7.8.04 any more.

domanov commented on 2011-07-29 12:51

New 7.7 is out. Enjoy.

domanov commented on 2011-07-11 01:12

Updated, also changed arch to 'any'. Enjoy!

L42y commented on 2011-07-07 07:26

please update to 7.6

Anonymous comment on 2011-04-25 12:06

Shouldnt this be arch=('any') ?

Anonymous comment on 2011-03-07 17:20


domanov commented on 2011-03-07 15:15

Updated to version 7.5. Enjoy!

domanov commented on 2010-12-13 14:39

I did not test thoroughly, but with my setup everything seems to work like before...

domanov commented on 2010-12-13 14:36 is unreachable right now, I'll try and check later this babel problem

domanov commented on 2010-12-13 14:27 is unreachable right now, I'll try and check later this babel problem

Anonymous comment on 2010-12-13 14:01

As of org 7.4 from their site, it certainly seems that none of my R org files are working. I can do C-c C-c run the blocks in the R process, but the results don't gwet included into the pdf or .tex file, even example or tutorial org files from the net. However I'm yet to try one more configuration before I'm stumped.

domanov commented on 2010-12-13 12:56

@ben9250 : I didn't test babel for this release. Have you a babel/R example which used to work and now doesn't work anymore?

Anonymous comment on 2010-12-13 12:44

Is this good for use with R code? I've been trying top get the latest 7.4 installed manually, and either it's my fault for putting it in the wrong location or something is up with babel. Where abouts does this package install to? I see an option for replacing the stock info files.

haawda commented on 2010-11-02 17:58

jdarnold, you will get this warning for all emacs packages that include byte-compiled files (*.elc). Open such a file and you see why. It is ignorable and not the package author's fault.

haawda commented on 2010-11-02 17:10

jdarnold, you will get this warning for all emacs packages that include byte-compiled files (*.elc). Open such a file and you see why. It is ignorable and not the package author's fault.

jdarnold commented on 2010-11-02 16:28

I'm getting an error when updating:

==> WARNING: Package contains reference to $srcdir

domanov commented on 2010-11-01 14:15

@ngz : you flagged the package as out-of-date, but it's not the case (just checked on Note that this package is the tarballed release, not the git version nor the ELPA package. So I am dropping the flag.

domanov commented on 2010-07-22 13:00

As usual, after a major version, the org-mode package is including bugfixes and minor modifications, so that a new distribution is available every couple of days or even more frequently. This is a measure of the active development upstream ;)
To avoid too frequent updates, I will check upstream only every 4-5 days. Please comment here or PM me if you strongly need the newest bump.

domanov commented on 2010-07-19 11:47

Brand new 7.01 org-mode!! Org-babel made into the main tree, pleas read user visible changes at (I also added a reminder to the .install). Have fun!

domanov commented on 2010-04-06 08:56

Updated to version 6.35 - please read user visible changes at