I just realized that files created and edited by VUE are saved in DOS format (line ends with chr 10 and chr 13) instead of UNIX format (just chr 10, I think).
Is there a way to setup VUE to save files in UNIX format (should not that be default on linux)?

(We just upgraded server so it is a new installation. Don't think we had problems with it on the old server).

Yes, I think it should default to LF line terminators for UNIX (and CRLF for Windows). And I believe it does, provided that it is not overridden by the CRLF option in the INI.VUE (or CRLF ON at the VUE command prompt), or by OPTIONS=CRLF in the miame.ini file.

Only if none of the above is specified does it revert to the standard line terminators for the current operating system.

(Note that in all of the above cases, "CRLF" and "CRNL" are interchangeable.)

Besides checking the miame.ini directly, you can also use the SET command with no args, which will display the overall A-Shell line terminator status (per the miame.ini) as CRNL or NOCRNL

For VUE, in command mode it will display crnl on the options line if the terminator is CRLF (aka CRNL, aka ASCII 13,10). Else it will display nothing up there. Note that you can also launch VUE with the /T switch to trace the INI.VUE processing, which may clear up any uncertainty about which INI.VUE file is being processed.

When VUE (if configured to use LF terminators) loads a file containing CRLF terminators, it will display a warning message (unless CVTWARN=FALSE is set in the INI.VUE)

Note that for most A-Shell files (including CMD files, Basic source code, text files processed with INPUT LINE, etc.) either type of terminator is acceptable. But for files used directly by UNIX (shell scripts, config files, etc.), you typically must have the correct (LF) terminator.

If you are using the standalone (native UNIX) vue executable to edit native UNIX files, you should create an /etc/ini.vue file containing the following:

CRNL=OFF
BAKDIR=/tmp

The BAKDIR command specifies an alternate location for the .BAK (backup) file created by VUE whenever you save the current file. Putting these in some other location (not necessarily /tmp, but that seems like a good spot) eliminates the possibility of unexpected side effects from the existence of the .bak file. (For example, in some of the "rc" directories, the boot up sequence may execute every file in the directory, so if you edited one and ended up with a .bak in the same directory, it could result in the script being executed twice, resulting in all kinds of confusion.)

Thank you Jack. You were right on:
1. miame.ini had OPTIONS=CRLF that I commented out - what solved the problem.
2. I created /etc/ini.vue as you suggested.
Thanks again. You do provide best support.

I feel like I'm plowing old ground here, but I just had cause to look at this issue and it appears that standalone VUE on LINUX (3.2(289)) does not look at the /etc/ini.vue file if your working directory does not fall under the $MIAME directory. Is this the case, and is it deliberate? Could it be changed?

Also, could there be a way to specify an alternate (to /etc) directory for the ini.vue file, perhaps most logically the current working directory as VUE does when running under ASHELL?

Also, the /t trace option doesn't seem to work in the standalone LINUX version of VUE (3.2(289))

To address the last point first, in the standalone version of VUE you have to express the switches in UNIX-style, i.e.

$ vue -t somefile.txt

instead of

$ vue somefile.txt /t

The trace does work (at least in the 3.2(300) version I'm running here.)

I'll check the other issue next (which also sounds suspicious to me)...

According to my research, as of vue edit 286, for files outside the context of the MIAME device structure) it looks for ini.vue in the current directory before looking for it in the /etc directory.

I've confirmed this testing here with version 3.2(300).

So I'm not sure how to explain the symptoms you're seeing.

But it might be a good idea to start with an update. If you're running something compatible with RHEL4+ then you can at least grab version 298 here .

Otherwise, let me know which platform you're on and I'll generate a fresh build.

I've gone back and tried to replicate my "problem," but can't, it all seems to be working "as advertised." But I do have a bunch of ini.vue files scattered around, so I suspect the wrong one was being read. The trace mode should clear up any future confusion in my mind. I forgot about the "-t".

I did look at your development notes and have an idle question re VUE. I'm on 3.2(289), You wrote latest is edit 298, but entry in development notes 5.1.1214.0 for 28 April 2011 refers to VUE 3.0(307). Note that's 3.0 not 3.2. On the surface that looks like a reversion.

Sorry, that was a typo. It should say 3.2(307).

Jack

check $PATH

if ..../miame/bin is BEFOERE /etc

Then VUE from ASHELL in /bin executes using $MIAME and I expect INI.VUE from DSK0:

in the ".profile" I made a bad change

export MIAME=/vm/miame
export PATH=$MIAME:$PATH

Just an idea that I had putting ASHELL at the beginning of the PATH, but I changed it back.

I hope this helps.
RJ

The native version of vue only looks for ini.vue in two places:

1) the same directory as the file being edited.
2) /etc

It doesn't matter what the order of the PATH is, or whether the MIAME variable is defined. The assumption is that if you are executing vue outside of A-Shell, you don't really care about the way A-Shell is internally configured.

Note that you can use the -t switch to trace the searching and processing of the ini.vue files.

For example:

$ cd /tmp
$ vue -t /u1/miame/dsk0/001002/spool.log

A-Shell/VUE 3.2(300)

Trace: ini.vue searching : /u1/miame/dsk0/001002/ini.vue
Trace: ini.vue searching : /etc/ini.vue
Trace: opening : /etc/ini.vue
Trace: processing: CRNL=OFF
Trace: processing: BAKDIR=/tmp

Trace: checking : /u1/miame/dsk0/001002/spool.log - exists

Some of this behavior might have changed since 4.6, but there is nothing stopping you from using the latest native vue even with an older ashell. You can download version 310 (RHEL/CentOS) here

Great!!! I see it.

I'll install it.

Later,
RJ

Is there a newer version of standalone VUE for CENTOS 6.5? I copied my Red Hat ELS4 version to CENTOS 6.5 and it doesn't display. The text/file is there, I can ^N and see the cursor 'land' at the end of the line but the line is not displaying. When I hit escape and go to command mode the only thing on the screen is the A-Shell information at the bottom. Am I missing something? I'm using VT-100 emulation with PUTTY.

Hmmm..., not sure what is happening here. Sounds almost like it's just a matter of the color scheme for the editing text, but VT100 is monochrome.

I tried it here on CentOS 6.4 and by default Putty ends up with the TERM variable set to xterm, and VUE seems normal with green on black characters. If I manually switch TERM to vt100, then I get white characters on a black background. I'm not really an expert with Putty configuration (although I'm assuming from you description that the Putty configuration hasn't changed).

Do you get the same problem when you use VUE from a console window on the server?

Have you tried ZTERM or ATE with another TERM setting (wyse50, am7* ...)?

You didn't say what version you were running, but here's a copy of vue 3.2.315 compiled under CentOS 6.4: vue-3.2.315-el5-upd.tz

That's exactly what was wrong. After adjusting the colors all is well. Thank you!