tm1984
Member
Posts: 15
Likes: 10
|
Post by tm1984 on May 12, 2023 1:07:49 GMT
Hello,
I am working through the e-book by Roger Carter. In the e-book, I am at "6.2 Connecting a Projector or Monitor". When I press Win+F2 to run the command, I get the following message:
Peace,
Tom
|
|
enigma9o7
Crew Member
Posts: 1,116 
Likes: 1,151
Member is Online
|
Post by enigma9o7 on May 12, 2023 4:17:05 GMT
I've not read that book, so can only guess what you're trying to do, something to do with connecting a projector or monitor? Maybe set your TV to clone desktop? Does it work for you manually? What is the actual problem?
In any case, when you get that error from Moksha, regardless of what causes it, you can run the same thing from a terminal to see what the error message might be.
Did you make that script yourself? If so I imagine it probably has some syntax error, if you can paste the script here perhaps we can help if the error message doesn't explain it. Or maybe you forgot to mark it executable? If that book describes making it, probably mentioned that, but fy it's:
chmod +x ~/.screenlayout/HisenseTVclone.sh
I would also avoid using ~/ in scripts and other places besides when manually typing in terminal, as there are some situations where shell/environment/user is different and that wont work right. Just use /home/username/ to be safe always.
|
|
tm1984
Member
Posts: 15
Likes: 10
|
Post by tm1984 on May 14, 2023 5:27:11 GMT
Hello enigma9o7,
What I have done is opened Key Bindings Settings, clicked Add to create the Win + F2 key binding, and in the Action box have selected Command, and in the Actions Params box typed "sh ~./screenlayout/HisenseTVclone.sh". HisenseTVclone.sh is a file located at this address in the directory: "/home/tom/.screenlayout".
|
|
|
|
Post by xpistian on May 14, 2023 6:52:38 GMT
Is this a typo?
sh ~./screenlayout/HisenseTVclone.sh
or is it like that in your command?
Because I'm pretty sure it should be
~/.screen... instead of ~./screen..
|
|
tm1984
Member
Posts: 15
Likes: 10
|
Post by tm1984 on May 14, 2023 23:41:14 GMT
Hello xpistian,
Not a typo. When I changed the position of the period, from before to after the forward slash, in the command, it fixed it. Thank you, enigma9o7 and xpistian.
|
|
