Author Topic: filetype not in filename  (Read 4951 times)

hs2

  • Senior Community Member
  • Posts: 2737
  • Hero Points: 288
Re: filetype not in filename
« Reply #15 on: December 20, 2014, 11:37:03 pm »
docname is nice :) New in v19 ?
HS2

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4691
  • Hero Points: 379
Re: filetype not in filename
« Reply #16 on: December 21, 2014, 01:37:23 pm »
No. It's very old. Originally it was for OEM customers that were pulling file data out of data bases and not opening files.

Paul Gilmartin

  • Junior Community Member
  • Posts: 8
  • Hero Points: 0
Compare Buffers (was: filetype not in filename)
« Reply #17 on: May 26, 2015, 07:54:13 pm »
I've been silent since December because:
o I got very satisfactory solutions, to use docname and
  -#selectmode.
o We were on V.16, probably stale.  Now on V.19, so:

I open two buffers where docname has only a very tenuous
relation to actual path.  Then I attempt tools->File Difference.
On each buffer, from the rightmost small icon, "Choose a
Buffer", I select one of my buffers and click "OK".  Then I
click "OK" at the lower left of the dialog window.  Fails with:

    Could not open file
    '(docname is displayed)
    (File)'

    New file

I could hope that when I select two buffers to compare,
VSlick would compare the contents of the buffers, and not
treat the docnames as paths.

Is there a way to make this work?

Thanks,
gil







Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2290
  • Hero Points: 128
Re: filetype not in filename
« Reply #18 on: May 27, 2015, 01:48:09 pm »
This will be fixed for the next hotfix.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4691
  • Hero Points: 379
Re: filetype not in filename
« Reply #19 on: May 27, 2015, 02:43:41 pm »
The "Path 2" text box seems to handle doc names correctly but not the "Path 1" text box. This won't help you if both files specify doc names.

Paul Gilmartin

  • Junior Community Member
  • Posts: 8
  • Hero Points: 0
Re: filetype not in filename
« Reply #20 on: May 27, 2015, 03:16:17 pm »
Thanks for your swift reply.

How quickly do hotfixes become available?  (Of course, "it depends" ...)
Do I get notified?  Will the prior cumulative hotfix (Feb. 12) be prerequisite?

This is not mission critical for us.  Our users are accustomed to extracting
to regular files for diffing; I was just trying to shortcut the procedure
for them.

Thanks again,
gil

Paul Gilmartin

  • Junior Community Member
  • Posts: 8
  • Hero Points: 0
Re: filetype not in filename
« Reply #21 on: November 24, 2015, 01:20:36 am »
Wondering ... Is the hotfix for this available yet?

Thanks,
gil

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2290
  • Hero Points: 128
Re: filetype not in filename
« Reply #22 on: November 24, 2015, 01:38:47 pm »
This is fixed on our 19.0.1 branch and should be in the latest hotfix.  It's in v20 as well (if you have maintenance).