Author Topic: B5: Unusable - Buffer changes to .command  (Read 7517 times)

bengle

  • Senior Community Member
  • Posts: 132
  • Hero Points: 4
Re: B5: Unusable - Buffer changes to .command
« Reply #15 on: May 30, 2013, 03:13:48 pm »
jc44: It might be useful to find out if it would still happen to you if you copy those same files to your C: drive and open them from there. 

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5092
  • Hero Points: 419
Re: B5: Unusable - Buffer changes to .command
« Reply #16 on: May 30, 2013, 03:16:49 pm »
For what its worth I'm using Brief emulation, and nearly all my files are C/C++ on network drives.

Have you mapped the networked files to a drive letter? Or are you using UNC names (i.e. \\machine\share\...)?

jc44

  • Senior Community Member
  • Posts: 218
  • Hero Points: 15
Re: B5: Unusable - Buffer changes to .command
« Reply #17 on: May 30, 2013, 03:20:10 pm »
All paths are to mapped drives (Y: or Z:) on a Samba server

I'll try copying to C: in a bit - right now I need to get some actual coding done :-) (back to using 17.0.3)

Ryan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 986
  • Hero Points: 77
Re: B5: Unusable - Buffer changes to .command
« Reply #18 on: May 30, 2013, 03:26:59 pm »
I'm not 100% sure but I think I might have just seen this.  Do you have Tools > Options > Languages > Application Languages > C/C++ > Context Tagging® > Show info for symbol under mouse checked?  If so, turn it off, and then see if you are still getting this weird behavior.

Thanks,

Ryan

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5092
  • Hero Points: 419
Re: B5: Unusable - Buffer changes to .command
« Reply #19 on: May 30, 2013, 03:29:39 pm »
I just got this problem for sure!! I think it has something to do with show symbol under mouse but I need to investigate further.

I mapped a drive letter and started editing a C++ project.
« Last Edit: May 30, 2013, 03:31:35 pm by Clark »

bengle

  • Senior Community Member
  • Posts: 132
  • Hero Points: 4
Re: B5: Unusable - Buffer changes to .command
« Reply #20 on: May 30, 2013, 03:55:32 pm »
I just unchecked "Tools > Options > Languages > Application Languages > C/C++ > Context Tagging® > Show info for symbol under mouse" and restarted SlickEdit, but the problem persists.  I have uploaded my config files and a couple of source files.

Just let me know whatever you would like me to try or information to collect. 

bengle

  • Senior Community Member
  • Posts: 132
  • Hero Points: 4
Re: B5: Unusable - Buffer changes to .command
« Reply #21 on: May 30, 2013, 04:15:32 pm »
I just reproduced this same problem on a network drive with a mapped drive letter.  So it seems to happen on either a network directory or an alias directory created via the "subst" command.

Here are the results of my testing so far...
- "subst" drive: problem occurs
- mapped network drive letter: problem occurs
- UNC network directory: no problem
- local drive: no problem

It would seem that might have something to do with remapped drive letters (either network or subst).
 

bengle

  • Senior Community Member
  • Posts: 132
  • Hero Points: 4
Re: B5: Unusable - Buffer changes to .command
« Reply #22 on: May 30, 2013, 04:45:44 pm »
See my comments in the separate thread: B4: SE confused, won't allow edits on certain files, brings up .command buffer

I believe these to be the same problem.  I never did see the problem in Beta 4, however.   

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5092
  • Hero Points: 419
Re: B5: Unusable - Buffer changes to .command
« Reply #23 on: May 30, 2013, 06:15:25 pm »
I just reproduced this same problem on a network drive with a mapped drive letter.  So it seems to happen on either a network directory or an alias directory created via the "subst" command.

Here are the results of my testing so far...
- "subst" drive: problem occurs
- mapped network drive letter: problem occurs
- UNC network directory: no problem
- local drive: no problem

It would seem that might have something to do with remapped drive letters (either network or subst).
 

Your results say it all. There is one more test case which also has the problem which is symbolic links. If your path has a symbolic link, you will also have this problem. Almost no one uses symbolic links on Windows but many use it on Unix.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5092
  • Hero Points: 419
Re: B5: Unusable - Buffer changes to .command
« Reply #24 on: May 30, 2013, 08:08:51 pm »
Beta 6 which fixes this problem will be available very soon

bengle

  • Senior Community Member
  • Posts: 132
  • Hero Points: 4
Re: B5: Unusable - Buffer changes to .command
« Reply #25 on: May 30, 2013, 08:16:20 pm »
For the sake of completeness, I did try this with both Windows symbolic links and Windows junctions (hard links).  Both of those do exhibit the problem, but you probably already know that.

Thank you for getting this fixed so quickly, and I will look forward to Beta 6.   ;D

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5092
  • Hero Points: 419
Re: B5: Unusable - Buffer changes to .command
« Reply #26 on: May 30, 2013, 09:42:30 pm »
Beta 6 is available for download. Solaris binaries for beta 6 will be available tomorrow.

bengle

  • Senior Community Member
  • Posts: 132
  • Hero Points: 4
Re: B5: Unusable - Buffer changes to .command
« Reply #27 on: May 30, 2013, 09:54:30 pm »
Just to confirm.  Beta 6 does, indeed, correct my problem, and I thank you very much!   ;D

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5092
  • Hero Points: 419
Re: B5: Unusable - Buffer changes to .command
« Reply #28 on: May 30, 2013, 09:57:39 pm »
Yes, it's fixed! Thanks for your help!

jc44

  • Senior Community Member
  • Posts: 218
  • Hero Points: 15
Re: B5: Unusable - Buffer changes to .command
« Reply #29 on: May 31, 2013, 09:52:01 am »
Yup that seems to fix it.  Now I can get on with reporting other issues :-)

Thanks