Puppy Linux Discussion Forum

[don570]

Pschedule.9

I came across this odd bug while using luci 238

I wanted to put some of the job info into the clipboard.

I selected the command , then clicked on Edit button.

It was easy to put the info into the clipboard,

But I found that the next button that you click is important.

If I click 'Cancel' to get rid of edit window everything is alright,

but if I click 'OK' this prevents me from transfering text to the clipboard again.

That's because the edit window has empty fields as shown in
image (click to enlarge)


I assume this is a bug.

_____________________________________________

[zigbert]

don570
I have read your post 4 times, and still not understanding the bug. Please keep in mind, - I am just a silly Norwegian with very limited global understanding. I have never been one of those smart guys, so maybe a couple of images would help.


Sigmund

[vovchik]

Dear zigbert,

Would this be of any use to you: http://www.murga-linux.com/puppy/viewtopic.php?p=470615#470615?

With kind regards,
vovchik

[don570]

I'll explain how to reproduce the bug step by step.

1) click on a task (or job) on the list. That selects it.
2) Click on edit. That produces the edit window.
3) Copy some command info to clipboard.
4) Now click on OK button
5) Click on edit button a second time and command field is now empty.
It shouldn't be empty.

I'll try to reproduce it again and report back this weekend.
I should have tried another puppy variant.

[don570]

There is problem with ampersand.
try command
touch test&&.txt
and go thru steps in previous post.


and try commands of my previous post of month ago

maybe other symbols as well

Edit:

try a better example

[zigbert]

[zigbert]

Don570
will look at your trouble a bit later.......


Sigmund

[zigbert]

Version 0.9-2
See main post

Changelog
- Bugfix: Accept & in command (thanks to don570)
- Bugfix: Wrong Title in error-box.

[zigbert]

[don570]

The only bug I had was with the ampersand.
I'll test the fix and report.

[don570]

I didn't explain the ampersand bug very clearly.
It doesn't refer to a variable name having an
ampersand character.

What I was doing was to connect two commands with a double
ampersand &&

This is a method that I like
to use to complete one command completely then start another command.

The example I used was

[don570]

I quickly drew up a design to show how to handle the double ampersand.

When the edit button is clicked , there would be a search for the double
ampersand in the task and if it was found, this window would appear.
Each command could be edited separately. Then click on the OK button
when the editing is concluded.





Once the edit window closes the two commands can be recombined
into one line of code and the regular window used.
____________________________________________________

[zigbert]

don570
I have made some more testing, I find the latest (0.9-2) to work as expected. Please be aware of
- it adds a \ in front of the &. This prints the text-string (with &) correct, and you can edit the cron-task without corrupting the command.
- Adding a & to the command to run in background seems to me not logical, since cron itself continues after execution.
- To execute several commands in one cron-task, you should use the separator ';'


Sigmund

[RetroTechGuy]

[don570]

I think I learned about the double ampersand when
I read a book about Unix a couple of years ago.
Linux does things different obviously.
When in Rome do as the Romans do.

_________________________________________