On 1/9/2025 8:01 AM, hb0815 wrote:
$ gdiff -ub lib.pas-orig lib.pas
$ gdiff -ub lib.for-orig lib.for
For those that do not speak diffish:
On 2025-01-13, Arne Vajhøj <arne@vajhoej.dk> wrote:
On 1/9/2025 8:01 AM, hb0815 wrote:
$ gdiff -ub lib.pas-orig lib.pas
$ gdiff -ub lib.for-orig lib.for
For those that do not speak diffish:
Then those people would benefit from learning it IMHO.
It is far, far, superior to VMS DIFF, especially in the unified diff format used in the above command. If the licence allows it, then it would be an excellent addition to standard VMS, maybe invoked as a new qualifier on the VMS DIFF command.
it should be
possible to get diffs outside a repository with "git diff --noindex".
That said, I tried it just now and couldn't get it to work.
On 1/17/25 8:07 AM, Craig A. Berry wrote:Using git to get a the output in the Unix/GNU diff style seems overkill
it should be
possible to get diffs outside a repository with "git diff --noindex".
That said, I tried it just now and couldn't get it to work.
It does work, but not for VFC files and it cannot handle version numbers
in a filename, so its usefulness on VMS is pretty limited.
On 1/17/25 15:39, Craig A. Berry wrote:
On 1/17/25 8:07 AM, Craig A. Berry wrote:
it should be
possible to get diffs outside a repository with "git diff --noindex".
That said, I tried it just now and couldn't get it to work.
It does work, but not for VFC files and it cannot handle version numbers
in a filename, so its usefulness on VMS is pretty limited.
Using git to get a the output in the Unix/GNU diff style seems overkill
to me.
As you probably know, if you can get the GNV diff utility, you can run
it from DCL.
To handle VMS file version, there is a workaround. Assumed gdiff is the
DCL symbol for the GNV diff utility:
$ pipe define/user decc$filename_unix_only 0 && -
 gdiff -ub sys$disk:[]x.com;1 sys$disk:[]x.com;2
As indicated, you may need a full file spec and the files have to be in Stream_LF record format.
git is available for OpenVMS x86. GNV is not yet, as far as I have seen,
so it seemed worth giving a quick try with something people may already
have installed. And to be a bit pedantic, there is no "GNV diff"; there
is GNU diff, which may have been included in various GNV packages. It
is also available various other places, such as
http://www.antinode.info/dec/sw/diffutils.html
...
The GNU diff I've been using for 24 years does not have those
limitations, and also conveniently does command-line redirection:
...
huhu$
https://www.digiater.com/openvms/freeware/v50/gnudiffutils/"This is a port of GNU diffutils 2.7.2 for OpenVMS."
GDIFF == "MC GNV$GNU:[USR.BIN]DIFF"
On Wed, 22 Jan 2025 12:58:01 +0100, hb0815 wrote:
GDIFF == "MC GNV$GNU:[USR.BIN]DIFF"
Is there any reason to choose this over
GDIFF == "$GNV$GNU:[USR.BIN]DIFF"
On 1/22/2025 17:30, Lawrence D'Oliveiro wrote:
On Wed, 22 Jan 2025 12:58:01 +0100, hb0815 wrote:
GDIFF == "MC GNV$GNU:[USR.BIN]DIFF"
Is there any reason to choose this over
GDIFF == "$GNV$GNU:[USR.BIN]DIFF"
No; both do the same thing and both forms of the syntax will never go away, even if the "MCR" form is technically unsupported.
I'm not saying it's unsupported, but several aspects of VMS are probably unsupported
(like EDT), but will never go away.
On 2025-01-22, Robert A. Brooks <FIRST.LAST@vmssoftware.com> wrote:
On 1/22/2025 17:30, Lawrence D'Oliveiro wrote:
On Wed, 22 Jan 2025 12:58:01 +0100, hb0815 wrote:
GDIFF == "MC GNV$GNU:[USR.BIN]DIFF"
Is there any reason to choose this over
GDIFF == "$GNV$GNU:[USR.BIN]DIFF"
No; both do the same thing and both forms of the syntax will never go away, >> even if the "MCR" form is technically unsupported.
I'm not saying it's unsupported, but several aspects of VMS are probably unsupported
(like EDT), but will never go away.
$ set response/mode=good_natured
TECO went away...
Simon.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 432 |
Nodes: | 16 (2 / 14) |
Uptime: | 30:03:38 |
Calls: | 9,081 |
Calls today: | 4 |
Files: | 13,409 |
Messages: | 6,022,132 |