unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: 43611@debbugs.gnu.org
Subject: bug#43611: 28.0.50; Some mismatches between documentation and custom types
Date: Sat, 26 Sep 2020 17:01:21 +0200	[thread overview]
Message-ID: <87ft74k2f2.fsf@gnus.org> (raw)
In-Reply-To: <CABczVwepu3ELOWicCJVo5E7OEc=1dUCpZiMt4FdCZAuPu7Nzmg@mail.gmail.com> (Mauro Aranda's message of "Fri, 25 Sep 2020 11:41:43 -0300")

Mauro Aranda <maurooaranda@gmail.com> writes:

> This report is about some mismatches between what the docstring says,
> and what the custom types allow, in cus-start.el.
>
> - cursor-type-types
> Two problems here:
> 1. The :tag for the (hbar . HEIGHT) option reads:
> Horizontal bar with specified width.
> It should say height.

OK, fixed.

> 2. The custom-type doesn't allow the (box . SIZE) option, described in
> the docstring.

  (box . SIZE)    display a filled box cursor, but make it
                  hollow if cursor is under masked image larger than
                  SIZE pixels in either dimension.

So I guess SIZE is an integer?  Then this should be correct, and I've
added it:

         (cons :tag "Box with specified size"
               (const box) integer)

> - hscroll-step
> The docstring says the value can be nil or 0, but the type is just
> number.  0 and nil have the same effect, according to the docstring, but
> it would be nice if the user could set it to nil if he wants to, using
> the Custom interface.

OK, fixed.

> - scalable-fonts-allowed
> The type is boolean, but the docstring says it can also be a list of
> regular expressions.

Ditto.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2020-09-26 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25 14:41 bug#43611: 28.0.50; Some mismatches between documentation and custom types Mauro Aranda
2020-09-26 15:01 ` Lars Ingebrigtsen [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.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=87ft74k2f2.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=43611@debbugs.gnu.org \
    --cc=maurooaranda@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.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).