This page allows to edit the contents of PG problem files (templates) as well as set headers and other files.
Warning: New windows or refreshed windows may not always be brought to the front. This depends on your browser.
- | Manpages | macro list | pod docs | report problem bugs |
- The first three links are to pages that give some information about writing problems: "Manpages" is an (incomplete) list of the most commonly used macros with a description of their parameters and how to use them; a complete list of macros is provided by the "macro list"; and details for many macros can be obtained using the "pod docs" link which links to documentation embedded in the macro files themselves. If you find an error in a library problem please use the "Report problem bugs" link to notify us so that we can fix it. You will need to register with an email address the first time you use bugzilla, but after that you will not.
- The large text window
- This is where you edit the text of the problem template. Nothing happens until you pick an action (below) and click the "Take action!" button.
Action items:(If an action cannot be executed it will not appear as an action item.)
View ... Will bring up a window to show the results of your editing. It does not change the permanent file on the disk. Add to set ... Add this problem as the last problem in an existing set, either as a problem or as the set header (the text that appears on the home page of a homework set). You can rearrange the order of the problems later using the "Hmwk Sets Editor" Save to... Saves the changes to the file indicated. Make local editable copy ... Will make a local copy of changes you have made to an uneditable library problem so that you can edit it. It also changes the file path for the current problem to the new local copy. (It is much like "rename" but actually suggests the file name for you so that you can remember where the problem came from. Rename file path to ... Saves the text to a new file and changes the file path for the current problem to this new file Create a copy ... Saves the changes to a new file but does not change the file path for the current problem Revert to ... Reverts to the copy of the file saved on the disk -- all unsaved editing changes will be lost. Take action Executes the action item selected above.