Recognizing & Solving Problems

Over this semester I have been learning quite a few new things. First, I have learned how to use new digital tools that will, although it may not seem like it now, help me in complete future research more efficiently. Second, how to put my incomplete work online (as discussed in my previous post). Finally though, I have learned that I don’t need to suffer on my own. My mind was blown by this idea. “What?!?! Dr Graham you are saying that we can share our issues with other people and ask for help?” No word of a lie that was a hard concept to wrap my head around.

Therefore, following these along with these lessons, I am moving forward and using them to help solve problems I am having. For example, I am writing down every single thing I do for each tutorial in Notational Velocity, one of the many new tools that I have been turned on to as I slowly gain more knowledge about its usefulness. Also, I am posting all my notes on this blog, below you can see the notes that I took yesterday (February 9, 2016) when I attempted the Command Line Tutorial for a second time.

When doing this tutorial for a second time I was able to complete it successfully despite the couple times that I thought I had done something wrong, I was later assured that I had not done anything wrong. Check them out and let me know if you have any suggestions.

Digital History – Command Line Tutorial Notes 2

- typed in pwd command to orient myself then hit the ls command to get a listing of the files and directories within my current location which is /users/hollispeirce1. These are:

ApplicationsDownloadsMoviesPublicprojects   Desktop   Dropbox      Music       Sites python    Documents         Library Pictures mallet-2.0.7

- Flags: these are additions to a command that provide the computer with a bit more guidance with what sort of output or manipulation that you want

- Playing around with changing files and directories but for some reason I still don’t understand how to move into files that have two words or more in the title. Tried _ , – , and . .

- Figured out how to do it! to get into files with two or more word titles i just have to use “quotation marks”

- Succeeded in using the -l flag to get more information on the main files and directories

- Adding an h to the -l flag (-lh) commands the computer to display the sizes of the files in a smaller format to make up room

- successfully moved straight to mallet by typing: cd /users/hollispeirce1/mallet-2.0.7

- i also was able to open mallet by typing: open . once i was in mallet and the window opened up

- created a new directory on the desktop called ProgHist-Text by entering the command: mkdir ProgHist-Text

- can now move in and out of it as desired and successfully moved into it using the auto-complete with the tab button remember though auto-complete is case sensitive

- figured out how to read a file on the command line by typing the command: cat name-of-text.txt

- When I hit the up arrow it cycles through the most recent commands and the down arrow goes through the commands in the other direction

- successfully duplicated the file by using the command: cp name-of-text.txt name-of-text2.txt

- and moved it into a smaller one with: cat name-of-text

- to open vim and edit a txt file in terminal enter the command: vim name-of-text.txt

- to man an edit enter the a flag which allows you to edit the text and press escape to go back to reading

- to save anything in vim type : and hit enter then type w and press enter

- to leave vim type : and hit enter then press the q button

- you can also combine these two like all other command BUT WATCH OUT AS YOU CAN QUIT WITHOUT SAVING SO IF YOU DO THIS ENTER wq

- create a back up before moving a file by entering cp file-name.txt file-name-backup.txt

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>