From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 25355@debbugs.gnu.org
Subject: bug#25355: 26.0.50; Provide function to non-destructively replace buffer contents
Date: Sun, 07 May 2017 22:19:07 +0300 [thread overview]
Message-ID: <83y3u8cw5w.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkQF1tqKHYV2N9iyJ7Y6Qmohbfz_HPHRRxHfd0Tcf3+5-Q@mail.gmail.com> (message from Philipp Stephani on Sun, 07 May 2017 18:45:07 +0000)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sun, 07 May 2017 18:45:07 +0000
> Cc: 25355@debbugs.gnu.org
>
> What do you mean by "use"? Treat it as an optional library, like we
> do with image support and GnuTLS? I thought you wanted this feature
> to be present in every Emacs, not only Emacs linked against that
> library.
>
> I just want to link it statically by adding the required source files to the source tree, like we do for e.g.
> oldXmenu.
That means we need legal papers, AFAIU.
> If this requires copyright assignment, then I'll stop immediately and reimplement this as a dynamic module
> outside of Emacs.
Maybe I'm missing something, but I don't see how legal paperwork could
be avoided in this case. Perhaps ask RMS.
next prev parent reply other threads:[~2017-05-07 19:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 12:45 bug#25355: 26.0.50; Provide function to non-destructively replace buffer contents Philipp
2017-01-04 13:38 ` npostavs
2017-05-07 17:44 ` Philipp Stephani
2017-05-07 18:05 ` Eli Zaretskii
2017-05-07 18:21 ` Philipp Stephani
2017-05-07 18:37 ` Eli Zaretskii
2017-05-07 18:45 ` Philipp Stephani
2017-05-07 19:19 ` Eli Zaretskii [this message]
2017-05-14 19:30 ` Philipp Stephani
2017-05-15 1:47 ` Richard Stallman
2017-05-15 2:49 ` Eli Zaretskii
2017-05-16 1:08 ` Richard Stallman
2017-05-15 22:09 ` Glenn Morris
2017-06-12 21:17 ` Philipp Stephani
2017-06-17 13:47 ` Philipp Stephani
2017-06-17 16:06 ` Eli Zaretskii
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=83y3u8cw5w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25355@debbugs.gnu.org \
--cc=p.stephani2@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 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.