User Tools

Site Tools

Trace:
basic_file_and_directory_tasks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
basic_file_and_directory_tasks [2020/12/10 09:09] – remove all the code tags i didn't need, use indent instead! peteyboybasic_file_and_directory_tasks [2024/08/31 20:20] (current) – – hc9
Line 4: Line 4:
  
 ==== Common File Commands ==== ==== Common File Commands ====
-  - touch -- create a file 
-  - pwd -- print working directory 
-  - ls -- list files in current directory 
-  - cp -- copy a file 
-  - mv -- move a file 
-  - rm -- remove a file 
-  - file -- examine type of file 
-  - less -- read a file 
-  - mkdir -- create a directory 
-  - cd -- change directory 
-  - rmdir -- remove a directory 
-  - clear -- clear screen 
  
-Please note that the above commands each have a man-page that will describe in more detail the full possibilities of each command. In this tutorial, we'll simply give a short overview, enough to get things done on the command line. For more information on man-pages, see the [[http://sdf.lonestar.org/index.cgi?tutorials/findinghelp| Finding Help From Within the Shell]] tutorial.+  - touch – create a file 
 +  - pwd – print working directory 
 +  - ls – list files in current directory 
 +  - cp – copy a file 
 +  - mv – move a file 
 +  - rm – remove a file 
 +  - file – examine type of file 
 +  - less – read a file 
 +  - mkdir – create a directory 
 +  - cd – change directory 
 +  - rmdir – remove a directory 
 +  - clear – clear screen 
 + 
 +Please note that the above commands each have a man-page that will describe in more detail the full possibilities of each command. In this tutorial, we'll simply give a short overview, enough to get things done on the command line. For more information on man-pages, see the [[http://sdf.org/index.cgi?tutorials/findinghelp| Finding Help From Within the Shell]] tutorial.
  
 First some notes about: First some notes about:
Line 34: Line 35:
  
 == File names with spaces == == File names with spaces ==
 +
 If you happen upon a file with empty spaces in its name, you can use the following methods to manipulate it: If you happen upon a file with empty spaces in its name, you can use the following methods to manipulate it:
  
Line 46: Line 48:
   cd backups/text\ pages/   cd backups/text\ pages/
  
-===Tab-Completion===+=== Tab-Completion === 
 Many shells support tab completion. This means if you type the first two or three characters of a file name and press your Tab button, unless you have multiple files with similar beginning names, your shell may be able to finish the word completion for you. Note: if you're not in the same directory as the file you want to tab complete, you'll need to provide the path, which tab-completion can help with also. Many shells support tab completion. This means if you type the first two or three characters of a file name and press your Tab button, unless you have multiple files with similar beginning names, your shell may be able to finish the word completion for you. Note: if you're not in the same directory as the file you want to tab complete, you'll need to provide the path, which tab-completion can help with also.
  
 Also, when naming a file using two or more words, the safest choices you have to use are the underscore, the dash, and the period. Examples are: Also, when naming a file using two or more words, the safest choices you have to use are the underscore, the dash, and the period. Examples are:
- 
  
   my_file.txt   my_file.txt
Line 65: Line 67:
  
 :!: in the examples below, you'll be typing these commands at the shell prompt, so they will appear after a ''$'' or a ''%'' prompt. :!: in the examples below, you'll be typing these commands at the shell prompt, so they will appear after a ''$'' or a ''%'' prompt.
- 
  
 === touch and pwd : create a file and print the working directory === === touch and pwd : create a file and print the working directory ===
Line 143: Line 144:
  
 The commands for copying, moving and removing files if carelessly used may wreak a bit of havoc for you. For these commands, you may want to invoke the interactive option by typing: The commands for copying, moving and removing files if carelessly used may wreak a bit of havoc for you. For these commands, you may want to invoke the interactive option by typing:
- 
  
   cp -i orange.txt backups/orange.txt   cp -i orange.txt backups/orange.txt
Line 152: Line 152:
  
 ==== file : examine type of file ==== ==== file : examine type of file ====
 +
 The //file// command is useful to determine what type of file a file is. In unix-like operating systems, a file's name is fairly flexible and the file extension, e.g. the .txt appendage, is not always necessary. So if someone sent you a file and you wanted to be certain what type of file it was before you opened it, use the //file// command like so: The //file// command is useful to determine what type of file a file is. In unix-like operating systems, a file's name is fairly flexible and the file extension, e.g. the .txt appendage, is not always necessary. So if someone sent you a file and you wanted to be certain what type of file it was before you opened it, use the //file// command like so:
  
Line 228: Line 229:
  
 legacy link: http://sdf.org/?tutorials/file_operations ,v 1.11 2009/11/28 10:39:54 rogerx Exp $ legacy link: http://sdf.org/?tutorials/file_operations ,v 1.11 2009/11/28 10:39:54 rogerx Exp $
- 
  
basic_file_and_directory_tasks.1607591343.txt.gz · Last modified: 2020/12/10 09:09 by peteyboy