When looking up PHP/Drupal functions, things seem to work fine if I have the function name selected before firing the Dash search command, but if I just have my cursor inside of the function string (nothing selected), too much cruft is sent to Dash and the search fails. For example, in a line like
$destination = drupal_get_destination();
If I put my cursor in the function name and then search, the search string sent to Dash is "drupal_get_destination();" instead of the intended "drupal_get_destination". For a line like
form_set_error('', t('Please select one or more comments to perform the update on.'));
Thanks for letting me know about this. It's kind of a Coda bug as Coda shouldn't be sending that when the plugin asks it for the currently selected word, but I think I can fix things on the plugin's end.
When looking up PHP/Drupal functions, things seem to work fine if I have the function name selected before firing the Dash search command, but if I just have my cursor inside of the function string (nothing selected), too much cruft is sent to Dash and the search fails. For example, in a line like
If I put my cursor in the function name and then search, the search string sent to Dash is "
drupal_get_destination();
" instead of the intended "drupal_get_destination
". For a line like"
form_set_error('',
" is sent to Dash.