bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#4876: marked as done (Defcustom without keywords)


From: Emacs bug Tracking System
Subject: bug#4876: marked as done (Defcustom without keywords)
Date: Sun, 15 Nov 2009 15:40:07 +0000

Your message dated Sun, 15 Nov 2009 17:33:20 +0200
with message-id <address@hidden>
and subject line Re: bug#4876: Defcustom without keywords
has caused the Emacs bug report #4876,
regarding Defcustom without keywords
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact address@hidden
immediately.)


-- 
4876: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=4876
Emacs Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Defcustom without keywords Date: Fri, 06 Nov 2009 03:52:47 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (x86_64-pc-linux-gnu)
I noticed a strange defcustom without any keyword in simple.el:

  (defcustom set-mark-default-inactive nil
    "If non-nil, setting the mark does not activate it.
  This causes \\[set-mark-command] and \\[exchange-point-and-mark] to
  behave the same whether or not `transient-mark-mode' is enabled.")

I could guess that :type should be 'boolean, :group 'editing-basics
and :version probably "23.1".  Was it supposed to be so?

-- 
Juri Linkov
http://www.jurta.org/emacs/



--- End Message ---
--- Begin Message --- Subject: Re: bug#4876: Defcustom without keywords Date: Sun, 15 Nov 2009 17:33:20 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (x86_64-pc-linux-gnu)
> I can't see any reason not to just fix this.

Fixed.

-- 
Juri Linkov
http://www.jurta.org/emacs/

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]