[Info-vax] Some questions on software for VMS 7.3 VAX

[Johnny Billquist]

On 2016-01-26 13:57, lists at openmailbox.org wrote:
> On Tue, 26 Jan 2016 11:18:59 +0100
> Johnny Billquist via Info-vax <info-vax at rbnsn.com> wrote:
>
>> On 2016-01-26 10:54, lists at openmailbox.org wrote:
>>> On Tue, 26 Jan 2016 09:35:17 +0000
>>> lists--- via Info-vax <info-vax at rbnsn.com> wrote:
>>>
>>>> On Tue, 26 Jan 2016 09:49:54 +0100
>>>> hb via Info-vax <info-vax at rbnsn.com> wrote:
>>>>
>>>>> On 01/26/2016 08:02 AM, lists at openmailbox.org wrote:
>>>>>> I thought you said you got it to crash by control-X space. If so this
>>>>>> isn't limited to dired. Maybe the whole thing needs to be
>>>>>> compiled /noopt and then it will probably be unusable. The other
>>>>>> option if you really want to compile it like it was "designed" to be
>>>>>> compiled if there indeed is any such thing would be to get the
>>>>>> comtemporaneous port of gcc for VAX/VMS and build with that. gnu
>>>>>> crapware is not guaranteed to build or work with anything but gcc and
>>>>>> bash and then only sometimes.
>>>>>
>>>>> With ^X^F and space, which for me seems to be more or less the same
>>>>> thing as meta-x and dired.
>>>
>>> It is definitely not the same as on UNIX/Linux. control xf should ask
>>> you what file you want to edit and control x control f should just move
>>> forward in the current buffer. Maybe this also means something...
>>
>> Huh?
>> ^X ^F should be "Find file". It should never move forward.
>
> I said that. "control xf should ask you what file you want to edit"

So what do you mean by "control x control f" then???
And how would you write out control x followed by a normal f?

	Johnny