emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Lawrence Bottorff <borgauf@gmail.com>
To: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: texi to org?
Date: Sun, 18 Feb 2018 23:14:36 -0500	[thread overview]
Message-ID: <CAFAhFSUZqZ9Nbcso2DqLHR7m9LBTnn0VkKfdV_iubSDHut4-Kw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]

Is there such a thing as a converter from a raw texi file to an org file?
I'm experimenting with manual formats and would like to take texi/info
files and convert them to org files. I've tried two approaches with pandoc,
namely, html to org and text (markdown) to org -- and they've produced org
files that lock up Emacs (25.3) - Org (9.1.6). Yes, they come up after a
good half hour, but Emacs is still locked up with my CPUs racing. Right now
I'm working with Emacs Calc
<https://www.gnu.org/software/emacs/manual/html_mono/calc.html>'s single
html manual. I've done

>pandoc -f html -t org -o GNUEmacsCalcManual.org GNUEmacsCalcManual.html

and it produces a 2.3 mb file that, as I say, doesn't come up well. This
was following Using Emacs Pandoc
<http://cestlaz.github.io/posts/using-emacs-41-pandoc/>.

I don't necessarily need to do this, but I've had this issue before with
semi-large org files, e.g., a mg-sized file with lots of scheduling stuff.
What sort of processing is going on to open an org file that it would bog
down so badly? Is there anything I can do outside of Emacs to help my
pandoc-produced org file?

LB

[-- Attachment #2: Type: text/html, Size: 1313 bytes --]

             reply	other threads:[~2018-02-19  4:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19  4:14 Lawrence Bottorff [this message]
2018-02-19  8:52 ` texi to org? Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFAhFSUZqZ9Nbcso2DqLHR7m9LBTnn0VkKfdV_iubSDHut4-Kw@mail.gmail.com \
    --to=borgauf@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).