Nautilus Scripts Not Working (Fedora 12)

kwanbis · 01-05-2010, 01:15 PM

It is probably me doing something wrong:

Quote:

#!/bin/bash
for arg
do
fileName="$arg"
fileNoExt=$(basename $fileName)
zenity --info --title="LOG" --text="$fileNoExt" --width=200 --height=200
done

Over a file called "Open Archive.TXT", i get "Open" as the output.

Over a file called "Extract To Folder", i get nothing as the output.

:S

David1357 · 01-05-2010, 01:41 PM

Quote:

Originally Posted by kwanbis

Over a file called "Open Archive.TXT", i get "Open" as the output.

The name "Open Archive.TXT" will get split into separate arguments, so the first argument will be "Open". You should also get a dialog for "Archive.TXT".

Try this

Code:

fileName="$@"
fileNoExt=$(basename "$fileName")
zenity --info --title="LOG" --text="$fileNoExt" --width=200 --height=200

Hopefully the window manager is smart enough to make separate calls for each file if you have multiple files selected.

kwanbis · 01-05-2010, 01:46 PM

but shouldn't the fileName="$arg" make it one file?

I get: "Open Archive.TXT", the .EXT is not taken out.

Quote:

#!/bin/bash
fileName="$@"
fileNoExt=$(basename "$fileName")
zenity --info --title="LOG" --text="$fileNoExt" --width=200 --height=200

David1357 · 01-05-2010, 01:51 PM

Quote:

Originally Posted by kwanbis

but shouldn't the fileName="$arg" make it one file?

No. You use the "for arg do" syntax, which splits the command line into arguments using space as the delimiter.

Quote:

Originally Posted by kwanbis

I get: "Open Archive.TXT", the .EXT is not taken out.

AUGH! My bad. Use your original extension stripping code. I occasionally get "basename" confused with the DOS/Windows "splitpath" function. Most of the time, they do the same thing... unless there is an extension you want to remove.

kwanbis · 01-05-2010, 02:17 PM

Files:

Quote:

AAA BBB CCC.TXT
DDD EEE FFF.DOC

Script 1:

Quote:

#!/bin/bash
for arg
do
fileName="$arg"
zenity --info --title="LOG" --text="$fileName" --width=200 --height=200
done

Result 1:

Quote:

AAA BBB CCC.TXT
DDD EEE FFF.DOC

Script 2:

Quote:

#!/bin/bash
for arg
do
fileName="$arg"
fileNoExt=${fileName%.*}
zenity --info --title="LOG" --text="$fileNoExt" --width=200 --height=200
done

Result 2:

Quote:

AAA BBB CCC
DDD EEE FFF

So "AAA BBB CCC" is not treated as 3 params.

David1357 · 01-05-2010, 04:16 PM

Quote:

Originally Posted by kwanbis

So "AAA BBB CCC" is not treated as 3 params.

I ran this from the command line

Code:

#!/bin/bash
for arg
do
        fileName="$arg"
        echo "fileName = $fileName"
done

and got this

Code:

[user@machine:~]:./blah AAA BBB CCC.TXT
fileName = AAA
fileName = BBB
fileName = CCC.TXT

Are you running the script from the command line?

Are you getting the file name by typing "A[Tab]" and getting "AAA\ BBB\ CCC.TXT"?

kwanbis · 01-05-2010, 04:21 PM

No, i'm running it as a nautilus script, by placing them on /home/kwanbis/.gnome2/nautilus-scripts

By the way, i just tested unrar on the command line, and as a script.

On the command line, i get echoes to the screen, but under the script, nothing is echoed to the screen.

It is like nautilus/gnome redirects the output.

Would it be possible somehow to make it print to the screen?

David1357 · 01-05-2010, 04:41 PM

Quote:

Originally Posted by kwanbis

It is like nautilus/gnome redirects the output.

I think that is what I was trying to tell you.

Because a GUI does not (normally) have a terminal, GUIs that run command line utilities have nowhere to send the output. Thus the need for log files for scripts that will be run under the control of a GUI.

The same problem occurs with daemons (such as web servers) that close stdout, stderr, and stdin in the child after they fork. They have no terminal to which to send output, so they log everything to files. Thus the need for several different log files in the configuration for Apache (i.e. error.log, access.log, etc.).

kwanbis · 01-05-2010, 06:01 PM

Right.

So my question then is if there is a way to create a dialog or terminal or something where the application can output to.

Like zenity, but live.

David1357 · 01-06-2010, 08:04 AM

Quote:

Originally Posted by kwanbis

So my question then is if there is a way to create a dialog or terminal or something where the application can output to.

You can start xterm or gnome-terminal and run a command:

Code:

#!/bin/bash
xterm -e tail -f /var/log/messages
# Note the quotes required for the gnome-terminal version
gnome-terminal -e "tail -f /var/log/messages"

The command could easily be another script which would then display all its output in the terminal.

kwanbis · 01-06-2010, 08:25 AM

I found out that zenity itself has a progress dialog that can be used. As in this example.

Quote:

#!/bin/sh
(
echo "10" ; sleep 1
echo "# Doing XYZ" ; sleep 1
echo "20" ; sleep 1
echo "# Doing ABC" ; sleep 1
echo "50" ; sleep 1
echo "This line would be ignored as it does not starts with #" ; sleep 1
echo "75" ; sleep 1
echo "# Finalizing Test" ; sleep 1
echo "100" ; sleep 1
) |
zenity --progress \
--title="Actualizando los registros del sistema" \
--text="Rastreando los registros de los correos..." \
--percentage=0

if [ "$?" = -1 ] ; then
zenity --error \
--text="Actualización cancelada."
fi

Now, the problem is that i need to pass a number, so it moves the percentage, and a # before the text. But this is what unrar outputs.

Quote:

UNRAR 3.91 freeware Copyright (c) 1993-2009 Alexander Roshal

Extracting from filXXXX.part1.rar

Creating abcd OK
Extracting abcd/filXXXX.xxx 0% 1% 2% 3% 4% 5% 6% 7% 8% 9% 10% 11% 12% 13% 14% 15% 16% 17% 18% 19% 20%

Extracting from filXXXX.part2.rar

... filXXXX.xxx 21% 22% 23% 24% 25% 26% 27% 28% 29% 30% 31% 32% 33% 34% 35% 36% 37% 38% 39% 40%

Extracting from filXXXX.part3.rar

... filXXXX.xxx 41% 42% 43% 44% 45% 46% 47% 48% 49% 50% 51% 52% 53% 54% 55% 56% 57% 58% 59% 60%

Extracting from filXXXX.part4.rar

... filXXXX.xxx 61% 62% 63% 64% 65% 66% 67% 68% 69% 70% 71% 72% 73% 74% 75% 76% 77% 78% 79% 80%

Extracting from filXXXX.part5.rar

... filXXXX.xxx 81% 82% 83% 84% 85% 86% 87% 88% 89% 90% 91% 92% 93% 94% 95% 96% 97% 98% 99% OK
All OK

So i need to use Sed to make it work somehow.

David1357 · 01-06-2010, 10:17 AM

Quote:

Originally Posted by kwanbis

So i need to use Sed to make it work somehow.

I put your output from unrar in a file and used this

Code:

sed -e 's/\([0-9]*\)%/\n\1#\n/g' < data | grep '#'

to convert it to a sequence of lines that looked like

Code:

0#
1#
...
8#
9#
10#
...
98#
99#

The "..." indicates lines I removed from the output.

kwanbis · 01-06-2010, 11:43 AM

That works fine, the only problem is that it is not real time. Unrar decompresses all the files, and then the progress works.

So i created a VERY BASIC Lazarus/FreePascal application, that reads all the input, and prints it to both, a memo, and a tpanel.

This is most of the code.

Code:

procedure TForm1.Memo1Enter(Sender: TObject);
var
 fStdIO: TextFile;
 sLinea: string;
begin
  assignfile(fStdIO,''); reset(fStdIO);                                                 // open the stdin "file"
  while not eof(fStdIO) do begin                                                        // while we are getting standard input ...
    application.ProcessMessages;                                                        // process messages (paint the texts)
    readln(fStdIO,sLinea);                                                              // read the a line
    sLinea := StringReplace(sLinea, '', '', [rfReplaceAll, rfIgnoreCase]);             // remove the strange unrar characters
    sLinea := StringReplace(sLinea, '  ', ' ', [rfReplaceAll, rfIgnoreCase]);           // remove double spaces
    Memo1.Append(sLinea);                                                               // update the memo
    Panel1.Caption := sLinea;                                                           // update the panel
  end;
  closefile(fStdIO);                                                                    // close stdin "file"
  Application.Terminate;
end;

So now i have a script to extract my RARs, that goes like this:

Code:

#!/bin/bash
for arg
do
	pathName=`echo $NAUTILUS_SCRIPT_CURRENT_URI | sed -e 's|file:///|/|' -e 's|//|/|' -e 's|%20| |'`
	fileName="$arg"
	fullName=$pathName/$fileName
	fileNoExt=${fileName%.*}
	fullFolder=$pathName/$fileNoExt
	~/xtractor/unrar e "$fullName" "$fullFolder/" | ~/xtractor/capturer
done

I still need to add something to check the returned value, and if it is ok, just close, if not, give an error message.

kwanbis · 01-06-2010, 12:11 PM

Just in case it is useful for anybody else, here is the link to the executable and the code/project for lazarus.

I release it under the GPL.

http://www.mediafire.com/?mownyjyuydg

David1357 · 01-06-2010, 12:46 PM

Quote:

Originally Posted by kwanbis

That works fine, the only problem is that it is not real time. Unrar decompresses all the files, and then the progress works.

I guess I was assuming you would change your script to be something like this

Code:

#!/bin/sh
(
unrar-command | sed -e 's/\([0-9]*\)%/\n\1\n/g'
) |
zenity --progress \
--title="Actualizando los registros del sistema" \
--text="Rastreando los registros de los correos..." \
--percentage=0

if [ "$?" = -1 ] ; then
zenity --error \
--text="Actualización cancelada."
fi

The sed expression should convert the output of the "unrar-command" to data that zenity understands. I created a proof of concept here using the following two scripts.

This first script simulates the output of the unrar command being processed into lines that zenity understands:

Code:

#!/bin/bash
# This simulates the output of the unrar command
exec 3<data
while read -u 3 line
do
        echo $line | sed -e 's/\([0-9]*\)%/\n\1 #\n/g' | grep "#"
        sleep 1 ;
done

This takes the output of the previous script and updates the progress bar of the zenity dialog:

Code:

#!/bin/bash
unrar-command | zenity --progress --percentage=0

My experiments show that you will need two scripts, one to run the command and convert the output, and one to display the zenity dialog. Trying to do the sed and grep in the zenity script causes the dialog to wait until the first script completes before it updates the progress bar, and then it jumps all the way to 100%.