all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: 32893@debbugs.gnu.org
Cc: jidanni@jidanni.org
Subject: bug#32893: Let him know source code is available
Date: Mon, 01 Oct 2018 18:56:18 -0400	[thread overview]
Message-ID: <qewor1nunh.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87zhvxgx1y.fsf_-_@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Tue, 02 Oct 2018 05:46:17 +0800")

積丹尼 Dan Jacobson wrote:

> B> most likely caused by missing recommended package emacs-el.
>
> Dear bug-gnu-emacs, I got an idea for 32893@debbugs.gnu.org:
> Show the same thing no matter if the user has the .els installed or not.

Emacs does not support installing without its .el files and makes no
provision for it. It's something downstream distributions added back
when disk space was an issue (I guess?). They get to keep all the pieces
from the resulting breakage. :)
Personally I think it should this separation should just go away.





  reply	other threads:[~2018-10-01 22:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r2h9ahig.fsf@tethera.net>
     [not found] ` <87tvm5pye2.fsf@jidanni.org>
     [not found]   ` <handler.910021.D910021.153840454221352.notifdone@bugs.debian.org>
2018-10-01 12:44     ` bug#32893: describe-variable doesn't metion what lisp file created the variable 積丹尼 Dan Jacobson
2018-10-01 12:51       ` Noam Postavsky
2018-10-01 13:08         ` 積丹尼 Dan Jacobson
2018-10-01 13:41           ` Noam Postavsky
2018-10-01 14:13             ` 積丹尼 Dan Jacobson
2018-10-01 13:43           ` Eli Zaretskii
2018-10-01 21:46       ` bug#32893: Let him know source code is available 積丹尼 Dan Jacobson
2018-10-01 22:56         ` Glenn Morris [this message]
2018-10-01 23:04           ` Glenn Morris
2018-10-02  0:28       ` bug#32893: GNU wishes Debian not split out .els anymore 積丹尼 Dan Jacobson

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=qewor1nunh.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=32893@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    /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.