From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: use-package has been merged into emacs-29 Date: Sat, 10 Dec 2022 12:34:03 -0800 Message-ID: References: <878rjgd0ej.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34262"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, John Wiegley To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 10 21:34:30 2022 Return-path: Envelope-to: ged-emacs-devel@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 1p46YH-0008j0-Kg for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Dec 2022 21:34:29 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p46Xx-0002ck-Lm; Sat, 10 Dec 2022 15:34:09 -0500 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 1p46Xw-0002Y7-4k for emacs-devel@gnu.org; Sat, 10 Dec 2022 15:34:08 -0500 Original-Received: from mail-oa1-x2a.google.com ([2001:4860:4864:20::2a]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1p46Xu-0002RV-GZ; Sat, 10 Dec 2022 15:34:07 -0500 Original-Received: by mail-oa1-x2a.google.com with SMTP id 586e51a60fabf-12c8312131fso3945890fac.4; Sat, 10 Dec 2022 12:34:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date:message-id:reply-to; bh=b4sT6UhjszmAB7bwwMgqend0pZnmicdzO6q8sjHHsIk=; b=D0wzTPAVgIuUWt5I/Hul6AfrfqEMBILiXwp0LHLEo7XMvzcQYsxlbLsCkYqMbsGGns bdfboM6huOFPjWWstMX6YN4F8qxA5d7vmAF2b6VN10kWlcyWjOrdf5E+1ochnm1BiJ6G eIFNa5R6VAQHBMwzib/KWLPAh0lm5Z4wnaf4wThHzrGzUhX7p+jeKbwv2eC+q7CAzWGS 6DVR+uBeBYbPZpIPQyEnUqGfI/Hhl4grvXg1x4pi6wcdyq400sOGYkqUOQcS+30nTXr2 fCegW1Ih58FNpXxdxS0/fYW/TmwyGKnq4bpxeSzl2q6RgSHxsQQYsc14UKrZ0KS4jM/m PFAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=b4sT6UhjszmAB7bwwMgqend0pZnmicdzO6q8sjHHsIk=; b=bHESFQO3A9J5u17CtKt7wM7dDFOx0bqniQqTt5A7jpzUvkQusd5EdseRxsUJ3Hwtj4 CMRHokBsXTcH8BIEf450AjFT1t2tDk8QEM5bQuJILIWLr16N6n6vKA/wPrQh59V+B1Jy eelTWqfNYMnlb8MbdwCRRMklgDZjGokBL5VawJpS7LFetW0oM7tY6cRPXLA/eN+pGfKA fs/d4IZBNeoPqwEN87erLZdlqAUDkzksvHgzJQlrPzzbqn0bZfJLzG+Dy/kXZsC3twmQ Q4MyFS3JXej7ChxiFPbYt3ufbk6z4LVJsPZMc1nMbHRljORj5/TFjPfL1azoBQJhGS9B UFbw== X-Gm-Message-State: ANoB5pnBkOgmH8hD7g8tgcif77nSwt+Y/2igXQ6SXyrlqt9UP+ISwBRp YW2zUpW98DciWPUFFNVVLsAxRbwmfhFPJHaJVN0= X-Google-Smtp-Source: AA0mqf57M1kTeYEhysHyra3uoXMqfQX+cxGYHZ0hlXvbkuSGZAFMD23lk0b7H28AfQ8d1T6sGCk6R2tQfbRKIAg1LNA= X-Received: by 2002:a05:6870:7813:b0:148:28c1:3d46 with SMTP id hb19-20020a056870781300b0014828c13d46mr78605oab.199.1670704444268; Sat, 10 Dec 2022 12:34:04 -0800 (PST) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Sat, 10 Dec 2022 12:34:03 -0800 In-Reply-To: <878rjgd0ej.fsf@posteo.net> X-Hashcash: 1:20:221210:johnw@gnu.org::OZmGUvXrtJYOF7qx:22xo Received-SPF: pass client-ip=2001:4860:4864:20::2a; envelope-from=stefankangas@gmail.com; helo=mail-oa1-x2a.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:301131 Archived-At: Philip Kaludercic writes: > - It appears to be mentioning a few packages that are not available on > GNU ELPA or NonGNU ELPA (e.g. git-gutter+, eruby-mode, dash-at-point, > ess, color-moccur, moccur-edit, unfill). Should they be replaced > with other packages to make sure the examples are consistently > reproducible? Yup. All examples like that come from the old README.md. I got rid of most of them, but there are several left to fix. I think we should replace them with either some made up package name (e.g. "foo" or "some-package") or, in order of preference: built-in, GNU ELPA, NonGNU ELPA. IMO, replacing NonGNU ELPA with GNU ELPA packages is usually an improvement, and so is replacing GNU ELPA packages with built-in ones. > - MELPA is mention under vindex `use-package-always-pin', is this ok. > AFAIR there was some decision to not mention MELPA in the official > documentation (currently this also appears to be the only instance). It's only mentioned to explain how to work around its date-based versioning scheme (by always installing packages from NonGNU ELPA instead). Which I think should be fine. > - It appears that use-package is sometimes formatted using @code and > sometimes not. I can't make out a consistent rule. I've tried to follow this: - Format use-package with no markup when referring to the package. - Use @code{use-package} when referring to a macro call. Does that make sense? > - GNU ELPA is also inconsistently marked up as a single or two separate > acronyms. In one sense, @acronym{GNU ELPA} is better, as that is the full name. One way of looking at it is that the acronym for "GNU Emacs Lisp Package Archive" is actually the acronym "GNUELPA", which we just happen to typeset with a space for increased legibility. But we also have @acronym{NonGNU ELPA}, and I guess we are now looking at just a name that is not really an acronym at all? So perhaps we should just write out the names GNU ELPA and NonGNU ELPA without any markup? Because we also don't want "@acronym{NonGNU} @acronym{ELPA}", I suppose?