Hello,
i've been trying to use the [shell] object to sen a simple command, but i can't get it working, i have previously used "sudo shutdown -h now", "sudo reboot" on other scripts, the command i'm trying to use is: "sed -i '' 's/cuenta/variable/g' /Users/myname/prueba.txt" to replace a variable on a system file, i put the command directly on the terminal and it works, but in PD it doesn't, Any idea?

Thank you
Excuse my English
Greener

None of the two versions work? The full message on the right is different than that on the left. The message on the left results in sed -i '' 's/pass/contrasena/g' Users/myname/prueba2.txt which the first message is sudo sed -i '' 's/cuenta/cosa/g' /Users/myname/prueba2.txt
Notice that the message you construct with [pack] doesn't include the root directory, it tries to find a file in Users/myname/ instead of /Users/myname/

i have tried it both ways, and a lot of different ways, changing the file location, but it doesn't work yet, i don't get it

I have found that using sudo in shell is problematic. Ive thought of some ways to potentially work around this, but in honesty, haven't tested them yet. If you try any of these ideas, pleas let me know how they go. In theory, they should work.

1 - try the visudo command and set your username to have nopasswd privelages so that sudo commands do not ask for a password.
2 - enter the sudo command through shell like this: echo "<your password>" | sudo -S <your command>
3 - try constructing the command with fakeroot instead of sudo

Hope any of these helps

Hello @th8a thanks for the answer

i tried de 2nd one previously, but it didn't work, and now i tried the 1st and 3rd and even it doesn't work, also i tried with a file on the desktop that doesn't require password or super user privileges, but no
Also i tried sudo -S <<< "mypassword" <my command>

i think it is the shell object

@Greener Is the terminal that shell opens actually opening where you think it is? In the root or somewhere else? If it is somewhere else then the paths will be wrong.....
... that is you might need to give the full path with the drive letter?
..... just a maybe...... sorry, but I am a windows user.
David.

Hi @whale-av

Usually the shell on Mac OS starts on: /Users/yourname/
But in the Shell object it starts on: /
So, as you see, we have to put all the path, i tried different paths a lot of times, and tried with different files on different paths also, i comprobed the path by myself using the command: ls (it shows you all the files and folders contained on the actual directory), so i don't really get it

Greener

Does any command work in the [shell] object that you are using? If you run something simple, like 'ls' or 'pwd' will it output the file list of the directory? If so, then there could likely be a formating issue with the text that you are sending to the object. The way that puredata handles sending certain symbols and characters through messages can sometimes throw a command askew when translating to bash. To make things harder, the front slash that is typically used as an escape symbol to send symbols as literals is not allowed in messages within pd... So if the [shell] object is functional, but your particular command just doesn't seem to want to work properly, then you can try the following:

1 - make use of objects that convert text in messages to and from symbols, like [makesymbol] [cyclone/tosymbol] [cyclone/fromsymbol] [s2l] [l2s] etc.
2 - try sending commands to shell via [text] or [coll].
3- when all else fails, or a script is just too complex or uses many odd characters, open a code editor like kate (or textmate on mac,) and type the code in there. Try running it in a terminal to make sure it works. Save the file, and then in terminal run

sudo chmod +x "/path/to/file/filename" 

enter your password and now that file will be marked by the OS as executable. You can call it from the [shell] object by simply sending it the path to the file, or cd <path>; ./<filename>

If your script requires variables that change in pd, like $1 $2, then you can set that up in your script by defining variables and then sending those values as in separate messages. for example, in your code, you could start by defining a variable like

foo=0;

then in pd

[nbx]
|
[foo=$1(
|
[shell]

After you send the change in value to the variable, call the script again and it will output with the updated values.
In sticky situations in shell, this trick has saved the day for me many times. Hope that helps.

Hello @th8a

Yesterday i took the time to read, understand and try every option, but, nothing happens with [shell], fortunately you gave me the idea with the [textfile] to achieve what i was looking for: Assemble a file system with variables and keyboard characters that PD doesn't allow, such as { }, and then use [shell] to move the file (Finally [shell] object wants to collaborate), if someone wants to see the final patch, just ask for it

Thanks for your answers,
Greener

glad to hear it. happy to help.