Author Topic: SlickEdit on MacOS  (Read 12462 times)

GaryFerland

  • Community Member
  • Posts: 14
  • Hero Points: 0
Re: SlickEdit on MacOS
« Reply #15 on: January 17, 2018, 02:33:58 PM »
coming back to this. 

The 22.0.1 update fixes the directory issues with vsdiff?

Has the C++ debugger been tested on macOS?  The gdb provided with the software did not seem compatible with the gcc obtained via homebrew.  The leaves the LLVM provided by Apple with the command line tools.  The IDE will work with the lldb debugger provided by Apple?

My trial license ran out in December.  Can I get another trial license for this version?

thanks!
Gary

SlickEdit Support

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 384
  • Hero Points: 29
Re: SlickEdit on MacOS
« Reply #16 on: January 17, 2018, 03:34:13 PM »
Trial License extension emailed to you Gary.

Best,
SlickEdit Support

gary_ferland

  • Junior Community Member
  • Posts: 4
  • Hero Points: 0
Re: SlickEdit on MacOS
« Reply #17 on: January 17, 2018, 08:38:50 PM »
the new version did seem to install and slickedit itself launches.  But vsdiff from the command prompt has regressed, I get this error

Pro15 data:vsdiff Badnell_DR_17.txt badnell_dr.dat
Pro15 data:2018-01-17 15:33:27.697 vs[93595:23155721] modalSession has been exited prematurely - check for a reentrant call to endModalSession:

Then nothing else.  No window launches.

I had set the path to the app in .bashrc, so

 Pro15 data:which vsdiff
/Applications/SlickEditPro2017.app/Contents/MacOS/vsdiff

The OS is a fully patched current macOS running on a MacBook Pro mid 2015.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6910
  • Hero Points: 531
Re: SlickEdit on MacOS
« Reply #18 on: January 17, 2018, 10:35:07 PM »
This isn't hot fixable. 22.0.2 will definitely fix this and will be available in about 2-3 weeks.

In the mean time, you'll need to run the diff from inside SlickEdit. Sorry for the inconvenience.

GaryFerland

  • Community Member
  • Posts: 14
  • Hero Points: 0
Re: SlickEdit on MacOS
« Reply #19 on: February 28, 2018, 08:55:24 PM »
Hi there,
Any updates on vsdiff for Mac?  Does it work now?
thanks,
Gary

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6910
  • Hero Points: 531
Re: SlickEdit on MacOS
« Reply #20 on: February 28, 2018, 09:03:11 PM »
Download 22.0.2. It’s available now

GaryFerland

  • Community Member
  • Posts: 14
  • Hero Points: 0
Re: SlickEdit on MacOS
« Reply #21 on: February 28, 2018, 10:49:22 PM »
I saw the post of the hotfix but vsdiff & Macos were not mentioned.  Could I please get a temporary license to give it a try?  The workflow really does need a command line lauch of vsdiff.
thanks,
Gary

SlickEdit Support

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 384
  • Hero Points: 29
Re: SlickEdit on MacOS
« Reply #22 on: February 28, 2018, 11:03:21 PM »
Trial License for SlickEdit 22.0.2 emailed to you.

Best,
SlickEdit Support

GaryFerland

  • Community Member
  • Posts: 14
  • Hero Points: 0
Re: SlickEdit on MacOS
« Reply #23 on: March 01, 2018, 03:03:02 AM »
first success, vsdiff DID launch from the command prompt.  But with these errors:

Pro15 ~:vsdiff
Pro15 ~:2018-02-28 21:59:03.780 vs[12737:2114930] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2018-02-28 22:00:34.950 vs[12737:2114930] modalSession has been exited prematurely - check for a reentrant call to endModalSession:


Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2902
  • Hero Points: 153
Re: SlickEdit on MacOS
« Reply #24 on: March 01, 2018, 11:31:17 AM »
Did the dialog immediately close, or did it work?

I just checked the code and the fix certainly seems to be there.

GaryFerland

  • Community Member
  • Posts: 14
  • Hero Points: 0
Re: SlickEdit on MacOS
« Reply #25 on: March 01, 2018, 06:35:46 PM »
I have a Macbook Pro at home, which produced the above error.   This iMac at work produces much more verbose errors - see below.  In both cases, I launched vsdiff from the command line with no arguments.  Both have the current Macos and apple command line tools.  homebrew gcc is also installed.

lightning ~:vsdiff
lightning ~:objc[8734]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fffaf39eb68) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x11e997cd8). One of the two will be used. Which one is undefined.
2018-03-01 13:29:53.839 vs[8734:42248869] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2018-03-01 13:30:06.280 vs[8734:42248869] modalSession has been exited prematurely - check for a reentrant call to endModalSession:

GaryFerland

  • Community Member
  • Posts: 14
  • Hero Points: 0
Re: SlickEdit on MacOS
« Reply #26 on: March 01, 2018, 06:49:06 PM »
launching vsdiff from the command line, with two different directories as the arguments, the right directory comes up "read only".  This is new to me and was not a problem in the older X11 Mac versions.  The "read only" option is greyed out so I cannot uncheck it.  I have full permissions in both directories.  The good news is that the app does launch.

the on-screen errors at as follows:
lightning LAMDA:vsdiff ~gary/cloudy/trunk/data/lamda/ 17_10_08_datafiles/
lightning LAMDA:2018-03-01 13:40:45.930 vs[8928:42330322] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2018-03-01 13:41:10.127 vs[8928:42330322] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2018-03-01 13:43:44.025 vs[8928:42330322] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2018-03-01 13:44:50.097 vs[8928:42330322] modalSession has been exited prematurely - check for a reentrant call to endModalSession:

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6910
  • Hero Points: 531
Re: SlickEdit on MacOS
« Reply #27 on: March 01, 2018, 08:26:10 PM »
To work around the read-only issue click on the "Line Diff" button. Unfortunately, the "Line Diff" button isn't present for files which aren't color coding (like .txt files). To work around that issue, you need to turn off the "Source Diff" check box which is in the diff options (not accessible when in the diff dialog). We've identified this  handling of non-color coded files as a bug since it should be handling the files as if source diff was turned off.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2902
  • Hero Points: 153
Re: SlickEdit on MacOS
« Reply #28 on: March 02, 2018, 11:47:56 AM »
I put in a fix for this in the next hotfix.

GaryFerland

  • Community Member
  • Posts: 14
  • Hero Points: 0
Re: SlickEdit on MacOS
« Reply #29 on: March 02, 2018, 11:11:38 PM »
thanks - that seemed to do the trick.  In a few minutes of testing, no obvious show stoppers. 

Will these screen-filling errors be fixed, or is this now normal operation?
lightning LAMDA:vsdiff ~gary/cloudy/trunk/data/lamda/ 17_10_08_datafiles/
lightning LAMDA:2018-03-02 18:07:18.324 vs[26578:2155609] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2018-03-02 18:07:48.957 vs[26578:2155609] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2018-03-02 18:09:04.431 vs[26578:2155609] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2018-03-02 18:09:09.626 vs[26578:2155609] modalSession has been exited prematurely - check for a reentrant call to endModalSession: