emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org, Dror Atariah <drorata@gmail.com>
Subject: Re: Re: Update org-mode
Date: Fri, 01 Apr 2011 14:14:16 -0400	[thread overview]
Message-ID: <87bp0pj0uf.fsf@norang.ca> (raw)
In-Reply-To: <3320.1301679543@alphaville.usa.hp.com> (Nick Dokos's message of "Fri, 01 Apr 2011 13:39:03 -0400")

Nick Dokos <nicholas.dokos@hp.com> writes:

> Bernt Hansen <bernt@norang.ca> wrote:
>
>> Dror Atariah <drorata@gmail.com> writes:
>> 
>> > I tried to follow the update process described here:
>> > http://orgmode.org/worg/org-faq.html under:
>> > How do I keep current with bleeding edge development?
>> >
>> > The only change I made was the place where I checked out the new version. Instead of ~/elisp I have ~/Library/elisp.
>> >
>> > Everything went smooth, except that I had to add "sudo" before the
>> > "make install". Without the sudo, I got an "access denied"
>> > error. Anyway, at the end, I got no warnings and it seems like the
>> > process was smooth. But when I checked the version of org-mode in
>> > aquamacs it was still 6.33x
>> >
>> > I am using Emacs 23.3.1 (i386-apple-darwin9.8.0, NS apple-appkit-949.54)
>> >  of 2011-03-19 on braeburn.aquamacs.org - Aquamacs Distribution 2.2 on a mac OS 10.6.7.
>> >
>> > What should I do in order to fix it?
>> 
>> Hi Dror,
>> 
>> I track the latest git code at least weekly.  I skip the compile and
>> make install steps completely and run the code uncompiled from the git
>> repository directly.
>> 
>> I just update the code and M-x org-reload (or restart Emacs) and I'm
>> done.
>> 
>
> ... and do ``make info'' to get the doc changes, right?

Yes - I do that but not for every update - normally just when new
releases come out.

Thanks for catching this.

Regards,
Bernt

  reply	other threads:[~2011-04-01 18:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01 15:20 Update org-mode Dror Atariah
2011-04-01 16:08 ` Ian Barton
2011-04-01 16:24 ` Jambunathan K
2011-04-05 15:31   ` Dror Atariah
2011-04-05 17:03     ` Ian Barton
2011-04-01 17:08 ` Bernt Hansen
2011-04-01 17:39   ` Nick Dokos
2011-04-01 18:14     ` Bernt Hansen [this message]
2011-04-01 17:58 ` Yagnesh Raghava Yakkala
2011-04-01 19:35   ` Dror Atariah
2011-04-01 20:03     ` Nick Dokos
2011-04-03  8:12       ` Dror Atariah
2011-04-03  8:23         ` Jambunathan K
     [not found]           ` <F1BFD612-B50C-4247-8261-1058352CF0E4@gmail.com>
     [not found]             ` <81zko7hft2.fsf@gmail.com>
2011-04-03  9:47               ` Dror Atariah
2011-04-03 11:53                 ` Jambunathan K
2011-04-02 20:13 ` Christian Moe
2011-04-02 20:45   ` Achim Gratz
2011-04-02 21:02   ` Nick Dokos
2011-04-03  5:45     ` Christian Moe
2011-04-03  8:08   ` Dror Atariah
2011-04-03  9:55     ` Christian Moe
2011-04-03 10:35       ` Dror Atariah
2011-04-03 11:31     ` Achim Gratz

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=87bp0pj0uf.fsf@norang.ca \
    --to=bernt@norang.ca \
    --cc=drorata@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    /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).