From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Thibaut Verron <thibaut.verron@gmail.com>
Cc: Caio Henrique <caiohcs0@gmail.com>,
Naoya Yamashita <conao3@gmail.com>,
Stefan Kangas <stefankangas@gmail.com>,
johnw@gnu.org, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Include leaf in Emacs distribution
Date: Tue, 13 Oct 2020 10:29:06 -0400 [thread overview]
Message-ID: <jwv4kmy8aoz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAFsi02R=JMGc5fMzgijOsLAr=-q6XBH-37ximkRT-dhNYVCQ5g@mail.gmail.com> (Thibaut Verron's message of "Tue, 13 Oct 2020 16:14:10 +0200")
> What would this gnu-elpa package contain, exactly?
No need for the conditional. You can look at the package
https://elpa.gnu.org/packages/gnu-elpa.html
or install it with `M-x package-install`.
> All the packages from GNU Elpa?
Currently, not quite.
>> except for the `diminish` which seems orthogonal (if we think it
>> should be diminished by default, then we should change undo-tree
>> accordingly).
> But diminish.el is only available on Melpa (and, I assume, soon on
> non-GNU Elpa).
I don't think you need this specific package in order to get the
corresponding change in behavior for undo-tree.
What I meant is that if we think that undo-tree should be `diminish`ed
by default, then it means we consider the default behavior of
`undo-tree` to be wrong and we should consider it as a bug to fix in
`undo-tree`.
Stefan
next prev parent reply other threads:[~2020-10-13 14:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 1:37 Include leaf in Emacs distribution Naoya Yamashita
2020-10-08 9:00 ` Ergus
2020-10-08 9:22 ` Naoya Yamashita
2020-10-10 10:11 ` Eli Zaretskii
2020-10-11 5:24 ` Richard Stallman
2020-10-11 8:39 ` Naoya Yamashita
2020-10-11 9:52 ` Thibaut Verron
2020-10-11 16:50 ` Naoya Yamashita
2020-10-11 17:12 ` Thibaut Verron
2020-10-12 2:10 ` Naoya Yamashita
2020-10-12 20:23 ` Ergus via Emacs development discussions.
2020-10-11 17:02 ` Stefan Kangas
2020-10-11 16:51 ` Stefan Kangas
2020-10-12 20:53 ` Mingde (Matthew) Zeng
2020-10-11 17:22 ` Stefan Kangas
2020-10-12 1:35 ` Naoya Yamashita
2020-10-12 22:13 ` Stefan Kangas
2020-10-12 22:19 ` Qiantan Hong
2020-10-12 22:39 ` Caio Henrique
2020-10-13 13:23 ` Stefan Monnier
2020-10-13 14:14 ` Thibaut Verron
2020-10-13 14:29 ` Stefan Monnier [this message]
2020-10-13 15:29 ` Thibaut Verron
2020-10-18 9:32 ` Phil Sainty
2020-10-13 15:25 ` Caio Henrique
2020-10-23 2:37 ` Naoya Yamashita
2020-10-23 3:41 ` John Wiegley
2020-10-23 14:33 ` Stefan Monnier
2020-10-23 15:53 ` Naoya Yamashita
2020-10-23 16:46 ` Warnings in init files (was: Include leaf in Emacs distribution) Stefan Monnier
2020-10-23 18:11 ` Include leaf in Emacs distribution T.V Raman
2020-10-23 18:41 ` Stefan Kangas
2020-10-23 20:04 ` John Wiegley
2020-11-16 5:29 ` Naoya Yamashita
2020-11-17 0:39 ` John Wiegley
2020-11-20 11:04 ` Naoya Yamashita
2020-11-20 11:29 ` Pankaj Jangid
2020-11-20 15:44 ` T.V Raman
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=jwv4kmy8aoz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=caiohcs0@gmail.com \
--cc=conao3@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=stefankangas@gmail.com \
--cc=thibaut.verron@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).