From: "Elias Mårtenson" <lokedhs@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: APL input revisited
Date: Thu, 20 Feb 2014 00:42:30 +0800 [thread overview]
Message-ID: <CADtN0WJc9G74hS5D8ea6mWeYz4Awb+co188Q2YonWfhPm6CvEA@mail.gmail.com> (raw)
In-Reply-To: <jwvob23gp7n.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
I'm still waiting for my employer to clear the necessary documents.
Then there is a second issue. The package contains documentation snippets
(for the integrated documentation buffers) that is copyright IBM (they gave
me permission to use the material). However, they still keep the copyright
to this material.
The mode works fine without it, but there is practically no integrated
documentation then. I've been thinking of splitting it so that the
IBM-derived documentation is in a separate optional package, or something
like that. I decided not to think about it until my employers legal
department finally decides to sign the documents.
If anyone is willing to write GNU-licensed reference documentation for GNU
APL, that would also be a good solution.
Until all of this is cleared, it'll be available in MELPA.
Regards,
Elias
On 19 February 2014 22:20, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > Since I started developing gnu-apl-mode a few months ago (it has grown
> > quite a lot recently), I have been thinking of the best ways to deal with
> > APL input in Emacs.
>
> Any news on adding it to GNU ELPA?
>
>
> Stefan
>
[-- Attachment #2: Type: text/html, Size: 1801 bytes --]
next prev parent reply other threads:[~2014-02-19 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 8:39 APL input revisited Elias Mårtenson
2014-02-19 9:46 ` Emilio Lopes
2014-02-19 14:20 ` Stefan Monnier
2014-02-19 16:42 ` Elias Mårtenson [this message]
2014-02-19 18:21 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADtN0WJc9G74hS5D8ea6mWeYz4Awb+co188Q2YonWfhPm6CvEA@mail.gmail.com \
--to=lokedhs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).