Hello Peter, Thanks for getting back to me. Thank you for your suggestion - I have had a look but I think Tramp mode is not quite what I need, though I can see how it might appear to fit. I too have not edited files on VMS for about 20 years, and even now that is not what I am seeking to do. It looks to me like Tramp will let me edit RMS files on a Vax provided I have a running Vax to edit the files on. My actual situation is that I have been given a dump of a Vax disk, as Windows files. The flies appear to be binary copies so are in RMS format and so that is what I need to access, files on windows that are in RMS format. It looks like Emacs has a system for handling Coding Systems that ought to be able to handle this - or to allow me to write my own handler, and that is what I am looking for information on.
And I have already written an application that can convert these files into conventional Windows format. I would like to be able to view the files without needing to convert them first. I think I may need to ask on the Emacs development list. Regards, Richard, From: Peter Milliken <peter.milli...@gmail.com> Sent: 18 September 2021 05:26 To: Kerry, Richard <richard.ke...@atos.net> Cc: help-emacs-windows@gnu.org Subject: Re: Coding System handler to access Vax-VMS/OpenVMS/RMS text files from Windows Emacs Caution! External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe. Richard, 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, Peter On Fri, Sep 17, 2021 at 9:10 PM Kerry, Richard <richard.ke...@atos.net<mailto:richard.ke...@atos.net>> 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? Regards, Richard. 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 richard.ke...@atos.net<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwebmail.siemens-it-solutions.com%2Fowa%2Fredir.aspx%3FC%3D9fb20d019e3e4cb99344d708709a3177%26URL%3Dmailto%253arichard.kerry%2540atos.net&data=04%7C01%7Crichard.kerry%40atos.net%7C06d81e45f4cc436d547608d97a5c8070%7C33440fc6b7c7412cbb730e70b0198d5a%7C0%7C0%7C637675359980138416%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yqgH37J38xgmkHDLCHHHlK%2FOTAfF3%2FnmvqZheKaaQ7c%3D&reserved=0> 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.
