From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: [External] : Re: Locating file via load-path Date: Fri, 09 Aug 2024 20:39:48 +0300 Message-ID: <868qx5lhnf.fsf@gnu.org> References: <868qx6n9ug.fsf@gnu.org> <86zfpml0sq.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18978"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Fri Aug 09 19:40:35 2024 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1scTbO-0004oJ-Um for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 09 Aug 2024 19:40:34 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1scTaw-0002sI-Rm; Fri, 09 Aug 2024 13:40:06 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1scTan-0002qF-OH for help-gnu-emacs@gnu.org; Fri, 09 Aug 2024 13:39:59 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1scTak-00037F-7S for help-gnu-emacs@gnu.org; Fri, 09 Aug 2024 13:39:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=Km3X0Q65bSmqHtM1AmebYG6VZTf06BG6lUMBD9xhWeo=; b=kHIcEM2IEg0sUuNZodf+ Mg93uf1akevWU74+3S3J7nBhzh9U3GKP4q97P6XFeDm4YA5DJ1K3Qti/KvQsBWAFZS6D/viOGG3/G IxlBV8XIMStkS4HdHltq+pP8nQmy0a7aklKuyP8N19VdJKyP85Raq0q3Hn6OgOXVThw0+c5wZ7vr9 S3GI8iFFUJaDVaJPPsENFTJK3DPSfTlTQ7ZG5wrozmi7YRJkNymNOOReCp3iAUVfCsvNeKtkd/k7D ziTFWVwuFM1fQ7tUoHx3J+eg7eNb/TnF5nyM3Vaiw3Qa7NxdNfmvy0DHSUZfmrr0h+qF/t9w2MTLx uAkI753IRlaOSg==; In-Reply-To: (message from Drew Adams on Fri, 9 Aug 2024 16:19:01 +0000) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:147575 Archived-At: > From: Drew Adams > Date: Fri, 9 Aug 2024 16:19:01 +0000 > > > > > Why cl-pushnew ? > > > > > > Either is OK. The doc of `add-to-list' says: > > > > > > you are usually better off using `push' or `cl-pushnew'. > > > > Talk about citation out of context. The full quotation is > > > > This is handy to add some elements to configuration variables, > > but please do not abuse it in Elisp code, where you are usually > > better off using ‘push’ or ‘cl-pushnew’. > > > > IOW, don't (ab)use add-to-list if all you need is to add a new element > > to some list of elements. add-to-list is for adding path elements to > > variables like load-path. > > That text says use it mainly for user ("configuration") > variables, not generally for Lisp code. And it neither > says nor suggests anything about lists of path elements. It did, albeit not explicitly enough. Now it does that more clearly. > > > It doesn't say why, and neither does the Elisp manual. > > > > Oh, yes, it does, see above. > > No, there's nothing about "why" above. Only if you refuse to think about what it says. > May I humbly encourage you to review the following > mails in this very list from Stefan Monnier on the > subject, back in 2013, during his tenure as the > Emacs maintainer (thread "Is add-to-list supposed > to work when lexical-binding is t?"): > > Not in chronological order, but perhaps in order of > relevance and understanding for us, here: Not relevant to this discussion.