From: despen@verizon.net
To: help-gnu-emacs@gnu.org
Subject: Re: Porting emacs
Date: Sat, 19 Feb 2011 18:27:24 -0500 [thread overview]
Message-ID: <iclj1bobab.fsf@verizon.net> (raw)
In-Reply-To: mailman.8.1298155303.7110.help-gnu-emacs@gnu.org
Boris Moskalev <BMoskalev@rocketsoftware.com> writes:
> Hello
>
> I'm trying to porting emacs to z/OS now. And now I have some problem
> with porting due there is using EBCDIC encoding. Could you help me
> for that problem. May be exist simple answer and I just have to add
> codes of EBCDIC somewhere.
I should add that I do mainframe work all day on a Linux PC using Emacs.
I never had a desire to run the editor on z/OS, I think you're going
to see performance issues.
A better plan is to develop a set of tools for moving data, submitting
compiles, run TSO commands, do compiles, etc.
next prev parent reply other threads:[~2011-02-19 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.8.1298155303.7110.help-gnu-emacs@gnu.org>
2011-02-19 23:23 ` Porting emacs despen
2011-02-19 23:27 ` despen [this message]
2011-02-20 13:15 ` Oleksandr Gavenko
[not found] ` <mailman.3.1298208011.970.help-gnu-emacs@gnu.org>
2011-02-20 15:56 ` despen
2011-02-18 12:15 Boris Moskalev
2011-02-20 13:10 ` Oleksandr Gavenko
2011-02-20 13:31 ` Oleksandr Gavenko
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=iclj1bobab.fsf@verizon.net \
--to=despen@verizon.net \
--cc=help-gnu-emacs@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.
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).