Samuel Wales writes:
> thanks for your reply. next time i will check for long lines.
>
> On 7/17/16, Nicolas Goaziou wrote:
>> It seems you are using very long lines.
>>
>> In particular one of them is ambiguous and the parser has to match too
>>
Christian Moe writes:
> Eric Abrahamsen writes:
>
>> I just had to convert a 200+ page document to Org by hand: searching
>> for italics worked, but not replace.
>
> Looks like pandoc is the way to go, I'll have to try it.
>
> Still, Search/Replace for italics in
thanks for your reply. next time i will check for long lines.
On 7/17/16, Nicolas Goaziou wrote:
> It seems you are using very long lines.
>
> In particular one of them is ambiguous and the parser has to match too
> much (hence the stack overflow) to decide what is that
Eric Abrahamsen writes:
> I just had to convert a 200+ page document to Org by hand: searching
> for italics worked, but not replace.
Looks like pandoc is the way to go, I'll have to try it.
Still, Search/Replace for italics in LibreOffice ought to work. Try this
recipe:
1) Edit -> Find /
Hello,
"Charles C. Berry" writes:
> In trying to export to a pdf in another directory specified with a
> relative pathname as the destination, I kept running into errors.
>
> It looks like `org-compile-file' does not handle such things gracefully.
>
> I believe that `out-dir'
Hello,
Sharon Kimble writes:
> I'm working on an org-mode file about cancer which is 945.1kb, is
> converted to a tex file of 1.0mb and a pdf of 2.0mb with 505 pages. The
> conversion is done through this code snippet '(global-set-key (kbd
> "s-#")
Hello,
Robert Klein writes:
> Thanks for the confirmation. I also have issues exporting
> http://orgmode.org/worg/dev/org-element-api.org -- while the error
> message is "Unable to resolve code reference: end" bisecting leads to
> the same commit; reverting the commit
Hello,
Samuel Wales writes:
> all i did was press return. this followed trying to comment
> a blank line (which i wish emacs would just do).
>
> i cannot do a thorough bug report or q/a at this time but
> thought this might be useful.
>
> Debugger entered--Lisp error:
Hello,
Sanel Zukan writes:
> I've been using org-mode 7.9.3f for quite a bit time and for clocking
> with unspecified timestamp I'd use the following construct:
>
> * Some task
>CLOCK: => 2:00
>
> which was perfectly valid in this org-mode version.
This syntax isn't