Update FAQ: JOJ3 usage
							parent
							
								
									668aa93458
								
							
						
					
					
						commit
						0300f985e5
					
				| 
						 | 
					@ -1,15 +0,0 @@
 | 
				
			||||||
# FAQ JOJ3
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
**Q: my program exits with a "weird" error status and a number. What does it mean?**
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
A: A working program should return with status (or code) 0. If something unexpected is happening JOJ or the OS might be sending a *signal* to your program. To understand what went wrong, run the following command `kill -L`. It lists all the signal names in a table. Check the name of the signal corresponding to the number you see in your Gitea issue and run a quick online search. 
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
**Q: I found a bug, what should I do?**
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
A: First make sure this is really a bug, then open an issue in course-support to report it. We will come back to you for more details if necessary.
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
**Q: JOJ3 looks very exciting, how can I contribute?**
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
A: Refer to the contributing section of the [Introduction to JOJ3](Introduction-to-JOJ3#contributing).
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
| 
						 | 
					@ -3,11 +3,11 @@
 | 
				
			||||||
 | 
					
 | 
				
			||||||
**Q: my program exits with a "weird" error status and a number. What does it mean?**
 | 
					**Q: my program exits with a "weird" error status and a number. What does it mean?**
 | 
				
			||||||
 | 
					
 | 
				
			||||||
A: A working program should return with status (or code) 0. If something unexpected is happening JOJ or teh OS might be sending a *signal* to your program. To understand what went wrong, run the following comment `kill -L`. It lists all the signal names in a table. Check the name of the signal corresponding to the number you see in your Gitea issue and run a quick online search. 
 | 
					A: A working program should return with status (or code) 0. If something unexpected is happening JOJ or the OS might be sending a *signal* to your program. To understand what went wrong, run the following command `kill -L`. It lists all the signal names in a table. Check the name of the signal corresponding to the number you see in your Gitea issue and run a quick online search. 
 | 
				
			||||||
 | 
					
 | 
				
			||||||
**Q: I found a bug, what should I do?**
 | 
					**Q: I found a bug, what should I do?**
 | 
				
			||||||
 | 
					
 | 
				
			||||||
A: First make sure this is really a big, then open an issue in course-support to report it. We will come back to you for more details if necessary.
 | 
					A: First make sure this is really a bug, then open an issue in course-support to report it. We will come back to you for more details if necessary.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
**Q: JOJ3 looks very exciting, how can I contribute?**
 | 
					**Q: JOJ3 looks very exciting, how can I contribute?**
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
		Reference in New Issue
	
	Block a user