Oh boy, you missed the Search menu options?

Click on the down-arrow next to the Q in the search field to reveal an 'Apply As Filter' option. Enable it.

Additionally, the menu will list all your recent searches (if any) plus a 'Clear' option to remove the recent search entries.

Good ?

PERFECT! I knew you wouldn't let this slip through!

THANKS!

Just wondering if you might be able to expand the SEARCH function to allow for more Mac-like search results, i.e., instead of showing all files and highlighting the search results with a green icon, allow us to only see the files in the search results. Otherwise, if I want to perform an action on all the matching files I still have to manually command-click each file, whereas if I saw only the matching files I could select all with a shift-click.

Maybe if people really like the green highlighting, offer the Mac-like search results as an option under preferences?

thanks!

in terms of modifying the Suffix Mappings, I believe the only thing I did was add the extension for Ruby files (.rb) so that they could be opened with TextMate rather than my default editor, BBEdit. This was how you suggested I get around the lack of an "open in secondary editor" option. At the time I needed to do this because the Ruby plugin in BBEdit was specific to PPC and therefore any Ruby files opened in BBEdit on my Intel iMac had no syntax coloring, etc.

Since then BareBones has shared their beta of a built-in Ruby plugin that is Universal Binary, so the need to open Ruby files in TextMate is no longer required. So, if I had to, I suppose I could delete the SuffixMapping file even though I have clicked on the "Defaults" button. Maybe there is something going on with how the user specific SuffixMapping file is getting read/written.

paulc. did the issues you described happen on Intel Macs or PPC Macs?

ok will do.

the only thing I can think of is if there is a key command I'm pressing that automatically sets all suffix maps to ASCII. This would be different then the transfer encoding setting which always remains on "Automatic", instead it is some magical gremlin or key command that resets all suffix maps to ASCII.

hey there - me again

there's definitely an issue whereby the transfer encodings seem to magically all get set to ASCII.  Over the past few days there have been at least 3 times I've had to go into the Suffix Mapping panel and click on the Defaults button in order for files to get uploaded/downloaded correctly. For example, I'll download a ZIP archive and when I try to unzip it reports an error. This is because YummyFTP downloaded it as ASCII. Same thing happens if I try to upload a TAR or GZIP archive onto my server and then try to uncompress them on the server - it reports an error because YummyFTP uploaded them as ASCII.

I'm running 1.5.1 on an Intel iMac (10.4.7).

thanks!

no worries mate

setting everything back to default did the trick. since doing so i haven't had any issues so it's quite possible I may have inadvertently pressed a key command or something to switch everything to ASCII.

thanks again.

DUH! 

i guess what I meant to ask is "is there a way to reset suffix maps to default OTHER THAN clicking on the big "DEFAULTS" button? 

heya JD

indeed the suffix mapping is set to ASCII for .jpg.  in fact, it seems EVERYTHING is set to ASCII 

any idea how that happened and is there a quick fix?

the only thing I did with suffix mapping was add .rb so that Ruby files could be opened by TextMate instead of BBEdit.

yet somehow all suffixes are now mapped to ASCII.

is there a way to reset suffix maps to "default"?

had a strange occurrence a little while ago when I was editing a file remotely with BBEdit and YummyFTP. When I tried to save my changes YummyFTP reported an error I've never seen before and I'm kicking myself for not taking a screenshot or writing down the  message. It was something like "YummyFTP could not fill that request due to an error. Please restart YummyFTP and try again" - but I am paraphrasing.

I did so, and now when I try to upload an image (JPEG) with the transfer encoding set to Auto it seems to mangle the image when uploaded - it's all distorted and pixellated.

I tried uploading the image several times under different names and refreshing my browser, etc. to no avail. I also restarted YummyFTP several times. Finally I had to manually set the transfer encoding to Binary for the image to get uploaded correctly.

Any idea what's up?

sweet! 

lehmkuhl nailed it on the head.   I was just about to follow up my previous suggestion with another idea borrowed from Dreamweaver. Dreamweaver allows you to preview in browser by hitting F12 and previewing in an alternate browser by hitting shift-F12. It would be great if YummyFTP could mirror this functionality but apply it to editors, i.e., F12 opens the file in the default editor and shift-F12 opens the file in the alternate editor.

sounds great!  I had envisioned that it would work similarly to the Favorites and History folder icons in the toolbar. Maybe by default the default editor is selected so as not to annoy users who only use one editor?

I was just trying to figure out a way of editing files with another editor besides the default, and while it's not as straightforward as I'd like, there does seem to be a built-in function "Edit With..." that is supposed to allow you to select a predefined editor in addition to the default.

However, whenever I select the submenu "Choose an Additional Editor" I am able to select another editor, but after selecting it the file opens up in YummyFTP's built-in "QuickEdit" instead. Then when I try to edit the document from within "Edit With..." and select the newly defined editor from the menu it still opens the file up in QuickEdit.

Any idea what's wrong?

As a follow up, is there any way to assign keyboard shortcuts to the alternate editors? In other words, I'm never going to use QuickEdit, so it would be great if I could assign its keyboard shortcut (cmd-opt-e) to an alternate external editor  such as TextMate.

thanks!

brilliant!!!

I was just about to suggest the very same feature as I am currently on the fence between BBEdit and TextMate. I have been using BBEdit for ages but there are a few things I really like about TextMate. However certain functions are much better in BBEdit (find/replace, compare 2 front documents) so that there are certain times that I need to open up a particular file in BBEdit.

I'm really glad to see there is an option to do this by suffix mapping, but what I'd really like to be able to do is define several different editors and be able to select which editor when clicking on the Edit icon in the toolbar. Maybe the Edit icon is a folder which when clicked reveals a menu of all defined editors?

My current workflow is TextMate for most coding, StyleMaster for CSS, and BBEdit for find/replace/diff.  So while I can map .php to TextMate there are occasions when I'll need to open up a PHP file in BBEdit for find/replace/diff.

Any way to accommodate this?

FWIW, the bug seems to appear only when the "Numeric Permissions, Owner/Group" is checked (in addition to "Icons reflect permissions" being checked).

In other words, if I uncheck the "Numeric Permissions, Owner/Group" preference, the icons are correct. But if I check "Numeric Permissions, Owner/Group", most if not all the icons display as "locked".

hope that helps...