unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefankangas@gmail.com>,
	Daniel Fleischer <danflscr@gmail.com>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: [PATCH] Package Installation in Tutorial
Date: Fri, 3 Dec 2021 20:24:55 +0000	[thread overview]
Message-ID: <SJ0PR10MB54880BBEACA91D7E83D5AE3BF36A9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CADwFkm=tAPN-u-hEz8g_a3FLLRKkr+gSXfpYrORkHNPWJvfQnA@mail.gmail.com>

> > I'd suggest that teaching basic customization
> > should be more useful/important than teaching
> > how to install an external package.
> 
> That sounds like another fine addition to make.  Maybe someone could
> write up 15-20 lines or so about how to use `M-x customize'?

+1.

Assuming that such additions are needed.  That's
the question.

One could argue, without reasons given, for almost
any Emacs this-or-that to be gone over in the basic
tutorial.  It's good to be able to _reason_ about a
change proposal, however.

Any number of "fine additions" are conceivable.
That doesn't make any or all of them desirable.

A proposal to change the status quo is usually
accompanied by some reasons for the change.

> > Fine.  So your argument is that _first timers_
> > don't know how to install packages and they're
> > dying to know that.  They need that, from the
> > get-go.
> 
> Correct.

So I understood correctly from the beginning.

And the evidence for that claim is?

  reply	other threads:[~2021-12-03 20:24 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 17:30 [PATCH] Package Installation in Tutorial Daniel Fleischer
2021-12-01 18:06 ` Daniel Martín
2021-12-01 19:25   ` Stefan Kangas
2021-12-01 19:25 ` Stefan Kangas
2021-12-02  6:42   ` Daniel Fleischer
2021-12-02  9:09   ` Juri Linkov
2021-12-02 11:17     ` Stefan Kangas
2021-12-03  6:57       ` Daniel Fleischer
2021-12-03 16:29         ` [External] : " Drew Adams
2021-12-03 17:48           ` Daniel Fleischer
2021-12-03 18:53             ` Stefan Kangas
2021-12-03 18:56               ` Drew Adams
2021-12-03 18:53             ` Drew Adams
2021-12-03 19:24               ` Stefan Kangas
2021-12-03 20:24                 ` Drew Adams [this message]
2021-12-03 22:54                   ` Stefan Kangas
2021-12-03 21:19               ` Daniel Fleischer
2021-12-03 23:01                 ` Drew Adams
2021-12-04  8:06                 ` Eli Zaretskii
2021-12-04 11:04                   ` Daniel Fleischer
2021-12-04 18:16                     ` Drew Adams
2021-12-04 21:06                       ` Daniel Fleischer
2021-12-04 17:38                   ` Drew Adams
2021-12-04  5:44               ` Richard Stallman
2021-12-04  8:04                 ` Eli Zaretskii
2021-12-04 17:20                   ` Drew Adams
2021-12-04 17:18                 ` Drew Adams
2021-12-03 17:00         ` Lars Ingebrigtsen
2021-12-04 13:08           ` Stefan Kangas
2021-12-04 14:15             ` Daniel Fleischer
2021-12-04 16:29               ` Eli Zaretskii
2021-12-04 20:38                 ` Daniel Fleischer
2021-12-04 21:58                   ` Lars Ingebrigtsen
2021-12-05  9:37                     ` Daniel Fleischer
2021-12-05 20:52                       ` Lars Ingebrigtsen
2021-12-05 10:21                   ` Eli Zaretskii
2021-12-05 10:54                     ` Daniel Fleischer
2021-12-05 11:44                       ` Stefan Kangas
2021-12-05 15:33                         ` Daniel Fleischer
2021-12-06 10:36                           ` Daniel Fleischer
2021-12-06 14:10                           ` Stefan Kangas
2021-12-05 11:29                     ` Stefan Kangas

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=SJ0PR10MB54880BBEACA91D7E83D5AE3BF36A9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=danflscr@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@gmail.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).