<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Text Editor on Oracle Scripts</title><link>https://www.oraclescripts.com/tags/text-editor/</link><description>Recent content in Text Editor on Oracle Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>OracleScripts.com</copyright><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oraclescripts.com/tags/text-editor/index.xml" rel="self" type="application/rss+xml"/><item><title>vi Editor Commands Reference for Oracle DBAs</title><link>https://www.oraclescripts.com/post/vi-editor-commands-reference-for-oracle-dbas/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/vi-editor-commands-reference-for-oracle-dbas/</guid><description>
&lt;h2 id="vi-editor-commands-reference-for-oracle-dbas"&gt;vi Editor Commands Reference for Oracle DBAs&lt;/h2&gt;
&lt;p&gt;Every Oracle DBA on Unix or Linux ends up in vi whether they planned to or not. It opens by default when you &lt;code&gt;crontab -e&lt;/code&gt;, it is what &lt;code&gt;visudo&lt;/code&gt; drops you into, and it is the editor on most Oracle Linux and AIX hosts before anyone has installed &lt;code&gt;nano&lt;/code&gt; or configured &lt;code&gt;EDITOR&lt;/code&gt;. Knowing the core commands is not optional — it is the difference between a clean parameter change and a corrupted &lt;code&gt;init.ora&lt;/code&gt; that brings down the instance.&lt;/p&gt;</description></item></channel></rss>