I want to use the package org-fstree (MELPA Link).
But in a file when I press C-c C-c at
#+BEGIN_FSTREE: ~/ I get the following error:
Symbol's function definition is void: reduce I am not sure if I installed the package correctly (this is the first time I am using MELPA). So here is all the information that I feel may be relevant:
I added the MELPA repository by adding the following to my ~/.emacs:
(when (>= emacs-major-version 24) (require 'package) (add-to-list 'package-archives ;; '("melpa" . "http://stable.melpa.org/packages/") ; many packages won't show if using stable '("melpa" . "http://melpa.milkbox.net/packages/") t)) Then I restarted Emacs. I pressed M-x list-packages and pressed i at org-fstree to mark it for installation and pressed x to complete the installation.
I got the following warnings:
In org-fstree-extract-path-from-headline: org-fstree.el:271:21:Warning: reference to free variable `org-fstree-heading-regexp' In end of data: org-fstree.el:311:1:Warning: the following functions are not known to be defined: reduce, org-columns-quit Then I added the following lines to my ~/.emacs:
;; org-fstree (add-to-list 'load-path "~/.emacs.d/elpa/org-fstree-20090723.819/") (require 'org-fstree) I got the above mentioned error after these steps.
Please advice me on what to do?
reducewithcl-reduceinorg-fstree.el. Furthermore, you should not need anything directly related to that package in your init file. Better add the comment line;;;###autoloadbefore the two hooks at the end of the library and before the definitions of the hooked functionsorg-fstree-show-entry-maybeandorg-fstree-apply-maybe. Byte-compile the library afterwards.package-install'd (or equivalent).(package-generate-autoloads "org-fstree" (current-directory))called from withinorg-fstree.el(i.e., withdefault-directoryset to the package directory) should do.;;;###autoloaddo? 2. How should one byte-compile the library? 3. The point that @phils raised - what does that mean? 4. How does your comment to @phils solve the above problem? And thanks for raising the issue on github.