emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [texinfo] Bug(?) in detailed node listing
Date: Thu, 21 Feb 2013 13:44:36 -1000	[thread overview]
Message-ID: <m1txp51bbv.fsf@poto.myhome.westell.com> (raw)
In-Reply-To: <CAEWDx5febnFxXeoG-kS8N-5-mRROi+wMnYJc6=Ny_wBeO4sHMA@mail.gmail.com> (Jonathan Leech-Pepin's message of "Thu, 21 Feb 2013 18:06:48 -0500")

Hi Jon,

Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:

> Hello Tom,
>
> On 20 February 2013 19:45, Thomas S. Dye <tsd@tsdye.com> wrote:
>
>> Aloha all,
>>
>> I can't figure out how to get the detailed node listing formatted
>> correctly, so I want to call this a bug.  An example shows the problem:
>>
>> * Hacking::                        How to hack your way around
>> * MobileOrg::                      Viewing and capture on a mobile device
>> * History and Acknowledgments::    How Org came into being
>>
>>  --- The Detailed Node Listing ---
>>
>> Introduction
>>
>> * Summary::                                              Brief summary of
>> what \
>> Org-mode does
>> * Installation::                                         How to install a
>> downl\
>> oaded version of Org-mode
>>
>>
> I'm guessing you mean the extra distance between the title and the
> description of the listing?

Yes.

>
> This is not exactly a bug... In an attempt to get all the descriptions
> to line up correctly I aligned them all based on the longest
> subheading.  I'm guessing in this case there is an extremely long one
> somewhere farther down.
>

Yes, that explains it.

> I couldn't find any specification as to how far they should be aligned,
> otherwise I would have set them to a specific column instead of
> basing them on the longest headline.
>
> I should be able to fix this to be more reasonable, however I would
> need an opinion as to what distance would be appropriate/desireable.

* MobileOrg::                   Viewing and capture on a mobile device
* History and Acknowledgments::  How Org came into being
* GNU Free Documentation License::  The license for this documentation.
* Main Index::                  An index of Org's concepts and features

Based on this example from the Org manual, it looks as if the
descriptions should start on column 32 or the third column after the end
of the title, whichever is greater.

Thanks for your help on this.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

  reply	other threads:[~2013-02-21 23:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-21  0:45 [texinfo] Bug(?) in detailed node listing Thomas S. Dye
2013-02-21 23:06 ` Jonathan Leech-Pepin
2013-02-21 23:44   ` Thomas S. Dye [this message]
2013-02-25 15:45     ` Jonathan Leech-Pepin
2013-02-25 16:57       ` Thomas S. Dye
2013-02-25 17:26         ` Jonathan Leech-Pepin
2013-02-25 18:29           ` Thomas S. Dye

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=m1txp51bbv.fsf@poto.myhome.westell.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jonathan.leechpepin@gmail.com \
    /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).