all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Krystian Samp <samp.krystian@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 72961@debbugs.gnu.org, philipk@posteo.net
Subject: bug#72961: Possible documentation improvement: Clarification for package installation
Date: Thu, 5 Sep 2024 11:23:12 +0200	[thread overview]
Message-ID: <CAKsGKCi74xqKqVDJRBqSy6VLoQN-edUuD==a_=YSqV=DOzBNbg@mail.gmail.com> (raw)
In-Reply-To: <86frqe4gb3.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]

This makes sense, thanks for taking the time to explain this in detail.

On Thu, 5 Sept 2024 at 11:10, Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Krystian Samp <samp.krystian@gmail.com>
> > Date: Thu, 5 Sep 2024 09:44:14 +0200
> > Cc: philipk@posteo.net, 72961@debbugs.gnu.org
> >
> > Thanks,
> >
> > imho it'd be also useful to add there that Emacs will make the installed
> packages available automatically at
> > startup. Now it reads that Emacs will add them to `load-path` but I
> wouldn't infer from this that Emacs will also
> > make these packages available. And right after that we say that "...
> making the above manual customizations
> > unnecessary for such packages" which specifically refers to loading, not
> only adding to `load-path`. Just two
> > cents,
>
> All of this is already described in the node "Package Installation",
> to which this node points.  Cross-references in the manual are there
> for a reason: interested readers are expected to follow them and to
> read what the referenced nodes say.  We don't have the same
> information in more than one place in the manual because that would
> make it a maintenance burden: all of those places have to be found and
> updated when something changes.  Our conventions are to describe each
> feature in full in a single place, and then have cross-references to
> that one place in other related places.
>
> So I decided not to expand on this more in the sections which is only
> tangentially related to package installation.  This text is there so
> as to avoid creating an impression that what this node describes must
> be done for packages installed via package.el.  It doesn't (and should
> not) pretend to describe installation via package.el.
>

[-- Attachment #2: Type: text/html, Size: 2332 bytes --]

  reply	other threads:[~2024-09-05  9:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02 10:41 bug#72961: Possible documentation improvement: Clarification for package installation Krystian Samp
2024-09-02 12:03 ` Eli Zaretskii
2024-09-02 18:49   ` Philip Kaludercic
2024-09-04 21:52     ` Krystian Samp
2024-09-05  6:25       ` Eli Zaretskii
2024-09-05  7:44         ` Krystian Samp
2024-09-05  9:10           ` Eli Zaretskii
2024-09-05  9:23             ` Krystian Samp [this message]
2024-09-05  6:24     ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKsGKCi74xqKqVDJRBqSy6VLoQN-edUuD==a_=YSqV=DOzBNbg@mail.gmail.com' \
    --to=samp.krystian@gmail.com \
    --cc=72961@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=philipk@posteo.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.