My problem was because I had a line
(require 'org-publish)
It would be super if there was a way to clearly flag this as an error after
an upgrade. Maybe renamed files should have old skeleton files that produce
an error indicating the new file name?
On Thu, Jan 2, 2014 at 10:43 PM, Sharon
On Thu, Jan 2, 2014 at 2:06 AM, Justin Gordon wrote:
> Achim Gratz nexgo.de> writes:
>
>>
>> John Hendy writes:
>> > Then again, is Worg saying that if `M-x org-version` outputs the
>> > "correct" answer... we're all set and there's nothing to worry about?
>>
>> The output of org-version is deter
On Thu, 2 Jan 2014 08:06:46 + (UTC)
Justin Gordon wrote:
> Achim Gratz nexgo.de> writes:
>
> >
> > John Hendy writes:
> > > Then again, is Worg saying that if `M-x org-version` outputs the
> > > "correct" answer... we're all set and there's nothing to worry
> > > about?
> >
> > The output
Achim Gratz nexgo.de> writes:
>
> John Hendy writes:
> > Then again, is Worg saying that if `M-x org-version` outputs the
> > "correct" answer... we're all set and there's nothing to worry about?
>
> The output of org-version is determined essentially by checking for two
> files from the instal
John Hendy writes:
> I'm with you so far. But if all of Org lives in /path/to/org.git/lisp,
> what's to go wrong if it's there vs. /system/path/site-lisp?
It is only "there" when you've built Org and whenever you do something
in Git, it's "gone", only that you might not see that. Having Org
insta
On Sun, Sep 8, 2013 at 11:41 AM, Achim Gratz wrote:
> John Hendy writes:
>> Could you elaborate on this? I'd always thought the exact opposite due
>> to being burned in the past by stale junk littered around /usr/lib,
>> /usr/bin, /usr/local/[bin/sbin]. Thus, for some things, I prefer to
>> run th
John Hendy writes:
> Then again, is Worg saying that if `M-x org-version` outputs the
> "correct" answer... we're all set and there's nothing to worry about?
The output of org-version is determined essentially by checking for two
files from the installation and comparing where they would be loaded
John Hendy writes:
> Could you elaborate on this? I'd always thought the exact opposite due
> to being burned in the past by stale junk littered around /usr/lib,
> /usr/bin, /usr/local/[bin/sbin]. Thus, for some things, I prefer to
> run them from the git repository since I know where they'll be vs
On Sun, Sep 8, 2013 at 10:10 AM, Suvayu Ali wrote:
> On Sun, Sep 08, 2013 at 09:37:23AM -0500, John Hendy wrote:
>>
>> On that note, is there a recommended "diagnosis" route someone could
>> recommend other than simply `M-x org-version`? Is it possible to get,
>> e.g. 8.0.7, from that command but
On Sun, Sep 08, 2013 at 09:37:23AM -0500, John Hendy wrote:
>
> On that note, is there a recommended "diagnosis" route someone could
> recommend other than simply `M-x org-version`? Is it possible to get,
> e.g. 8.0.7, from that command but be pulling from mixed org locations
> (org shipped with E
On Sun, Sep 8, 2013 at 12:40 AM, adam wrote:
>
>> -Original Message-
>> From: Suvayu Ali
>> To: emacs-orgmode@gnu.org
>> Subject: Re: [O] mixed orgmode installation
>> Date: Wed, 4 Sep 2013 17:07:49 +0200
>>
>> On Wed, Sep 04, 2013 at 04:
On Wed, Sep 4, 2013 at 2:20 PM, Achim Gratz wrote:
> Johannes Rainer writes:
>> is there a "clean" way to disable the built in org from emacs?
>
> Short answer: no.
>
>> I'm loading org mode from git externally, but newer emacs always come
>> with org mode included.
>
> That's not a problem as lon
> -Original Message-
> From: Suvayu Ali
> To: emacs-orgmode@gnu.org
> Subject: Re: [O] mixed orgmode installation
> Date: Wed, 4 Sep 2013 17:07:49 +0200
>
> On Wed, Sep 04, 2013 at 04:52:34PM +0200, Johannes Rainer wrote:
> > hm, that's an option.
> &
Johannes Rainer writes:
> is there a "clean" way to disable the built in org from emacs?
Short answer: no.
> I'm loading org mode from git externally, but newer emacs always come
> with org mode included.
That's not a problem as long as you set up the load-path to point to the
install made via G
On Wed, Sep 4, 2013 at 4:19 PM, Thorsten Jolitz wrote:
> Johannes Rainer writes:
>
> > hi all!
> >
> > is there a "clean" way to disable the built in org from emacs? I'm
> > loading org mode from git externally, but newer emacs always come with
> > org mode included. would just deleting the org
Johannes Rainer writes:
> hi all!
>
> is there a "clean" way to disable the built in org from emacs? I'm
> loading org mode from git externally, but newer emacs always come with
> org mode included. would just deleting the org folder in the emacs (am
> using Emacs.app on mac) installation help?
>
hi all!
is there a "clean" way to disable the built in org from emacs? I'm loading
org mode from git externally, but newer emacs always come with org mode
included.
would just deleting the org folder in the emacs (am using Emacs.app on mac)
installation help?
thanks in advance!
On Wed, Sep 04, 2013 at 04:52:34PM +0200, Johannes Rainer wrote:
> hm, that's an option.
> based on your suggestion I created now my own little makefile to install
> the git org-mode and directly over-write the one located in
> /Applications/Emacs.app/Resources/lisp/org . actually, I first delete a
18 matches
Mail list logo
