Birmingham mumbai

[
 123 
]
To be fair, editing a log file directly is probably not a good idea in practice, but the 
example works. The syslog is a file you may want to open and inspect, but it would 
be a good idea to check the size of the syslog file with the 
ls -lh /var/log/syslog
 
command to make sure it's not excessively large in size, which can slow down the 
server. 
All of that aside, the takeaway here is that you can open a file with 
nano
 directly by 
simply providing it with a path to something. Inside the editor window, you can 
move around with the arrow keys, just like you would in a graphical editor. You 
can also search for a specific string of text, by pressing 
Ctrl
 + 
w
 for 
Where Is
, as it 
mentions in the list of actions near the bottom.
In addition, note the text in the screenshot that is highlighted in red. It's simply 
telling us that we don't have access to edit the file. In that example, I didn't use 
sudo
 because I didn't intend on making any changes to the file. I was able to open it 
without 
sudo
 since my user is a member of the 
syslog
 group. Sometimes, I'll open 
files in an editor that I don't have write permission to make changes to, which serves 
as a fail-safe in case I accidentally do make a change. To make a real change, I can 
close the file and reopen it with 
sudo
.
Anyway, the 
nano
 editor is fairly simplistic. Is there more to it than that? Sure, but 
the most important thing to know is how to open files, edit them, and save them, 
which we've covered in this section. Of course, you can practice with the actions that 
are presented to you at the bottom of the window to go beyond normal usage.
Now, let's take a look at Vim.