[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Coding System handler to access Vax-VMS/OpenVMS/RMS text files from

From: Peter Milliken
Subject: Re: Coding System handler to access Vax-VMS/OpenVMS/RMS text files from Windows Emacs
Date: Sat, 18 Sep 2021 14:26:14 +1000


It's been 20 years since I last used Emacs on a Windows computer to edit files under VMS, but from memory, I used Tramp Mode (Transparent Remote Access Multiple Protocols), it handled all of that stuff transparently.

Best of luck,

On Fri, Sep 17, 2021 at 9:10 PM Kerry, Richard <> wrote:

Does anyone know whether there is a Coding System handler available that will allow me to use Windows Emacs to view text files originating from a Vax system?  Ie from a system running Vax/VS or OpenVMS.  The filing system in these is called RMS, which means it is difficult to successfully search for Emacs issues relating to it using that term.
I have established that text files on that system are not stored using a line terminator/separator character, like many other OSs tend to do (ie CR and/or LF chars).  Instead it uses a system where each line starts with two bytes representing its length.
My understanding that emacs uses a Coding System driver to interface between the underlying files and its string representation.  I would expect that if there is a VMS implementation of Emacs (which there is, or has been) then it would include this handling, however I have the files on a Windows PC so I need Windows Emacs to be able to access them.

Has anyone done this?
Is there just an incantation that I need to enable it, or might I have to get into writing the driver myself?


Richard Kerry

BNCS Engineer, SI SOL Telco & Media Vertical Practice

M: +44 (0)7812 325518

2nd Floor, MidCity Place, 71 High Holborn, London, WC1V 6EA

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]