It does happen anyway. I had that in to get around this issue a while ago
(long story, but it is why we still run 8.2.10), and I still get the issue
without it.
I think I have figured it out. The order the packages are installed is
important. The code below illustrates the issue for me. If I insta
Aaron Ecay writes:
> This looks like the kind of problem that results when org is byte-compiled
> in an emacs with a different version of org loaded. This used to be a
> problem when installing via package.el (and not just for org), but I think
> there has been some work put into making sure it do
Hi John,
2016ko otsailak 14an, John Kitchin-ek idatzi zuen:
>
> Hi all,
>
> I am trying to debug an issue with installing org-mode from Melpa.
>
> After installing org from Melpa, I get this on starting emacs:
>
> byte-code: Invalid function: org-babel-header-args-safe-fn
> Org-mode version 8.
John Kitchin writes:
> I am trying to debug an issue with installing org-mode from Melpa.
There's no Org on Melpa or at least there shouldn't be.
> After installing org from Melpa, I get this on starting emacs:
>
> byte-code: Invalid function: org-babel-header-args-safe-fn
You must not install O
Hi all,
I am trying to debug an issue with installing org-mode from Melpa.
After installing org from Melpa, I get this on starting emacs:
byte-code: Invalid function: org-babel-header-args-safe-fn
Org-mode version 8.3.3 (8.3.3-51-g30bcff-elpaplus @
/Users/jkitchin/Desktop/jmax-git/elpa/org-plus-
Bastien writes:
> Hi Thomas,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> What's going on?
>
> Do you still see this errors?
No, the errors are gone. Thanks for following up.
All the best,
Tom
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-5
Bastien gnu.org> writes:
> Can you try reinstalling by first remove local.mk or regenerating it
> with ~$ make config ?
The local.mk is never touched if one exists, make config simply shows you
the most important settings there.
In any case, the error was most likely caused by an incorrect defcu
Hi Thomas,
t...@tsdye.com (Thomas S. Dye) writes:
> What's going on?
Do you still see this errors?
> Worg suggests that the invalid function problem might be solved by
> running make clean and then make again, but doing this didn't help
> me.
Can you try reinstalling by first remove local.mk o
Thorsten Jolitz writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
> Hi,
>
>> ox.el:77:1:Error: Invalid function: "Org"
>
> Is that line 77 in /lisp/ox.el? Maybe have a look ...
Nothing that looks like "Org" there. And there are still the other 42
failures ...
Tom
--
Thomas S. Dye
http://www
t...@tsdye.com (Thomas S. Dye) writes:
Hi,
> ox.el:77:1:Error: Invalid function: "Org"
Is that line 77 in /lisp/ox.el? Maybe have a look ...
--
cheers,
Thorsten
Aloha all,
Today I updated Org mode from its git repo using the makefile I've had
for a long time. It usually works flawlessly, but today it didn't:
In toplevel form:
ox.el:77:1:Error: Invalid function: "Org"
Done (Total of 65 files compiled, 43 failed, 3 skipped)
What's going on?
Worg suggest
To: emacs-orgmode@gnu.org
Subject: Bug: Debugger entered--Lisp error: (invalid-function
org-with-silent-modifications) despite reinstall [8.2.3a (8.2.3a-elpaplus @
c:/Users/Dexter/.emacs.d/elpa/org-plus-contrib-2013/)]
From: odta...@yahoo.com
--text follows this line--
Remember to cover the b
Hello,
Trying to provide batch Emacs/Org scripts to colleagues, I must ensure that
they have Org 8.
I wrote the following code so that users which have a default (Cygwin) Emacs
24.3.1 (with the default Org 7.9.3f) are proposed an upgrade through the
`package' manager:
--8<---cut here
Achim Gratz writes:
> Bastien writes:
>>> We'll have to tell users to forcibly update the tags again.
>>
>> For the users who will not do this, only the release_7.8.11
>> will not properly set, right?
>
> Yes. Another sticky point is that any clones of the orgmode repo (like
> the one on repo.or
Bastien writes:
>> We'll have to tell users to forcibly update the tags again.
>
> For the users who will not do this, only the release_7.8.11
> will not properly set, right?
Yes. Another sticky point is that any clones of the orgmode repo (like
the one on repo.or.cz) will not automatically pick
Achim Gratz writes:
> Bastien writes:
>> Can you summarize what would be the change and why it is called for?
>
> The tag release_7.8.11 is affixed to the merge commit, which means that
> it's first parent is on the master branch rather than maint. The change
> sets it back one commit so that it
Bastien writes:
> Can you summarize what would be the change and why it is called for?
The tag release_7.8.11 is affixed to the merge commit, which means that
it's first parent is on the master branch rather than maint. The change
sets it back one commit so that it correctly is located on the mai
Hi Achim,
Achim Gratz writes:
> It doesn't automatically propagate. Otherwise, it's Bastiens decision —
> I can push the change if he wants to.
Can you summarize what would be the change and why it is called for?
Thanks,
--
Bastien
Nick Dokos writes:
> Does that have any undesirable consequences? If not, can this be done on
> the repo?
It doesn't automatically propagate. Otherwise, it's Bastiens decision —
I can push the change if he wants to.
> I actually did the above in my clone and then fetched tags again which
> reset
Achim Gratz wrote:
> Nick Dokos writes:
> > OK. Is there no way to fix that? That's pretty confusing.
>
> If you already know the tag is on a merge commit on the wrong side:
>
> git tag fixup release_7.8.11
> git tag -d release_7.8.11
> git tag release_7.8.11 fixup^2
> git tag -d fixup
>
Does
Nick Dokos writes:
> OK. Is there no way to fix that? That's pretty confusing.
If you already know the tag is on a merge commit on the wrong side:
git tag fixup release_7.8.11
git tag -d release_7.8.11
git tag release_7.8.11 fixup^2
git tag -d fixup
> And how can I tell that I have fallen into t
Achim Gratz wrote:
> Nick Dokos writes:
> > Achim Gratz wrote:
> >
> >> Nick Dokos writes:
> >> > This doesn't make sense (I blame the head-spinning reverts :-) ), so let
> >> > me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
> >> > fixed somehow, either because of a rever
Nick Dokos writes:
> Achim Gratz wrote:
>
>> Nick Dokos writes:
>> > This doesn't make sense (I blame the head-spinning reverts :-) ), so let
>> > me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
>> > fixed somehow, either because of a revert or because some fix was
>> > actu
Achim Gratz wrote:
> Nick Dokos writes:
> > This doesn't make sense (I blame the head-spinning reverts :-) ), so let
> > me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
> > fixed somehow, either because of a revert or because some fix was
> > actually applied, I don't know
Nick Dokos writes:
> This doesn't make sense (I blame the head-spinning reverts :-) ), so let
> me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
> fixed somehow, either because of a revert or because some fix was
> actually applied, I don't know which. It was working until 7.8
Nick Dokos writes:
> Nick Dokos wrote:
>
>> I haven't chased it all the way down because the reverts are
>> making my head spin, but it may be that somehow the above commit
>> got lost somewhere - or it got fixed and then the big revert lost
>> the fix. Maybe Eric or Bastien remembers what happe
Nick Dokos wrote:
> I haven't chased it all the way down because the reverts are
> making my head spin, but it may be that somehow the above commit
> got lost somewhere - or it got fixed and then the big revert lost
> the fix. Maybe Eric or Bastien remembers what happened.
>
This doesn't make s
Nick Dokos wrote:
> Nick Dokos wrote:
>
> > Loris Bennett wrote:
> >
> > > I used to be able do all sorts of stuff with sh, Perl and R. Now the
> > > following example no longer works:
> > >
> > > ,---
> > > | #+begin_src sh :dir /@:/t
Nick Dokos wrote:
> Loris Bennett wrote:
>
> > I used to be able do all sorts of stuff with sh, Perl and R. Now the
> > following example no longer works:
> >
> > ,---
> > | #+begin_src sh :dir /@:/tmp
> > | echo "Executed by `whoami` on
Loris Bennett wrote:
> I used to be able do all sorts of stuff with sh, Perl and R. Now the
> following example no longer works:
>
> ,---
> | #+begin_src sh :dir /@:/tmp
> | echo "Executed by `whoami` on `hostname` in `pwd`"
> | #+end_src
Nick Dokos writes:
> Achim Gratz wrote:
>
>> Nick Dokos writes:
>> > Loris Bennett wrote:
>> >> In the *Org-Babel Error Output* buffer, I get the following:
>> >>
>> >> /bin/bash: /scpc:x@xx:/tmp/sh-script-7472puH: No such file or
>> >> directory
>>
>> It would seem that you are tryi
Achim Gratz wrote:
> Nick Dokos writes:
> > Loris Bennett wrote:
> >> In the *Org-Babel Error Output* buffer, I get the following:
> >>
> >> /bin/bash: /scpc:x@xx:/tmp/sh-script-7472puH: No such file or
> >> directory
>
> It would seem that you are trying to use a remote file with a l
Nick Dokos writes:
> Loris Bennett wrote:
>> In the *Org-Babel Error Output* buffer, I get the following:
>>
>> /bin/bash: /scpc:x@xx:/tmp/sh-script-7472puH: No such file or
>> directory
It would seem that you are trying to use a remote file with a local
bash. That won't work, especial
Loris Bennett wrote:
> Bastien writes:
>
> > Hi Loris,
> >
> > "Loris Bennett" writes:
> >
> >> Nothing works now, not even
> >>
> >> #+BEGIN_SRC sh :file tmp.txt :dir /x@xxx:
> >> echo hostname
> >> #+END_SRC
> >
> > Maybe you don't have permission to read the /tmp/ dir
> > on the rem
Bastien writes:
> Hi Loris,
>
> "Loris Bennett" writes:
>
>> Nothing works now, not even
>>
>> #+BEGIN_SRC sh :file tmp.txt :dir /x@xxx:
>> echo hostname
>> #+END_SRC
>
> Maybe you don't have permission to read the /tmp/ dir
> on the remote machine?
>
> Anyway, it's hard to debug with so
Hi Loris,
"Loris Bennett" writes:
> Nothing works now, not even
>
> #+BEGIN_SRC sh :file tmp.txt :dir /x@xxx:
> echo hostname
> #+END_SRC
Maybe you don't have permission to read the /tmp/ dir
on the remote machine?
Anyway, it's hard to debug with so little information.
--
Bastien
Hi Bastien,
Bastien writes:
> Hi Lorise,
>
> "Loris Bennett" writes:
>
>> I have just updated to emacs 24.2.50.1 and org 7.9-32-g805a9f-elpa and
>> am having this problem again even with an ECM. Commenting out the
>> declaration as suggested above no longer helps.
>>
>> Any suggestions?
>
> Ca
Hi Lorise,
"Loris Bennett" writes:
> I have just updated to emacs 24.2.50.1 and org 7.9-32-g805a9f-elpa and
> am having this problem again even with an ECM. Commenting out the
> declaration as suggested above no longer helps.
>
> Any suggestions?
Can you share the Perl script that is not worki
"Loris Bennett" writes:
> Nick Dokos writes:
>
>> Loris Bennett wrote:
>>
>>> Nick Dokos writes:
>>>
>>> > Loris Bennett wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >> When I try to run a Perl script remotely via ":dir", I get the following
>>> >> error:
>>> >>
>>> >> ,-
Nick Dokos writes:
> Loris Bennett wrote:
>
>> Nick Dokos writes:
>>
>> > Loris Bennett wrote:
>> >
>> >> Hi,
>> >>
>> >> When I try to run a Perl script remotely via ":dir", I get the following
>> >> error:
>> >>
>> >> ,--
Loris Bennett wrote:
> Nick Dokos writes:
>
> > Loris Bennett wrote:
> >
> >> Hi,
> >>
> >> When I try to run a Perl script remotely via ":dir", I get the following
> >> error:
> >>
> >> ,-
> >> | org-babel-local-file-na
Nick Dokos writes:
> Loris Bennett wrote:
>
>> Hi,
>>
>> When I try to run a Perl script remotely via ":dir", I get the following
>> error:
>>
>> ,-
>> | org-babel-local-file-name: Invalid function: with-parsed-tramp-file-
Loris Bennett wrote:
> Hi,
>
> When I try to run a Perl script remotely via ":dir", I get the following
> error:
>
> ,-
> | org-babel-local-file-name: Invalid function: with-parsed-tramp-file-name
> `---
Hi,
When I try to run a Perl script remotely via ":dir", I get the following
error:
,-
| org-babel-local-file-name: Invalid function: with-parsed-tramp-file-name
`--
That worked, thank you so much!
On Mon, Feb 13, 2012 at 3:55 AM, Thorsten wrote:
> Peter Salazar writes:
>
> > I seem to have broken my org-mode.
>
> I remember having a similar problem, and it turned out that the old
> version interfered with the new one, resulting in a corrupted org
> instal
Peter Salazar writes:
> I seem to have broken my org-mode.
I remember having a similar problem, and it turned out that the old
version interfered with the new one, resulting in a corrupted org
installation. I had to get the old version completely out of the
way (delete the org folder in the ori
Hey everyone,
I seem to have broken my org-mode. I'm running Aquamacs which comes with
org-mode 6.33 or thereabouts. I downloaded 7.8.03, did a setq load-path
(cons to the directory, then used the package manager to install org from
within Aquamacs.
I can verify that org now states its version as
At Sun, 09 Oct 2011 22:04:47 +0530,
Jambunathan K wrote:
>
>
> Seems like a bug to me.
Not necessarily: From past experience an invalid function error is an
indicator of a mixed up Org mode installation. What roughly happens is
that Emacs tries to look up a function value for
`org-called-interacti
Thanks mate, that works fine
On Sun, Oct 9, 2011 at 5:34 PM, Jambunathan K wrote:
>
> Seems like a bug to me.
>
> As a temporary workaround add this to your .emacs. (Do this only if your
> are running emacs >= 23.2)
>
> --8<---cut here---start->8---
> (defalia
Gerrard McNulty writes:
> Here's what I get when I follow those instructions:
>
> Library is file ~/.emacs.d/elpa/org-20111008/org-table.elc
> Library is file ~/.emacs.d/elpa/org-20111008/org-macs.elc
Did you perhaps have an earlier version of org-mode installed without
using ELPA? Is it possibl
Seems like a bug to me.
As a temporary workaround add this to your .emacs. (Do this only if your
are running emacs >= 23.2)
--8<---cut here---start->8---
(defalias 'org-called-interactively-p 'called-interactively-p)
--8<---cut here---e
Hi,
Here's what I get when I follow those instructions:
Library is file ~/.emacs.d/elpa/org-20111008/org-table.elc
Library is file ~/.emacs.d/elpa/org-20111008/org-macs.elc
On Sun, Oct 9, 2011 at 4:31 PM, Jambunathan K wrote:
>
> See http://www.mail-archive.com/emacs-orgmode@gnu.org/msg47345.h
See http://www.mail-archive.com/emacs-orgmode@gnu.org/msg47345.html
> Hi,
>
> I'm using Emacs 23.3.1 on Windows 7 and org mode 7.7 (installed via
> elpa/marmalade).
>
> My .emacs is fairly minimalist:
>
> (add-to-list 'load-path "~/.emacs.d/")
>
> (require 'package)
> (add-to-list 'package-archi
Hi,
I'm using Emacs 23.3.1 on Windows 7 and org mode 7.7 (installed via
elpa/marmalade).
My .emacs is fairly minimalist:
(add-to-list 'load-path "~/.emacs.d/")
(require 'package)
(add-to-list 'package-archives
'("marmalade" . "http://marmalade-repo.org/packages/";))
(package-initia
54 matches
Mail list logo
