all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Zhu Zihao <all_but_last@163.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: Eli Zaretskii <eliz@gnu.org>, Zhu Zihao <all_but_last@163.com>,
	emacs-devel@gnu.org
Subject: Re: Why subr.el doesn't provide a feature?
Date: Sat, 31 Aug 2019 20:15:09 +0800	[thread overview]
Message-ID: <87o905jzua.wl-all_but_last@163.com> (raw)
In-Reply-To: <878sr97iej.fsf@tcd.ie>

On Sat, 31 Aug 2019 18:12:36 +0800,
Basil L. Contovounesios wrote:
> 
> Zhu Zihao <all_but_last@163.com> writes:
> 
> > Should we add a provide form for subr? I ask this question because I see a elisp
> > file wrote "(require 'subr)" and no doubt that it failed to run because subr.el
> > didn't provide such feature.
> 
> Can you show which file this was in?
> Perhaps the author meant to write (require 'subr-x).
> 
> -- 
> Basil
Thanks for your intention, but I think it just a misnomer because the author of
that elisp file had require subr-x explicitly.

And now subr requirement had been removed in
https://github.com/manateelazycat/snails/commit/4677daf80a8ee6d5202b98d1acde7a99c2294ec9

IMO, missing provide form is a counter-intuitive behavior because almost all
library have one(even backquote.el). I can't find a reason for why subr lacks
this, so I guess adding provide form for subr may breaks emacs bootstrap.




  reply	other threads:[~2019-08-31 12:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29  3:59 Why subr.el doesn't provide a feature? Zhu Zihao
2019-08-29  7:12 ` Eli Zaretskii
2019-08-29 10:59   ` Zhu Zihao
2019-08-29 12:38     ` Eli Zaretskii
2019-08-31 10:12     ` Basil L. Contovounesios
2019-08-31 12:15       ` Zhu Zihao [this message]
2019-08-31 13:21         ` Basil L. Contovounesios
2019-09-01  3:30       ` Richard Stallman
2019-09-01 16:02         ` Basil L. Contovounesios

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=87o905jzua.wl-all_but_last@163.com \
    --to=all_but_last@163.com \
    --cc=contovob@tcd.ie \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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.