Hi Kaushal,
Kaushal Modi writes:
> Using the W3C Invalid Link checker[1], I found the following invalid
> (404) links on Worg.
Those should be fixed, thanks!
--
Bastien
Hello Nicolas,
that worked perfectly.
I had a strange character in that file and now it works good.
Thanks,
Michael
Am 2017-05-08 11:52, schrieb Nicolas Goaziou:
> michael.zi...@xiron.de writes:
>
>> When i byte-compile the file i get the following error:
>>
>> Compiling file
>> c:/Use
michael.zi...@xiron.de writes:
> When i byte-compile the file i get the following error:
>
> Compiling file
> c:/Users/sane/AppData/Roaming/.emacs.d/elpa/org-20170502/org-clock.el at
> Mon May 8 11:27:30 2017
> org-clock.el:1949:1:Error: Invalid read syntax: "?"
It looks odd. Could you double-c
Hello Nicolas,
thanks for the answer.
I'm not a big expert on lisp. As i did not find any information how a
.patch file works so fast, i just changed it manually in the
org-clock.el like this:
(defun org-clock-put-overlay (time)
"Put an overlays on the current line, displaying TIME.
This cr
Hello,
michael.zi...@xiron.de writes:
> when i try to swicht an active timestamp via org-shitright or when i
> fire M-x org-submit-bug-report i get the following error:
>
> Debugger entered--Lisp error: (invalid-read-syntax "?")
> eval-buffer(# nil
> "c:/Users/sane/AppData/Roaming/.emacs.d/elp
No the problem is this bug that has been fixed recently in 25.1 about
unbalanced changed hooks.
It is a bug that has always existed, so in 24.x also.
Fabrice
2016-08-23 11:53 GMT+02:00 Eric S Fraga :
> On Tuesday, 23 Aug 2016 at 09:31, Toby Gee wrote:
> >> What version of emacs are you using?
On Tuesday, 23 Aug 2016 at 09:31, Toby Gee wrote:
>> What version of emacs are you using? I know that there was a problem in
>> the development version of emacs early in July that caused this type of
>> problem. I am not sure if it has been fixed -- I've kept to a version
>> from June for the tim
Hopefully, it should be fixed in emacs-25.1-rc2 (available now)
Fabrice
2016-08-23 11:31 GMT+02:00 Toby Gee :
> > What version of emacs are you using? I know that there was a problem in
> > the development version of emacs early in July that caused this type of
> > problem. I am not sure if it
On Thursday, 18 Aug 2016 at 15:22, Toby Gee wrote:
> Sometimes when I create my agenda I get an "Invalid search bound (wrong side
> of
> point)". Usually this happens when I just filed some todos and hit r on
> the Agenda screen; invariably when this happens todo.org isn't
> saved. When I save it,
> What version of emacs are you using? I know that there was a problem in
> the development version of emacs early in July that caused this type of
> problem. I am not sure if it has been fixed -- I've kept to a version
> from June for the time being.
I'm using 24.4.5 on one machine, and 24.5.4
I would like to thank everyone for their help in resolving something
which I should have done myself had I but gave the matter a little more
thought.
Best wishes,
Colin.
On Wed, Apr 20 2016, Nick Dokos wrote:
> Colin Baxter writes:
>
>> The file /lisp/ox-html.el of org-mode release_8.3.4-743-g516bbf has
>> binary content at line 1952, whereas the same file of org-mode
>> release_8.3.4-721-g16ad80 has not. Perhaps this is significant.
>>
>
> Perhaps I'm missing so
Colin Baxter writes:
> The file /lisp/ox-html.el of org-mode release_8.3.4-743-g516bbf has
> binary content at line 1952, whereas the same file of org-mode
> release_8.3.4-721-g16ad80 has not. Perhaps this is significant.
>
Perhaps I'm missing something but I don't see anything like that.I also
On Wed, Apr 20 2016, Alan Schmitt wrote:
> On 2016-04-20 07:59, Colin Baxter writes:
>
>> On Tue, Apr 19 2016, Nicolas Goaziou wrote:
>>
>>> Hello,
>>>
>>> Colin Baxter writes:
>>>
With the latest org-mode release_8.3.4-739-g7894129, I'm getting an lisp
error
(invalid-read-syntax
On Tue, Apr 19 2016, Nicolas Goaziou wrote:
> Hello,
>
> Colin Baxter writes:
>
>> With the latest org-mode release_8.3.4-739-g7894129, I'm getting an lisp
>> error
>> (invalid-read-syntax "#"). This ocurs with emacs-25.1.50.1 and
>> emacs-24.5.1.
>
> Could you provide an ECM? What command trigg
On 2016-04-20 07:59, Colin Baxter writes:
> On Tue, Apr 19 2016, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> Colin Baxter writes:
>>
>>> With the latest org-mode release_8.3.4-739-g7894129, I'm getting an lisp
>>> error
>>> (invalid-read-syntax "#"). This ocurs with emacs-25.1.50.1 and
>>> emacs-2
Hello,
Colin Baxter writes:
> With the latest org-mode release_8.3.4-739-g7894129, I'm getting an lisp error
> (invalid-read-syntax "#"). This ocurs with emacs-25.1.50.1 and
> emacs-24.5.1.
Could you provide an ECM? What command triggered that?
Regards,
--
Nicolas Goaziou
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
El lun, 13 jul 2015, Rasmus decía:
> Hi,
>
> OSiUX writes:
>
> > Hi everybody, using a W3C validator the footnotes are invalid. :(
> > [...]
> > How should define the footnote?
> > Is an exporter error?
>
> Thanks.
>
> I tried to fix it in commit fd990a81e38ad80892519395ed52fbef5aca6545. It
Hi,
OSiUX writes:
> Hi everybody, using a W3C validator the footnotes are invalid. :(
> [...]
> How should define the footnote?
> Is an exporter error?
Thanks.
I tried to fix it in commit fd990a81e38ad80892519395ed52fbef5aca6545. It
produces error-free and visually correct results in with my
Hello,
Keith David Bershatsky writes:
> I had a little free time today and was finally able to track down the
> invalid face reference when generating an org-agenda buffer. It is
> caused because the `car` of the `cons` cell created by
> `org-agenda-fontify-properties` is sometimes `nil`. I thre
Hello,
Karl Voit writes:
> - re-produce with:
> 1. ~C-c a m~
> 2. +SCHEDULED>"<+2d>" (or similar)
>
> - I get:
> : org-element-paragraph-parser: Invalid search bound (wrong side of point)
>
>
> How do I debug this issue without bi-secting all my Org-mode files?
Try M-x toggle-debug-on-error
Hello,
Nicolas Richard writes:
> Sometimes I apparently manage to corrupt my org files by having an
> unfinished drawers in them. Of course this is wrong and I should
> investigate, but if it happens, hitting C-c C-x p leads to a useless
> error (Wrong type argument: integer-or-marker-p, nil). I
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
Luca Ferrari writes:
> Hi all,
> when exporting to OpenOffice using a ott file as template I get the
> error "Invalid specification of styles.xml: nil", even if I placed the
> property
> #+ODT_STYLES_FILE: /home/luca/letter.ott
> in the org file. Regular exports to ODT works out of the box, of co
On Thu, Aug 29, 2013 at 6:22 AM, Jambunathan K wrote:
> The double quotes. See the following section in the manual.
Great!
I did not noted that!
Thanks,
Luca
On Tue, Aug 20, 2013 at 9:48 AM, Sebastien Vauban
wrote:
> Mehul Sanghvi wrote:
> > Sebastien Vauban wrote:
> >> Mehul Sanghvi wrote:
> Mehul Sanghvi wrote:
> > The error only occurs if I'm using org-babl. The offending piece of
> code
> > I've got is:
> >
> > #+BEGIN_SRC emac
Mehul Sanghvi wrote:
> Sebastien Vauban wrote:
>> Mehul Sanghvi wrote:
Mehul Sanghvi wrote:
> The error only occurs if I'm using org-babl. The offending piece of code
> I've got is:
>
> #+BEGIN_SRC emacs-lisp
> (setq tramp-default-method "ssh")
> #+END_SRC
>
> I
On Tue, Aug 20, 2013 at 4:20 AM, Sebastien Vauban
wrote:
> Mehul Sanghvi,
>
> Mehul Sanghvi wrote:
> >> Mehul Sanghvi wrote:
> >> > The error only occurs if I'm using org-babl. The offending piece of
> code
> >> > I've got is:
> >> >
> >> > #+BEGIN_SRC emacs-lisp
> >> > (setq tramp-default-method
Mehul Sanghvi,
Mehul Sanghvi wrote:
>> Mehul Sanghvi wrote:
>> > The error only occurs if I'm using org-babl. The offending piece of code
>> > I've got is:
>> >
>> > #+BEGIN_SRC emacs-lisp
>> > (setq tramp-default-method "ssh")
>> > #+END_SRC
>> >
>> > If I remove the #+BEGIN_SRC and #+END_SRC th
Sebastien,
Thanks for the suggestion. That does not fix the problem. I still
get the same error as before.
cheers,
mehul
On Mon, Aug 19, 2013 at 10:06 AM, Sebastien Vauban
wrote:
> Mehul Sanghvi wrote:
> > The error only occurs if I'm using org-babl. The offending piece of
Mehul Sanghvi wrote:
> The error only occurs if I'm using org-babl. The offending piece of code
> I've got is:
>
> #+BEGIN_SRC emacs-lisp
> (setq tramp-default-method "ssh")
> #+END_SRC
>
> If I remove the #+BEGIN_SRC and #+END_SRC than everything works fine and
> I'm able to publish.
Would this
The error only occurs if I'm using org-babl. The offending piece of code
I've got is:
#+BEGIN_SRC emacs-lisp
(setq tramp-default-method "ssh")
#+END_SRC
If I remove the #+BEGIN_SRC and #+END_SRC than everything works fine and
I'm able to publish.
On Sun, Aug 18, 2013 at 11:43 PM, Mehul Sa
OSiUX,
OSiUX wrote:
> After upgrading, when publish a project I get
> the error:
>
> org-export-expand-include-keyword:
> Invalid syntax in INCLUDE keyword
>
> I try delete all lines with:
>
> #+INCLUDE: header.org
New syntax: quote the file name...
#+INCLUDE: "header.org"
>
Thorsten Jolitz writes:
[continuation, prior message sent unfinished by accident]
> but with your other hints, I now understand the problem. I wanted to see
> how the parse tree looks like, so I printed it out (I did not know about
> the existance of 'print-circle' then, but it was set to nil).
Nicolas Goaziou writes:
>> I want to write an 'unusual' backend that does not need anything else
>> from the exporting framework but the parse-tree as a list.
>
> Then you don't want the exporting framework at all, only org-element.el.
yes, only the parser.
> Anyway I'm confused. The parse-tr
Thorsten Jolitz writes:
>> I'm not sure about what you want to do with the parse tree. The usual
>> function to work with it is `org-element-map'. You may want to have
>> a look at its docstring, as it contains examples.
>
> I want to write an 'unusual' backend that does not need anything else
>
Nicolas Goaziou writes:
Hello,
> I'm not sure about what you want to do with the parse tree. The usual
> function to work with it is `org-element-map'. You may want to have
> a look at its docstring, as it contains examples.
I want to write an 'unusual' backend that does not need anything else
Hello,
Thorsten Jolitz writes:
> here is an excerpt of a parse tree produced with
> 'org-element-parse-buffer':
>
> ,-
> | (section (:begin 1 :end 624 :contents-begin
> | 1 :contents-end 623 :post-blank 1 :parent #0) (keyword (:key
> |
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
Org-mode version 6.30c at home, even with the snapshot. I'll probably
update and follow your advice, thank you.
On 9/18/12, Jorge Timón wrote:
> I still get \texttt{<<<} \ldots{} \texttt{>>>}
>
> I have Org-mode version 6.33x at work. I'll check later at home, where
> I have both emacs23 and emac
"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:
>>> >>
>>> >> ,-
I still get \texttt{<<<} \ldots{} \texttt{>>>}
I have Org-mode version 6.33x at work. I'll check later at home, where
I have both emacs23 and emacs24 (snapshot).
On 9/17/12, Nick Dokos wrote:
> Jorge Timón wrote:
>
>> I wouldn't care about the spaces and I would prefer not to use latex.
>
Jorge Timón wrote:
> I wouldn't care about the spaces and I would prefer not to use latex.
> The problem is that that produces:
>
> \texttt{<<<} \ldots{} \texttt{>>>}
>
Did you try it with the tildes instead of the equal signs?
Here, both old and new exporters produce
aaa \verb~<<<~ \
I wouldn't care about the spaces and I would prefer not to use latex.
The problem is that that produces:
\texttt{<<<} \ldots{} \texttt{>>>}
and then latex joins the first << and the first >> together, which is
really ugly.
My document is already LaTeX specific, but if I'm able replace more
latex
Jorge Timón wrote:
> The only way I know to do what I want is \verb=<<<=...\verb=>>>=, in
> case someone has a similar problem.
>
If you don't mind the extra space around the dots, you can say
aaa ~<<<~ ... ~>>>~ aa a a
the advantage being that it is backend-independent, so it will
Thank you very much, now all makes sense. And I hopefully find some
use for radio targets.
The only way I know to do what I want is \verb=<<<=...\verb=>>>=, in
case someone has a similar problem.
On 9/17/12, Achim Gratz wrote:
>
> Search the manual for "radio targets".
>
>
> Regards,
> Achim.
>
Search the manual for "radio targets".
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
I've been testing a little more. I anyone wants to reproduce the error.
Here's a simpler example, just create a file with this:
#+AUTHOR: test
* 123 1 2 3 4
aaa =<<<...>>>= aa a a
And export it with C-c C-e L.
The output buffer will look like this:
% Created 2012-09-17 Mon 21:09
\documentclas
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
> `---
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
On 28 Jan 2012, at 16:55, Bastien wrote:
> For some reason, the first code block is evaluated twice.
Ah, this explains why I was being asked twice if I allowed the code to run.
> When putting a headline on top of this first block, the error
> disappears.
>
> Sorry I can't help further with this
Hi Alan,
"Alan Schmitt" writes:
> I'm trying this example to export nicely formatted code in LaTeX:
> http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
>
> Unfortunately it fails with an error 'Invalid read syntax "#"'. If I delete
> the second code block (the python one), it
Nick Dokos wrote:
> Alan Schmitt wrote:
>
> > Hello,
> >
> > I'm trying this example to export nicely formatted code in LaTeX:
> > http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
> >
> > Unfortunately it fails with an error 'Invalid read syntax "#"'. If I
> > delete the s
Nick Dokos writes:
> You are quoting the entry but including a , before the concat. That
> indicates that instead of the quote ', you need to use a backquote ` to
> allow the comma to evaluate the (concat ...) expression at definition
> time.
>
> I checked the webpage you refer to and there is a
Damon Haley wrote:
> Hi I was wondering if someone could point me in the right direction
> because one of my Org capture templates, that I use to feed questions to
> myself (for later use with org-drill) just broke with the most recent
> bzr pull of emacs.
>
Probably not - see below.
> Now, wh
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
97 matches
Mail list logo
