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
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
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
> |
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
19 matches
Mail list logo
