emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: setting local variables
Date: Tue, 05 Sep 2017 09:57:09 -0700	[thread overview]
Message-ID: <87h8wh13tm.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87wp5dmkm0.fsf@gmx.us

Rasmus <rasmus@gmx.us> writes:

> Hi,
>
> (Sorry for replying to this old thread which I am only reading now)
>
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>>>> I'm writing an Emacs manual in Org, using
>>>> https://github.com/tarsius/ox-texinfo-plus to make things a bit
>>>> easier.
>>>
>>> I don't know that library, but as a biased POV, it would be nice to use
>>> "ox-texinfo" and let us know about its shortcomings. Just saying.
>>
>> Oh I don't think it's about shortcomings, just about having a version
>> that's tweaked specifically for writing Emacs manuals. I _really_ want
>> my packages to have info manuals, and I _really_ don't want to learn how
>> to write texinfo. I saw Rasmus' Org manual in org, and it looked like a
>> lot of work. Then I noticed that the Magit manuals used this
>> texinfo-plus thing, and it seemed good enough.
>
> It was Thomas S. Dye who ported the Org manual in Org
>
>     https://github.com/tsdye/orgmanual
>
> FWIW I like to see general tweaks added directly to ox-texinfo to the
> extend it’s feasible.

Oops, sorry about that.

Later I removed my manual's dependency on ox-texinfo+, and went with
plain Org export functionality. It looks a lot better now, and is more
correct, but it took me a good half day to learn texinfo and do the
work. I knew I'd have to do that at some point, so that's fine, I was
just putting it off.

The only real problem I encountered was that links to external Info
manuals did not export correctly, and couldn't be followed. I gave up on
learning the exact syntax of texinfo's @[px]ref commands because it was
dinnertime, but I can figure out what went wrong and maybe provide a
patch.

The other thing I'd like to know is how to "inline" sections (ie output
several sections on a single page), but still have links to those
sections work correctly.

That problem and most others could probably be "solved" by expanding the
docs. For instance, regarding the sectioning problem, "12.14.6 Headings
and sectioning structure" in the Org manual says:

  If an Org headline’s level has no associated Texinfo structuring
  command, or is below a certain threshold (*note Export settings), then
  the Texinfo export back-end makes it into a list item.

Why a list item? Plenty of Info manuals have multiple sub-headings on a
single page, how do we do that?

In general, I think the texinfo part of the Org manual could benefit
from some beefing up, and I'd be happy to provide suggestions.

Eric

  reply	other threads:[~2017-09-05 16:57 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 21:53 setting local variables Eric Abrahamsen
2017-08-02 22:10 ` Kaushal Modi
2017-08-02 22:15   ` Eric Abrahamsen
2017-08-03 10:52 ` Nicolas Goaziou
2017-08-03 16:11   ` Eric Abrahamsen
2017-08-03 22:02     ` Nicolas Goaziou
2017-08-03 22:49       ` Eric Abrahamsen
2017-08-04  0:42         ` Eric Abrahamsen
2017-08-04 15:37           ` Nicolas Goaziou
2017-08-05  1:06             ` Eric Abrahamsen
2017-08-05  8:50               ` Nicolas Goaziou
2017-08-05 19:14                 ` Eric Abrahamsen
2017-09-05 11:48     ` Rasmus
2017-09-05 16:57       ` Eric Abrahamsen [this message]
2017-09-06  8:56         ` Rasmus
2017-09-06 10:38           ` Nicolas Goaziou
2017-09-06 12:42             ` Rasmus
2017-09-06 13:08               ` Nicolas Goaziou
2017-09-06 16:33                 ` Eric Abrahamsen
2017-09-06 16:57                   ` Nicolas Goaziou
2017-09-06 17:44                     ` Eric Abrahamsen
2017-09-07  8:56                     ` Rasmus
2017-09-07 12:48                       ` Nicolas Goaziou
2017-09-07 15:01                         ` Eric Abrahamsen
2017-09-10 13:55                           ` Nicolas Goaziou
2017-09-20 16:17                           ` Carsten Dominik
2017-09-20 18:42                             ` Scott Randby
2017-09-20 23:16                               ` Kaushal Modi
2017-09-21  8:38                                 ` Carsten Dominik
2017-09-21  9:39                                   ` Rasmus
2017-09-21  9:58                                     ` Carsten Dominik
2017-09-21 19:21                                       ` Nicolas Goaziou
2017-09-21 21:25                                         ` Kaushal Modi
2017-09-22  7:22                                         ` Carsten Dominik
2017-09-22  9:09                                         ` Rasmus
2017-09-21 13:00                                 ` Scott Randby
2017-09-21  7:45                               ` Eric S Fraga

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=87h8wh13tm.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).