emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Greg Minshall <minshall@umich.edu>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: patch to change org-adapt-indentation customization documentation
Date: Wed, 18 Nov 2020 10:49:41 +0100	[thread overview]
Message-ID: <87r1or570q.fsf@gmail.com> (raw)
In-Reply-To: <839402.1605622845@apollo2.minshall.org> (Greg Minshall's message of "Tue, 17 Nov 2020 17:20:45 +0300")

Greg Minshall <minshall@umich.edu> writes:

> Robert,
>> The whole point of customize is that you shouldn't have to worry about
>> what the actual lisp value is. The actual lisp value only matters if
>> you directly set the value without using customize.
> thanks for the response.  i've included the documentation for
> org-adapt-indentation below.  since the documentation talks about values
> and associated behaviors, it might be helpful to mention the values in
> the customization dialog.  an alternative maybe would be to re-do the
> documentation to highlight the three customization phrases:
> ----
> "Adapt indentation for all lines"
> "Adapt indentation for headline data lines"
> "Do not adapt indentation at all"
> ----
> and not change the customization dialog?

Yes, I think that would be better.

> i, anyway, was very uncertain, even after several rounds, as to which
> customization option would give me the behavior i had read about in the
> documentation.

That means the docstring is probably the thing that needs adjusting.


  reply	other threads:[~2020-11-18  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 13:22 patch to change org-adapt-indentation customization documentation Greg Minshall
2020-11-17 14:08 ` Robert Pluim
2020-11-17 14:20   ` Greg Minshall
2020-11-18  9:49     ` Robert Pluim [this message]
2020-11-18 12:13       ` Greg Minshall
2020-11-19  4:05         ` Kyle Meyer

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:

  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=87r1or570q.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=minshall@umich.edu \


* 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


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).