From: Pascal Bourguignon <pjb@informatimago.com>
Subject: Re: gnu.emacs.sources ettiqutte question
Date: Tue, 15 Aug 2006 03:00:50 +0200 [thread overview]
Message-ID: <87hd0e3j99.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: 1155603049.974865.106650@i42g2000cwa.googlegroups.com
"Þorne" <ego111@gmail.com> writes:
> I wrote a generic mode for syntax highlighting IBM AS/400 CL (Control
> Language) files. It seems to work so far.
>
> Leaving aside the question of who really cares or wants such an obscure
> thing, i am wondering about the rules for posting on gnu.emacs.sources.
> Emacs is free and the code for the mode is free, but it is only useful
> for editing files which only run on a distinctly non-free operating
> system--and one for which i suspect there is no free replacement going
> to be written... ever.
This should not be an impediment to make and distribute free software.
This is really a strategical question, and given the obscurity of the
proprietary software concerned, it is not very important. It might
even suscitate the development of free implementations!
What about an AS400 Control Language unix shell? ;-)
> So i guess there is an analogy with, say, an editing mode for java
> files back when there was no free java compiler. Or something.
> Anyway, i'm interested to know if posting such a thing would likely be
> frowned upon.
I don't think so.
--
__Pascal Bourguignon__ http://www.informatimago.com/
"You can tell the Lisp programmers. They have pockets full of punch
cards with close parentheses on them." --> http://tinyurl.com/8ubpf
next prev parent reply other threads:[~2006-08-15 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 0:50 gnu.emacs.sources ettiqutte question Þorne
2006-08-15 1:00 ` Pascal Bourguignon [this message]
2006-08-15 9:16 ` Tim X
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=87hd0e3j99.fsf@thalassa.informatimago.com \
--to=pjb@informatimago.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.
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).