all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, stefan@marxist.se, emacs-devel@gnu.org
Subject: Re: Preloading seq.el
Date: Thu, 29 Aug 2019 17:44:06 -0400	[thread overview]
Message-ID: <jwv7e6vsl6u.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87woevizhd.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 29 Aug 2019 20:43:42 +0200")

> That's fine with me, and I guess we should now start adding
> ;;;###autoload to seq.el whenever we feel like using functions from that
> file from the preloaded files.

[ Assuming this option does, which is not a given.  ]

Yes, I think it's a good first step: it will also *document* the places
where seq/cl-lib is needed so we can make a more informed choice.

When it doesn't work, adding a comment showing the code we'd use if we
could use seq/cl-lib could play a similar role.


        Stefan




  reply	other threads:[~2019-08-29 21:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 12:21 Preloading seq.el Stefan Kangas
2019-08-29 12:30 ` Lars Ingebrigtsen
2019-08-29 12:47   ` Eli Zaretskii
2019-08-29 12:50     ` Lars Ingebrigtsen
2019-08-29 14:59       ` Eli Zaretskii
2019-08-29 15:15         ` Lars Ingebrigtsen
2019-08-29 15:20           ` Eli Zaretskii
2019-08-29 15:35             ` Lars Ingebrigtsen
2019-08-29 18:41               ` Eli Zaretskii
2019-08-29 18:43                 ` Lars Ingebrigtsen
2019-08-29 21:44                   ` Stefan Monnier [this message]
2019-08-29 15:20   ` Stefan Monnier
2019-08-29 12:44 ` Eli Zaretskii
2019-08-31 12:33 ` Zhu Zihao
2019-08-31 12:38   ` Eli Zaretskii
2019-09-06  0:49     ` Juanma Barranquero
2019-09-06  7:12       ` Eli Zaretskii
2019-09-06  7:46         ` Robert Pluim
2019-09-06  8:23           ` Eli Zaretskii
2019-09-06 11:27         ` Juanma Barranquero

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=jwv7e6vsl6u.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=stefan@marxist.se \
    /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.