From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [texinfo] Bug(?) in detailed node listing
Date: Mon, 25 Feb 2013 12:26:57 -0500 [thread overview]
Message-ID: <CAEWDx5d+8DR=XNuoUZF1Ei3jqu4EeHU88urrcfHx2tOh+_CpaA@mail.gmail.com> (raw)
In-Reply-To: <m1zjysxrfm.fsf@tsdye.com>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
Hello Tom,
On 25 February 2013 11:57, Thomas S. Dye <tsd@tsdye.com> wrote:
> Hi Jon,
>
> Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
>
> > Hi Tom,
> >
> > On 21 February 2013 18:44, Thomas S. Dye <tsd@tsdye.com> wrote:
> >
> >> Hi Jon,
> >> [...]
> >>
> >> 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.
> >>
> >>
> > I've just pushed a fix for this. It also introduces a new defcustom
> > to allow for choosing the column you want it to align at
> > (org-texinfo-node-description-column).
> >
>
> Nice. Thanks!
>
> One nit: You have one space between the `::' at the end of a long title
> and the start of the description, where the Org manual has two spaces.
>
>
This should now be fixed (along with a logic error that was actually
inserting
description at column+5)
Regards,
Jon
> All the best,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>
[-- Attachment #2: Type: text/html, Size: 1871 bytes --]
next prev parent reply other threads:[~2013-02-25 17:27 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
2013-02-25 15:45 ` Jonathan Leech-Pepin
2013-02-25 16:57 ` Thomas S. Dye
2013-02-25 17:26 ` Jonathan Leech-Pepin [this message]
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='CAEWDx5d+8DR=XNuoUZF1Ei3jqu4EeHU88urrcfHx2tOh+_CpaA@mail.gmail.com' \
--to=jonathan.leechpepin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).