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.

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.

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.

I could still not reproduce this in Puppy 5.1.1. In case this is related to the &-bug, please tray 0.9-2

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

Code:

cd /mnt/sda5 && arecord -d 7200 -f cd -D hw out2.wav

This worked well in previous versions of pschedule, but then I
got ambitious and tried to see if I could edit the line in pschedule.
So here is what I did.

1) click on the task (or job) on the list. That selects it.
2) Click on edit button ---> That produces the edit window.
3) Copy some of command line 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 concluded that the ampersand character is causing pschedule
to become confused.

What I suggest is that when the edit button is clicked , a check for
the double ampersand is made and when the OK button is clicked,
reconstruct the two commands back together so that there is
some sense to the line of code again.

If that's too hard to do then you'd better go back to previous version.

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.
____________________________________________________

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 ';'

would go into the running processes, leaving your command prompt available for further commands.

Some other useful commands:

When a process is running from your command prompt: ^z = (control-z) suspend current process
To "background" that process: bg
To bring that backgrounded process back to the command prompt ("foreground"): fg

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum