From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 8652@debbugs.gnu.org
Subject: bug#8652: 24.0.50; incorrect indentation in (elisp) Special Properties
Date: Wed, 11 May 2011 11:22:41 -0700 [thread overview]
Message-ID: <0E754F1E9A124004968E173A8BC6913E@us.oracle.com> (raw)
In-Reply-To: <83ipthglw0.fsf@gnu.org>
> > The reference sections, such as `--Variable:', should
> > follow the same indentation throughout the manual.
>
> Why? What bad things happen if they don't?
>
> > In (elisp) Special Properties, the two `--Variable:' sections are
> > indented too far; they should be indented to only column 1, as in
> > the rest of the manual.
>
> That's because they are pertinent to the `point-entered' and
> `point-left' properties, and so are sub-items of their parent item.
> Having them indented as you suggest would make them stand out of the
> surrounding text, which IMO isn't right.
The description of `inhibit-point-motion-hooks' makes it clear what it pertains
to. This is so regardless of the indentation.
The description of `show-help-function' does not, however. It is not at all
clear - even with the extra indentation - what the scope of this variable's
effect is (the fact that it is somehow "pertinent [only] to the `point-entered'
and `point-left' properties"). The description suggests that it affects the
display of help strings _in general_. And nothing in the description says what
it does, in particular, for properties `point-entered' and `point-left'. Just
how is it pertinent only to them?
You will do whatever you want, of course. ;-) Just letting you know.
This is the _only_ place in the manual where the indentation is different.
next prev parent reply other threads:[~2011-05-11 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 15:21 bug#8652: 24.0.50; incorrect indentation in (elisp) Special Properties Drew Adams
2011-05-11 17:58 ` Eli Zaretskii
2011-05-11 18:22 ` Drew Adams [this message]
2011-05-14 8:48 ` Eli Zaretskii
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0E754F1E9A124004968E173A8BC6913E@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=8652@debbugs.gnu.org \
--cc=eliz@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.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).