From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [elpa] master 9173a44 1/2: [Fix #12] Don't autodisable beacon on hl-line-mode Date: Mon, 19 Oct 2015 09:31:09 -0400 Message-ID: References: <20151017213254.5317.59042@vcs.savannah.gnu.org> <877fmjflkk.fsf@mbork.pl> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1445261533 22938 80.91.229.3 (19 Oct 2015 13:32:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 19 Oct 2015 13:32:13 +0000 (UTC) Cc: Artur Malabarba , emacs-devel To: Marcin Borkowski Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 19 15:32:05 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZoAXj-000690-LN for ged-emacs-devel@m.gmane.org; Mon, 19 Oct 2015 15:32:03 +0200 Original-Received: from localhost ([::1]:39537 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZoAXi-0000Ad-PG for ged-emacs-devel@m.gmane.org; Mon, 19 Oct 2015 09:32:02 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60096) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZoAWw-0007jP-3U for emacs-devel@gnu.org; Mon, 19 Oct 2015 09:31:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZoAWs-0005ay-S7 for emacs-devel@gnu.org; Mon, 19 Oct 2015 09:31:14 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:8671) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZoAWs-0005as-Or for emacs-devel@gnu.org; Mon, 19 Oct 2015 09:31:10 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0AsEwA731xV/1/x92hcgxCEAoVVuzcJh0sEAgKBPDkUAQEBAQEBAYEKQQWDXQEBAwFWIwULCw4mEhQYDSSINwjPIwEBAQEGAQEBAR6LOoUFB4QtBZlthSqSFINZI4I7gVkigngBAQE X-IPAS-Result: A0AsEwA731xV/1/x92hcgxCEAoVVuzcJh0sEAgKBPDkUAQEBAQEBAYEKQQWDXQEBAwFWIwULCw4mEhQYDSSINwjPIwEBAQEGAQEBAR6LOoUFB4QtBZlthSqSFINZI4I7gVkigngBAQE X-IronPort-AV: E=Sophos;i="5.13,465,1427774400"; d="scan'208";a="170166060" Original-Received: from 104-247-241-95.cpe.teksavvy.com (HELO pastel.home) ([104.247.241.95]) by ironport2-out.teksavvy.com with ESMTP; 19 Oct 2015 09:31:09 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 14324628FE; Mon, 19 Oct 2015 09:31:09 -0400 (EDT) In-Reply-To: <877fmjflkk.fsf@mbork.pl> (Marcin Borkowski's message of "Mon, 19 Oct 2015 07:56:27 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:192092 Archived-At: >> A custom var shouldn't be modified programmatically. > Out of curiosity: why? Because Custom then can't change those chunks of code in order to get the desired value. E.g. there's a (setq foo 4) somewhere and the user uses Custom to set `foo' to 3. How is customize-save going to make sure that next time Emacs starts, `foo' will be set to 3 rather than 4? > I setq all my defcustoms, since I don't use Customize. As a user you're free not to (setq foo 4) in your ~/.emacs, of course, and since you don't use Custom, Custom won't have to try and set `foo', so everything's fine. And if you do try and set `foo' via Custom, then Custom will rightfully complain and you'll just get what you deserve. But as a package author, such a decision is very different: using (setq foo 4) or add-hook in your package means that all your users will have problems if they try to set this var via Custom. Stefan