Update report3.md

labreport3/report3.md

@@ -54,14 +54,16 @@ I added this JUnit Test to my ListTests class:
         assertEquals(stringList2, ListExamples.filter(stringList, sc));
     }
 ```
-This test tests an ArrayList containing "string" and "ey", and since only the first string starts with 's', the expected result is an ArrayList only containing "string."/
+This test tests an ArrayList containing "string" and "ey", and since only the first string starts with 's', the expected result is an ArrayList only containing "string." 
+
 ### Symptom
-Running JUnit with testFilter and testFilter2 (along with a testMerge function that is related to another function)/
+Running JUnit with testFilter and testFilter2 (along with a testMerge function that is related to another function)
 ![Running JUnit](junit_listTests.png)
-The result is that testFilter failed while testFilter2 succeeded./
+The result is that testFilter failed while testFilter2 succeeded.
+
+Additional screenshots:
 
-Additional screenshots:/
-Running the tests through a VSCode extension:/
+Running the tests through a VSCode extension:
 ![testfilter](failure_testfilter.png)
 ![testfilter2](success_testfilter2.png)
 ### Bug, Before-change
@@ -88,41 +90,77 @@ Running the tests through a VSCode extension:/
     return result;
   }
 ```
-The fix was changing `result.add(0, s)` to `result.add(s)`. The bug was that it was prepending the valid strings to a new array, when it should be adding them to the end in order to preserve the order. I changed it so that it adds the valid strings to the end of the new array./
+The fix was changing `result.add(0, s)` to `result.add(s)`. The bug was that it was prepending the valid strings to a new array, when it should be adding them to the end in order to preserve the order. I changed it so that it adds the valid strings to the end of the new array.
 
 ## Part 2:
--less command/
-1. Using -N/
-Source: Calling `man less` in the Terminal. [manual on less](https://man.archlinux.org/man/less.1#D)/
-My two examples were calling `less -N` on a file, and combining `less -N` with `-p pattern`./
+-less command
+
+1. Using -N
+
+Source: Calling `man less` in the Terminal. [](https://man.archlinux.org/man/less.1#D)
+
+My two examples were calling `less -N` on a file, and combining `less -N` with `-p pattern`.
 ![Two commands](less1-3.png)
 a.
 ![less -N](less1-1.png)
 Adding in `-N` after less lists the line numbers of each line. This is useful since we can see how many total lines there are and where we are in the file./
 b.
 ![less -N and -p](less1-2.png)
-Once again, having the line numbers is useful so we can see where we are looking in the file. It is especially helpful when also using `-p`, so that we know what line we are on when looking for a specific word./
+Once again, having the line numbers is useful so we can see where we are looking in the file. It is especially helpful when also using `-p`, so that we know what line we are on when looking for a specific word.
+
+2. Viewing multiple files
+
+Source: [](https://www.thegeekstuff.com/2010/02/unix-less-command-10-tips-for-effective-navigation/)
 
-3. Viewing multiple files/
-Source: [Multiple files Link](https://www.thegeekstuff.com/2010/02/unix-less-command-10-tips-for-effective-navigation/)/
 a. 
-Working directory: `/Users/katelynnguyen/docsearch/technical/biomed` and using less on two files in the current directory. I used `:n` and `:p` to go back and forth between the files./
+
+Working directory: `/Users/katelynnguyen/docsearch/technical/biomed` and using less on two files in the current directory. I used `:n` and `:p` to go back and forth between the files.
 ![Viewing 2 files in current directory](less2-1.png)
 ![Viewing 2 files in current directory](less2-2.png)
-I can also use less to look at multiple files. In this case, I provided two files in biomed, the current directory, as command line arguments. I was able to switch between the two files using `:n` and `:p` which is useful if I want to compare two files side by side./
-b./
-Working directory: `/Users/katelynnguyen/docsearch/technical`. Using less on two files in the 911report subdirectory./
+I can also use less to look at multiple files. In this case, I provided two files in biomed, the current directory, as command line arguments. I was able to switch between the two files using `:n` and `:p` which is useful if I want to compare two files side by side.
+
+b.
+
+Working directory: `/Users/katelynnguyen/docsearch/technical`. Using less on two files in the 911report subdirectory.
 ![Viewing 2 files in a subdirectory](less2-4.png)
 ![Viewing 2 files in a subdirectory](less2-3.png)
-In this case, I provided two files in 911report, the subdirectory in technical, as command line arguments. I was oncee again able to switch between the two files using `:n` and `:p`, and it was useful to know that I can also provide different paths to look at files./
+In this case, I provided two files in 911report, the subdirectory in technical, as command line arguments. I was oncee again able to switch between the two files using `:n` and `:p`, and it was useful to know that I can also provide different paths to look at files.
+
+3. Searching for a pattern/sequence of characters
+
+Source: [](https://ioflood.com/blog/less-linux-command/#Advanced_Usage_of_the_8216less8217_Linux_Command)
 
-5. Searching for a pattern/sequence of characters/
-Source: [Search resource link](https://ioflood.com/blog/less-linux-command/#Advanced_Usage_of_the_8216less8217_Linux_Command)/
 a. Typing in /word/
 ![/place](less3-1.png)
 ![/place](less3-2.png)
-I used less then typed in `/place` to search for the word 'place' in the file. It highlighted all of its occurrences, which is a helpful tool similar to the Command F shortcut to find a word or phrase./
-b. Using -p pattern/
+I used less then typed in `/place` to search for the word 'place' in the file. It highlighted all of its occurrences, which is a helpful tool similar to the Command F shortcut to find a word or phrase.
+
+b. Using -p pattern
 ![-p](less3-3.png)
 ![-p](less3-4.png)
 This time, I used less with `-p place` to search for the word 'place' in the file. It highlighted all of its occurrences and brought me to them, and it is helpful to be able to search for a word in the same line that I called `less`.
+
+4. Jumping to a specific line
+a. Typing in g50 to get to line 50
+In the terminal, I typed in the less command, then typed in `50g`
+```
+(base) katelynnguyen@Katelyns-MacBook-Air technical % less 911report/chapter-1.txt
+50g
+```
+It jumped to this line:
+```
+When the local civil aviation security office of the Federal Aviation Administration (FAA) later i
+```
+This is really useful so that you can go directly to a specific line and view it. It makes it easier to navigate.
+
+b. Using `+50`
+In the terminal, I typed:
+```
+(base) katelynnguyen@Katelyns-MacBook-Air technical % less +50 -N 911report/chapter-1.txt
+```
+It jumped to the same line 50:
+```
+When the local civil aviation security office of the Federal Aviation Administration (FAA) later i
+```
+
+This is another way to navigate line numbers of a file, and is an easy way that can fit in one line.