Yummy Software

Yummy FTP => Feedback & Suggestions => Topic started by: Domsou on June 29, 2009, 11:55:40 PM



Title: Associate editor base on file extension
Post by: Domsou on June 29, 2009, 11:55:40 PM
The main goal is to associate different editor for different file format !

For example :
  • PHP > Textmate
  • CSS > CSSEdit
  • png > the Gimp
  • and so on

Because in my day to day use I have to select each time which editor to edit a file with.  :'(


Title: Re: Associate editor base on file extension
Post by: JD on June 30, 2009, 02:19:36 AM
This is already implemented in the next version, within the Info window. You can see it in the latest beta version:

http://www.yummysoftware.com/beta/latest/YummyFTP.dmg


Title: Re: Associate editor base on file extension
Post by: Domsou on June 30, 2009, 10:31:43 AM
Fine !

I used the beta version of Yummy but I was searching the configuration on the wrong place : preferences !

Definitely the killer FTP app' !

Thanks !


Title: Re: Associate editor base on file extension
Post by: Domsou on July 01, 2009, 09:23:02 AM
Well,

Yummy FTP seems to loose the association between file and editor.
The feature I originally told about is to associate one file to an editor using extension in addition to file by file.

In preferences panel just say "ok, for .css is CSSedit, for .php, espresso and so on.

For now this is not working. For example I quit Yummy FTP and for a CSS file I was working on this morning the association to CSSEdit I made not exist anymore. Maybe this is a bug !


Title: Re: Associate editor base on file extension
Post by: JD on July 01, 2009, 10:58:53 AM
I'm pretty sure this bug was already fixed in the latest beta. Please check:

http://www.yummysoftware.com/beta/latest/YummyFTP.dmg


Title: Re: Associate editor base on file extension
Post by: JD on July 02, 2009, 04:48:25 PM
Actually, you're right! It only happens if you choose 'Other' then select your own choice. If you choose the Default setting, or one of the predefined options then the setting is saved.

Anyway, now all is fixed in the next build. Thanks for reporting the bug :)