all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathias Dahl <mathias.dahl@gmail.com>
To: emacs-devel@gnu.org
Subject: How can I put together a small bare bones "Emacs for scripting" package?
Date: Fri, 24 Jan 2020 16:34:08 +0100	[thread overview]
Message-ID: <CABrcCQ6ZtRCZayTXL72GodjwQ7LLcu0Qa1ZRuUE7F7jRqYQq-A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

Hi,

I am writing a lot of tools for my own use at work in Emacs. Sometimes I
like to share these tools with friends who are not using Emacs. I have
tried this a few times and I have ended up zipping my whole Emacs file
structure together with some scripts to start Emacs and do the stuff for
them.

This approach kind of works, but today I got thinking: how little could I
actually copy from my Emacs installation to have basic scripting working?
And with basic scripting I mean basic file handling (creating, checking
for, deleting), buffer handling and basic text manipulation stuff.

Obviously I would need emacs.exe. On my Windows installation it's around 9
MB. A bit on the big side for a scripting engine, still not bad by today's
standards.

But what would I need more, for Emacs to even start? If I knew the bare
minimum of what is needed to start, I think I would be able to add in any
additional features just by copying those Elisp files.

Any thoughts, comments or pointers to further reading?

Thanks!

/Mathias

[-- Attachment #2: Type: text/html, Size: 1254 bytes --]

             reply	other threads:[~2020-01-24 15:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24 15:34 Mathias Dahl [this message]
2020-01-24 15:49 ` How can I put together a small bare bones "Emacs for scripting" package? Eli Zaretskii
2020-01-24 16:18   ` Eli Zaretskii
2020-01-24 21:37     ` Mathias Dahl
2020-01-25  7:41       ` Eli Zaretskii
2020-01-25 20:12         ` Mathias Dahl
2020-01-27 14:36           ` Mathias Dahl

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=CABrcCQ6ZtRCZayTXL72GodjwQ7LLcu0Qa1ZRuUE7F7jRqYQq-A@mail.gmail.com \
    --to=mathias.dahl@gmail.com \
    --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.