Link.Refresh # gives a mysterious syntax error if there is nothing to synchronize

[dyavc]

)clear ]link.create # d:\tmp\junklink\ ]link.Refresh #

• Command Execution Failed: SYNTAX ERROR

I then )ed and fix a function and then this works. )ed blah ]link.Refresh #

Linked: # ←→ d:\tmp\junklink

  ]uversion Link.refresh

framework: 2.4
command: ]LINK.Refresh
source: C:\Program Files\Dyalog\Dyalog APL-64 17.1 Unicode\SALT\spice\Link.dyalog version: 2.09
revision:
commit: 2019 06 19 Adam: Avoid special-cased vars in caller

[abrudz]

I cannot reproduce this with user command version 2.12 and c293d59d358cd381b7befb15720d122cb400cd14 — @stampes can you?

[stampes]

      ]uversion Link.refresh
framework:  2.3                                                                   
command:    ]LINK.Refresh                                                         
source:     \\dk01sn017\IMSDEV\Dev\Common\Dyalog\Production\SALT\spice\Link.dyalog
version:    2.09                                                                  
revision:                                                                         
commit:     2019 06 19 Adam: Avoid special-cased vars in caller                   

             )clear
clear ws

      ]link.create # c:\tmp\junklink
Source directory not found: c:\tmp\junklink
      ]link.create # c:\tmp\junklink
Linked: # ←→ c:\tmp\junklink

      ]link.Refresh #
* Command Execution Failed: SYNTAX ERROR

      )ed ee
      ]link.Refresh #
Linked: # ←→ c:\tmp\junklink

Like this?

[abrudz]

No, please try upgrading Link to c293d59 and see it that helps.

[stampes]

R:\Dev\Common\Dyalog\LSVCLONE>git status
HEAD detached at c293d59

SORRY - it does help:

  )clear

clear ws ]uversion Link.refresh framework: 2.4
command: ]LINK.Refresh
source: \dk01sn017\IMSDEV\Dev\Common\Dyalog\LSVCLONE\SALT\spice\Link.dyalog version: 2.09
revision:
commit: 2019 06 19 Adam: Avoid special-cased vars in caller

  ]link.create # c:\tmp\junklink

Linked: # ←→ c:\tmp\junklink

[abrudz]

So can I close this issue?

[stampes]

So we take the release defined as c293d59d358cd381b7befb15720d122cb400cd14 and use?

[abrudz]

Yes, or in other words, use the 17.1 branch.

[nicolas-dyalog]

closed then.