From: Robert Goldman <rpgoldman@sift.info>
To: nicholas.dokos@hp.com
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Bug in :minlevel for INCLUDE
Date: Thu, 05 May 2011 18:17:43 -0500 [thread overview]
Message-ID: <4DC33017.5060207@sift.info> (raw)
In-Reply-To: <7063.1304636608@alphaville.dokosmarshall.org>
On 5/5/11 May 5 -6:03 PM, Nick Dokos wrote:
> Robert Goldman <rpgoldman@sift.info> wrote:
>
>> AFAICT there is an off-by-one-error here. I.e., if I tell it that the
>> :minlevel is 2, then my included level one headers get level 3, and if I
>> tell it that the :minlevel is 1, then they get level 2.
>>
>
> I think that's the desired behavior. That allows text before the first
> headline in the included file (level 0) to properly take its place in the
> result tree.
>
>> So it seems like :minlevel is actually being interpreted as a level
>> *increment*, rather than a minimum...
>>
>
> I don't really understand your comment: level N in the included file
> becomes level :minlevel+N in the result (N = 0, 1, 2, ...). What were you
> expecting?
I was expecting the standard English usage (always dangerous in a
technical context!).
The minimum of 1,2,3 is 1.
But here the thing we are calling "minimum" for 1,2,3 would be zero.
Suggestion: the term :levelinc[rement] would be more indicative of the
meaning. I think if you read your explanation, you will see that the
thing referred to as a minimum is really an increment...
It may be too late to make that change without disruption, so the
alternative would be to modify the manual to make the meaning clearer.
Best,
r
prev parent reply other threads:[~2011-05-05 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 22:43 Bug in :minlevel for INCLUDE Robert Goldman
2011-05-05 23:03 ` Nick Dokos
2011-05-05 23:17 ` Robert Goldman [this message]
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=4DC33017.5060207@sift.info \
--to=rpgoldman@sift.info \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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).