Author Topic: Subversion 1.14.0  (Read 8605 times)

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2092
  • Karma: +159/-0
    • View Profile
Re: Subversion 1.14.0
« Reply #15 on: July 29, 2020, 09:39:00 am »
Hi Andreas,

Hi Paul, it looks like you've packed the same svn.exe as before. (I've renamed them for this:)

Code: [Select]
epm: I:\Download\connect > svn-2020-07-24.exe --version
svn, version 1.14.0 (r1876290)
   compiled Jul 24 2020, 19:07:05 on i386-pc-os2-emx

epm: I:\Download\connect > svn-2020-07-28.exe --version
svn, version 1.14.0 (r1876290)
   compiled Jul 24 2020, 19:07:05 on i386-pc-os2-emx

Needless to say: It behaves the same as the old version.

The 'compiled' flag is set by configure - it's not a true compile date/time....


Andreas Schnellbacher

  • Hero Member
  • *****
  • Posts: 827
  • Karma: +14/-0
    • View Profile
Re: Subversion 1.14.0
« Reply #16 on: July 29, 2020, 01:45:51 pm »
The 'compiled' flag is set by configure - it's not a true compile date/time....
OK. I've tested it with the correct file before: Both entries editor-cmd = epm /m and editor-cmd = cmd /c epm /m lead to the same error message, as I've posted above. Or has the syntax changed now, compared to 1.7.21?

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2092
  • Karma: +159/-0
    • View Profile
Re: Subversion 1.14.0
« Reply #17 on: July 30, 2020, 03:30:54 am »
The 'compiled' flag is set by configure - it's not a true compile date/time....
OK. I've tested it with the correct file before: Both entries editor-cmd = epm /m and editor-cmd = cmd /c epm /m lead to the same error message, as I've posted above. Or has the syntax changed now, compared to 1.7.21?

Steven's suggestion is to use '4os2 /c epm /m' as the editor command

I'll try and test this evening - but Lewis/Steven have suggested in email that things are working for them.

Cheers,

Paul.

Andreas Schnellbacher

  • Hero Member
  • *****
  • Posts: 827
  • Karma: +14/-0
    • View Profile
Re: Subversion 1.14.0
« Reply #18 on: July 30, 2020, 11:31:35 am »
Steven's suggestion is to use '4os2 /c epm /m' as the editor command

I'll try and test this evening - but Lewis/Steven have suggested in email that things are working for them.
I've tried now all combinations: From a VIO shell, "cmd /c" must be prepended to call a PM editor. (It doesn't matter, if 4os2 or cmd is used.) From a PM shell, there exists no variant that works:

Code: [Select]
Test applications:
   VIO shell: cmd.exe, 4os2.exe
   PM shell : epm.exe 'shell', meshell.exe, lcmd.exe (Larsen Commander)

Test command:
   svn ci * (with an altered file in that dir)

editor-cmd      svn.exe 1.14.0 2020-07-28   svn.exe 1.7.21
                VIO shell    PM shell       VIO shell    PM shell   
             
tedit           OK           -              OK           OK
cmd /c tedit    OK           -              OK           OK
epm /m          -            -              OK           OK
cmd /c epm /m   OK           -              OK           OK