You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*`find_contact John` returns `john` and `John Doe`.
190
190
*`find_contact alex david` returns `Alex Yeoh`, `David Li`.
191
+
*`find_contact doe` after `find_contact john` will return `John Doe` and not `john` who was originally in the result.
191
192
<br><br>
192
193
193
194

194
195
195
-
*`find_contacts doe` after `find_contacts john` will return `John Doe` and not `john` who was originally in the result.
196
-
197
196
### Adding a tag : `add_tag`
198
197
199
198
Adds a tag with the specified name to JobFestGo.
200
199
201
200
Format: `add_tag t/TAG_NAME`
202
201
203
202
* The tag name **must not already exist** in JobFestGo.
204
-
* The tag name` must be alphanumeric, i.e, should consist only of alphabets and numbers, and no other characters.
203
+
* The tag name must be alphanumeric, i.e, should consist only of alphabets and numbers, and no other characters.
205
204
206
205
Examples:
207
206
*`add_tag t/vendor`
@@ -220,7 +219,7 @@ Deletes the specified tag name from JobFestGo.
220
219
221
220
Format: `delete_tag t/TAG_NAME`
222
221
223
-
* The tag name **must be an existing tag** vendor, personal, customer, …
222
+
* The tag name **must be an existing tag**. e.g. vendor, personal, customer, …
224
223
225
224
Examples:
226
225
*`delete_tag` followed by `t/vendor` deletes the tag: `vendor` in JobFestGo.
@@ -231,17 +230,17 @@ Displays contacts tagged by any of the specified tags.
231
230
232
231
Format: `filter_by_tag TAG_NAME [MORE_TAG_NAMES]`
233
232
234
-
* Tag names are case-insensitive. e.g `Vendor` will match `vendor`.
233
+
* Tag names are case-insensitive. e.g.`Vendor` will match `vendor`.
235
234
* Only full words will be matched e.g. `ven` will not match `vendor`.
236
-
* Contacts tagged by at least one of the given tags will be returned (i.e. `OR` search).
235
+
* Contacts tagged by at least one of the given tags will be returned (i.e. `OR` search).
237
236
e.g. `vendor customer` will return all contacts tagged by `vendor` and
238
237
all contacts tagged by `customer`.
239
-
* The contacts found will be based on the list that is currently displayed e.g If the current event that is selected is not linked to `Hans` who is tagged by `vendor`, `filter_by_tags vendor` will not display `Hans` in the result.
238
+
* The contacts found will be based on the list that is currently displayed e.g. If the current event that is selected is not linked to `Hans` who is tagged by `vendor`, `filter_by_tags vendor` will not display `Hans` in the result.
240
239
241
240
Examples:
242
241
*`filter_by_tag vendor` returns all contacts tagged by the tag: vendor in JobFestGo.
243
-
*`filter_by_tag vendor customer` returns all contacts tagged by the tag: vendor and
244
-
all contacts tagged by the tag: customer in JobFestGo. The image below illustrates the result of this command.<br><br>
242
+
*`filter_by_tag vendor customer` returns all contacts tagged by the tag: `vendor` and
243
+
all contacts tagged by the tag: `customer` in JobFestGo. The image below illustrates the result of this command.<br><br>
245
244
246
245

247
246
@@ -276,7 +275,7 @@ Format: `delete_event INDEX`
276
275
277
276
* Deletes the event specified at the `INDEX` from the list of events of JobFestGo.
278
277
* The index refers to the index number shown in the displayed event list.
279
-
* The index`**must be a positive integer** 1, 2, 3, …
278
+
* The index **must be a positive integer** 1, 2, 3, …
280
279
281
280
Examples:
282
281
*`delete_event` followed by `1` deletes the 1st event in the displayed event list.
* It works exactly the same way as `mark_task` except for the fact that `unmark_task` marks a completed task as not completed.
396
388
* You may `unmark_task` a task when you realize that you have not completed the task but have wrongly marked it as completed.
389
+
* Errors will be raised if the specified task has already been marked as completed.
397
390
398
391
Examples:
399
392
*`unmark_task td/Book Venue ev/NUS Career Fair 2023` marks the task `Book Venue` from the task list of the event `NUS Career Fair 2023` as not completed.
400
393
394
+
### Viewing help : `help`
395
+
396
+
Shows a message explaining how to access the help page.
397
+
398
+

399
+
400
+
Format: `help`
401
+
401
402
### Clearing all entries : `clear`
402
403
403
404
Clears all entries from JobFestGo.
@@ -424,7 +425,7 @@ JobFestGo data are saved in the hard disk automatically after any command that c
424
425
425
426
JobFestGo data are saved automatically as a JSON file `[JAR file location]/data/jobfestgo.json`. Advanced users are welcome to update data directly by editing that data file.
426
427
427
-
<boxtype="warning"seamless></box>
428
+
<boxtype="warning"seamless>
428
429
429
430
**Caution:**
430
431
If your changes to the data file makes its format invalid, JobFestGo will discard all data and start with an empty data file at the next run. Hence, it is recommended to take a backup of the file before editing it.
@@ -450,7 +451,7 @@ _Details coming soon ..._
450
451
<br>
451
452
1. Open the command prompt
452
453
1. Navigate to the directory where the JAR file is located using cd [JAR file location]
453
-
1. Type java -jar jobfestgo.jar and press enter
454
+
1. Type `java -jar jobfestgo.jar` and press enter
454
455
1. JobFestGo should launch
455
456
456
457
**Q**: How can I check my Java version?<br>
@@ -469,25 +470,25 @@ can download it [here](https://www.oracle.com/java/technologies/downloads/#java1
0 commit comments