Hello. This is my Org-from-Git recipe:
After you've cloned the repository (master branch), run "make" and
then edit the "local.mk" file. There you'll find a variable named
"prefix"; change it according to your Emacs installation.
In my setup, Emacs files live in /usr/share/emacs/ so I leave "pref
Marcin Borkowski writes:
But one problem remains: the info manual is still taken from
Emacs, not from the newest Org.
Did you try to do 'make install-info'?
--
Jorge.
On 2015-05-14, at 15:04, Marcin Borkowski wrote:
> I wanted to upgrade Org, using the package manager, and it failed.
> Being accustomed to the package manager failing (for whatever reason),
> I deleted Org-mode and decided to go with the git version. I did
> a clone, then make, make doc and su
Hi all,
I wanted to upgrade Org, using the package manager, and it failed.
Being accustomed to the package manager failing (for whatever reason),
I deleted Org-mode and decided to go with the git version. I did
a clone, then make, make doc and sudo make install, but M-x org-version
says its
Org-
Vicente Vera writes:
> - M-x info shows the updated info manual which now resides in
> /usr/local/share/info (I think it replaced the built-in manual?).
That depends on where your system installation put it originally. But
even if it was originally installed someplace else, it would now find
the
Jorge A. Alfaro-Murillo writes:
> Why? emacs/lisp points to org-mode/lisp, if I update org it updates in
> its org-mode repo, what can I break?
All the derivative files that were lifted out of this directory into
other places, like cus-load and loaddefs. Again, Emacs doesn't treat
any of its buil
Thank you for your replies, I think i'm beginning to understand the
process. These are the changes I made to local.mk:
prefix = /usr/local/share
datadir = /usr/local/share/emacs/24.4.50/etc/org (actually, this directory
belongs to the built-in Org installation)
Then:
$ make
$ sudo make install
Achim Gratz writes:
> It doesn't work, you just haven't run into a problem that you can
> positively identify with that habit yet. You'd need to re-build Emacs
> each time you update Org if you wanted it to work.
Why? emacs/lisp points to org-mode/lisp, if I update org it updates in
its org-mo
Jorge A. Alfaro-Murillo writes:
> For org, I once read a discussion in this list about not doing this but
> that a lot of people do it, it keeps working for me, so I keep doing it.
It doesn't work, you just haven't run into a problem that you can
positively identify with that habit yet. You'd nee
Miguel Ruiz writes:
> Minimal sequence for me is: make clean & git pull & make autoloads &
> make info
You can simplify this to a just "make" by defining your own default
target in local.mk like this:
my_default_target: up0 uncompiled info
(that's a tab after the colon).
Regards,
Achim.
--
+<
Vicente Vera writes:
> Hello. I'm quite confused with the installation options.
>
> Recently started out a Debian base system and compiled Emacs from the
> bzr repository. That came out fine, so I ran 'make install' and now
> Emacs 24.4.50 sits in /usr/local/bin, /usr/local/share, etc.
>
> I want
This is my setup in .emacs; it runs without problems version after version. You are encouraged to simplify the path schema of org-mode branches I use. Minimal sequence for me is: make clean & git pull & make autoloads & make info;; .emacs begins activate debugging (setq debug-on-error
Vicente Vera writes:
> Thanks for your reply. Which one is the default install method? If
> it's 'make install',
I'd go for "make up2" (which ends up doing make install if the tests are
passing) if you want minimum involvement, but it's your choice.
> do i need to tweak local.mk because of the
>
On Tue, Jul 1, 2014 at 12:21 PM, Achim Gratz wrote:
> John Hendy writes:
>> Did you search around a bit? There's lots of posts with people's
>> setups. You certainly *can* install over the top of the Org that came
>> with your version of Emacs (pointing it to install to
>> /usr/local/share, I supp
It seems i'm flooding John's inbox trying to send back this message into
the discussion. I'm deeply sorry for that.
I did what John suggested:
- git clone...
- cd to the repository
- make (which i think does two things, byte-compilation and generating
org-loaddefs.el)
- add lisp dir to load-path
John Hendy writes:
> Did you search around a bit? There's lots of posts with people's
> setups. You certainly *can* install over the top of the Org that came
> with your version of Emacs (pointing it to install to
> /usr/local/share, I suppose), though I've never gone that route.
In any case, this
On Mon, Jun 30, 2014 at 5:44 PM, Vicente Vera wrote:
> Hello. I'm quite confused with the installation options.
>
> Recently started out a Debian base system and compiled Emacs from the bzr
> repository. That came out fine, so I ran 'make install' and now Emacs
> 24.4.50 sits in /usr/local/bin, /u
Hello. I'm quite confused with the installation options.
Recently started out a Debian base system and compiled Emacs from the bzr
repository. That came out fine, so I ran 'make install' and now Emacs
24.4.50 sits in /usr/local/bin, /usr/local/share, etc.
I want to install the master branch of or
18 matches
Mail list logo
