Can't edit files with spaces in SE 17 (64-bit) for Linux

[AriP]

Ah, the pains of dealing with a trial user! Right-clicking a file in the Ubuntu file manager (Nautilus) and picking 'Edit with SE' works fine if there are no spaces anywhere in the fully qualified file name. If there are, Slick attempts to edit a non-existent file! For example, if I try to edit "/home/me/financial reports/qtr1.txt" what pops up in Slick is an empty file named "/home/me/financial". Please, someone, tell me there's a way around this or I'll have to let the trial expire. Thanks.

[Dan]

Filenames with spaces need to be double quoted (because the command line accepts multiple files).  Is there a way to adjust the command that Nautilus uses so the filename is always double quoted?

[AriP]

To the best of  my knowledge that can't be done without modifying Nautilus. It's easy enough to use gedit to do the job, but gedit is so pathetic I was hoping to use Slick. Looking at the problem in reverse, is there a way via configuration files to modify SE? This is really important to me. I know the rule in *nix is, "You'll be sorry if you use spaces in path names even though it's allowed," but my predecessor was a non-conformist.

[Dan]

There isn't really a way to configure this in SlickEdit.

What if you replaced vs with a script that gathered all the command line arguments, quoted them, and then ran the original vs?  This introduces another problem.  There are invocation options that can be space delimited, so you would have to skip items that start with - or +.

[patrick]

Nautilus does allow you to define scripts that show up in the right click menus for files.  But it doesn't look like you can associate with the with the default double-click action for that file type.  But if you don't mind right clicking all of the time...

Create a file called "slickedit_open" under ~/.local/share/nautilus/scripts/ for Gnome3, or ~/.gnome2/nautilus-scripts for Gnome2.  Here's the text for the script:

#!/bin/bash

for f in $NAUTILUS_SCRIPT_SELECTED_URIS
do
   f=`echo $f | sed 's/%20/ /g' | sed 's/file:\/\///g'`
   PATH_TO_YOUR_VS_INSTALL/bin/vs \"$f\"
done


chmod +x the file, and then when you select a file or files in nautilus and right click, there should be a Scripts -> slickedit_open option now that will launch the files in slickedit.

This script doesn't even try to deal with the space delimited options that Dan mentioned.

[AriP]

Dan and Patrick: Thanks very much for the quick response. I'll give your suggestions a try after lunch.

[patrick]

Out of curiosity, what version of Ubuntu are you on?  It looks like on newer versions of nautilus, as long as we supply a proper .desktop file, we can launch v17 just fine for files that are in directories with spaces. Without knowing what version you're on, can't tell how relevant that is.  Thanks.