From: despen@verizon.net
To: help-gnu-emacs@gnu.org
Subject: Re: Porting emacs
Date: Sun, 20 Feb 2011 10:56:07 -0500 [thread overview]
Message-ID: <icfwriog2w.fsf@verizon.net> (raw)
In-Reply-To: mailman.3.1298208011.970.help-gnu-emacs@gnu.org
Oleksandr Gavenko <gavenkoa@gmail.com> writes:
> On 2011-02-19 23:27, despen@verizon.net wrote:
>> 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.
>>
> Yes this is may be best choice. Emacs comes with TRAMP mode
> which allow connect to remote machine via SSH and make
> editing on Linux/Windows host and all other job (as compilation,
> testing) on mainframe.
I haven't had much success with Emacs directly accessing mainframe
files. scp returns various errors.
z/OS can mount UNIX files with NFS but I haven't tried that either.
Instead I just ftp files back and forth. At first I thought that
might be a little slow but moving source files and listings back
and forth is pretty much instantaneous.
Other hints:
Use a .netrc
Write commands in Perl. Perl pipes to FTP are much easier
than C or shell.
next prev parent reply other threads:[~2011-02-20 15:56 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
2011-02-20 13:15 ` Oleksandr Gavenko
[not found] ` <mailman.3.1298208011.970.help-gnu-emacs@gnu.org>
2011-02-20 15:56 ` despen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=icfwriog2w.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.
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.