GSP/GSP-Agent-Windows
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Initial Windows agent repository

Browse source
This commit is contained in:
Frank Harris 2026-06-08 10:45:20 -05:00
commit a0db0c2e5b
10589 changed files with 3844063 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

288
OGP64/usr/share/doc/nano/html/faq.html Normal file
View file

@ -0,0 +1,288 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en">
<head>
<title>The GNU nano editor FAQ</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="description" content="The genesis story of the nano editor, plus the solution to some common problems.">
<style type="text/css">
.indented { margin-left: 2em; font-family: courier; font-size: 110%; }
</style>
</head>
<body text="#330000" bgcolor="#ffffff" link="#0000ef" vlink="#51188e" alink="#ff0000">
<h1>The GNU nano editor FAQ</h1>
<h3>Table of Contents</h3>
<h3><a href="#1">1. General</a></h3>
<blockquote><p>
<a href="#1.1">1.1. What is GNU nano?</a><br>
<a href="#1.2">1.2. What is the history behind nano?</a><br>
<a href="#1.3">1.3. Why the name change from TIP?</a><br>
<a href="#1.4">1.4. What is the current version of nano?</a><br>
<a href="#1.5">1.5. I want to read the manpage without having to download the program!</a>
</p></blockquote>
<h3><a href="#2">2. Where to get GNU nano.</a></h3>
<blockquote><p>
<a href="#2.1">2.1. FTP and WWW sites that carry nano.</a><br>
<a href="#2.2">2.2. RedHat and derivatives (.rpm) packages.</a><br>
<a href="#2.3">2.3. Debian (.deb) packages.</a><br>
<a href="#2.4">2.4. By git (for the brave).</a>
</p></blockquote>
<h3><a href="#3">3. Installation and Configuration</a></h3>
<blockquote><p>
<a href="#3.1">3.1. How do I install the RPM or DEB package?</a><br>
<a href="#3.2">3.2. Compiling from source: WHAT THE HECK DO I DO NOW?</a><br>
<a href="#3.3">3.3. Why does everything go into /usr/local?</a><br>
<a href="#3.4">3.4. nano should automatically run strip on the binary when installing it!</a><br>
<a href="#3.5">3.5. How can I make the executable smaller? This is too bloated!</a><br>
<a href="#3.6">3.6. Tell me more about this multibuffer stuff!</a><br>
<a href="#3.7">3.7. Tell me more about this verbatim input stuff!</a><br>
<a href="#3.8">3.8. How do I make a .nanorc file that nano will read when I start it?</a><br>
<a href="#3.9">3.9. Why does my self-compiled nano not read /etc/nanorc?</a><br>
</p></blockquote>
<h3><a href="#4">4. Running</a></h3>
<blockquote><p>
<a href="#4.1">4.1. Alt+Up does nothing on a Linux console. How can I make it scroll?</a><br>
<a href="#4.2">4.2. How can I make Ctrl+Shift+Left/Right select words on urxvt?</a><br>
<a href="#4.3">4.3. Ack! My numeric keypad's keys don't work properly when NumLock is off! What can I do?</a><br>
<a href="#4.4">4.4. With what keystroke can I paste text from the clipboard into nano?</a><br>
<a href="#4.5">4.5. How do I select text for or paste text from the clipboard when nano's mouse support is turned on?</a><br>
<a href="#4.6">4.6. When I paste text into a document, each line gets indented further than the last. Why? And how can I stop this?</a><br>
<a href="#4.7">4.7. When I paste from Windows into a remote nano, nano rewraps the lines. What gives?</a><br>
<a href="#4.8">4.8. I've compiled nano with color support, but I don't see any color when I run it!</a><br>
<a href="#4.9">4.9. How do I make nano my default editor (in Pine, mutt, etc.)?</a><br>
</p></blockquote>
<h3><a href="#5">5. Internationalization</a></h3>
<blockquote><p>
<a href="#5.1">5.1. There's no translation for my language!</a><br>
<a href="#5.2">5.2. I don't like the translation for &lt;x&gt; in my language. How can I fix it?</a><br>
<a href="#5.3">5.3. What is the status of Unicode support?</a>
</p></blockquote>
<h3><a href="#6">6. Advocacy and Licensing</a></h3>
<blockquote><p>
<a href="#6.1">6.1. Why should I use nano instead of Pico?</a><br>
<a href="#6.2">6.2. Why should I use Pico instead of nano?</a><br>
<a href="#6.3">6.3. What is so bad about the older Pine license?</a><br>
<a href="#6.4">6.4. Okay, well, what mail program should I use then?</a>
</p></blockquote>
<h3><a href="#7">7. Miscellaneous</a></h3>
<blockquote><p>
<a href="#7.1">7.1. Where can I ask questions or send suggestions?</a><br>
<a href="#7.2">7.2. How do I submit a bug report or patch?</a><br>
<a href="#7.3">7.3. I want to send the development team a big load of cash (or just a thank you).</a><br>
<a href="#7.4">7.4. How do I join the development team?</a><br>
<a href="#7.5">7.5. Can I have write access to the git tree?</a>
</p></blockquote>
<hr width="100%">
<h1><a name="1"></a>1. General</h1>
<h3><a name="1.1"></a>1.1. What is GNU nano?</h3>
<blockquote><p>GNU nano was designed to be a free replacement for the Pico text editor, part of the Pine email suite from <a href="http://www.washington.edu/pine/">The University of Washington</a>. It aimed to &quot;emulate Pico as closely as is reasonable and then include extra functionality&quot;.</p></blockquote>
<h3><a name="1.2"></a>1.2. What is the history behind nano?</h3>
<blockquote><p>Funny you should ask!</p>
<p><b>In the beginning...</b></p>
<p>For years Pine was THE program used to read email on a Unix system. The Pico text editor is the portion of the program one would use to compose his or her mail messages. Many beginners to Unix flocked to Pico and Pine because of their well organized, easy to use interfaces. With the proliferation of GNU/Linux in the mid to late 90's, many University students became intimately familiar with the strengths (and weaknesses) of Pine and Pico.</p>
<p><b>Then came Debian...</b></p>
<p>The <a href="https://www.debian.org/">Debian GNU/Linux</a> distribution, known for its strict standards in distributing truly &quot;free&quot; software (i.e. software with no restrictions on redistribution), would not include a binary package for Pine or Pico. Many people had a serious dilemma: they loved these programs, but the versions available at the time were not truly free software in the <a href="https://www.gnu.org/philosophy/free-sw.html">GNU</a> sense of the word.</p>
<p><b>The event...</b></p>
<p>It was in late 1999 when Chris Allegretta (our hero) was yet again complaining to himself about the less-than-perfect license Pico was distributed under, the 1000 makefiles that came with it and how just a few small improvements could make it the Best Editor in the World (TM). Having been a convert from Slackware to Debian, he missed having a simple binary package that included Pine and Pico, and had grown tired of downloading them himself.</p>
<p>Finally something snapped inside and Chris coded and hacked like a madman for many hours straight one weekend to make a (barely usable) Pico clone, at the time called TIP (Tip Isn't Pico). The program could not be invoked without a filename, could not save files, had no help text display, spell checker, and so forth. But over time it improved, and with the help of a few great coders it matured to the (hopefully) stable state it is in today.</p>
<p>In February 2001, nano was declared an official GNU program by Richard Stallman. nano also reached its first production release on March 22, 2001.</p></blockquote>
<h3><a name="1.3"></a>1.3. Why the name change from TIP?</h3>
<blockquote><p>On January 10, 2000, TIP was officially renamed to nano because of a namespace conflict with another program called 'tip'. The original 'tip' program &quot;establishes a full duplex terminal connection to a remote host&quot;, and was included with many older Unix systems (and newer ones like Solaris). The conflict was not noticed at first because there is no 'tip' utility included with most GNU/Linux distributions (where nano was developed).</p></blockquote>
<h3><a name="1.4"></a>1.4. What is the current version of nano?</h3>
<blockquote><p>The current version of nano <i>should</i> be <b>8.0</b>. Of course, you should always check the <a href="https://nano-editor.org/">nano homepage</a> to see what the latest and greatest version is.</p></blockquote>
<h3><a name="1.5"></a>1.5. I want to read the man page without having to download the program!</h3>
<blockquote><p>Jeez, demanding, aren't we? Okay, look <a href="https://nano-editor.org/dist/latest/nano.1.html">here</a>.</p></blockquote>
<hr width="100%">
<h1><a name="2"></a>2. Where to get GNU nano.</h1>
<h3><a name="2.1"></a>2.1. Web sites that carry nano.</h3>
<blockquote><p>The nano source tarballs can be downloaded from the following web sites:</p>
<ul>
<li><a href="https://nano-editor.org/dist/latest/">https://nano-editor.org/dist/latest/</a></li>
<li><a href="https://ftpmirror.gnu.org/gnu/nano/">https://ftpmirror.gnu.org/gnu/nano/</a></li>
</ul>
</blockquote>
<h3><a name="2.2"></a>2.2. RPM packages (RedHat, OpenSuse, and derivatives).</h3>
<blockquote>
<ul>
<li><a href="https://kojipkgs.fedoraproject.org//packages/nano/">https://kojipkgs.fedoraproject.org//packages/nano/</a></li>
<li><a href="https://software.opensuse.org/package/nano">https://software.opensuse.org/package/nano</a></li>
</ul>
</blockquote>
<h3><a name="2.3"></a>2.3. Deb packages (Debian and derivatives):</h3>
<blockquote><p>Debian users can check out the current nano packages for:</p>
<ul>
<li><a href="https://packages.debian.org/stable/editors/nano">stable</a></li>
<li><a href="https://packages.debian.org/testing/editors/nano">testing</a></li>
<li><a href="https://packages.debian.org/unstable/editors/nano">unstable</a></li>
</ul>
<p>You can also have a look at the <a href="http://ftp.debian.org/debian/pool/main/n/nano/">Package Pool</a> to see all the available binary and source packages.</p>
</blockquote>
<h3><a name="2.4"></a>2.4. By git (for the brave).</h3>
<blockquote><p>For the "bleeding edge" current version of nano, you can use <b>git</b> to download the current source code. <i>Note:</i> believe it or not, by downloading code that has not yet stabilized into an official release, there could quite possibly be bugs, in fact the code may not even compile! Anyway, see <a href="http://git.savannah.gnu.org/cgit/nano.git/tree/README.hacking">the hacking document</a> for info on getting and building nano from git.</p></blockquote>
<hr width="100%">
<h1><a name="3"></a>3. Installation and Configuration</h1>
<h3><a name="3.1"></a>3.1. How do I install the RPM or DEB package?</h3>
<blockquote><p>It's simple really! As root, type <b>rpm -Uvh nano-x.y-1*.rpm</b> if you have a RedHat-ish system or <b>dpkg -i nano_x.y-1*.deb</b> if you have a Debian-ish system, where <b>x.y</b> is the version number of nano. There are other programs to install packages, and if you wish to use those, knock yourself out.</p></blockquote>
<h3><a name="3.2"></a>3.2. Compiling from source: WHAT THE HECK DO I DO NOW?</h3>
<blockquote><p>Okay, take a deep breath, this really isn't hard. Unpack the nano source with a command like:</p>
<p class="indented"><b>tar -xvf nano-x.y.tar.gz</b></p>
<p>Then you need to run <b>configure</b> with any options you might want (if any).</p>
<p>The average case is this:</p>
<p class="indented"><b>cd nano-x.y/</b><br>
<b>./configure</b><br>
<b>make</b><br>
<b>make install</b>&nbsp;&nbsp; #(as root, of course)</p></blockquote>
<h3><a name="3.3"></a>3.3. Why does everything go into /usr/local?</h3>
<blockquote><p>Well, that's what the <b>configure</b> script defaults to. If you wish to change this, simply do this:</p>
<p class="indented"><b>./configure --prefix=/usr</b></p>
<p>This will put nano into /usr/bin when you run <b>make install</b>.</p></blockquote>
<h3><a name="3.4"></a>3.4. nano should automatically run strip on the binary when installing it!</h3>
<blockquote><p>It does when you use <b>make install-strip</b>. The default <b>make install</b> does not, and will not, run strip automatically.</p></blockquote>
<h3><a name="3.5"></a>3.5. How can I make the executable smaller? This is too bloated!</h3>
<blockquote><p>Actually, there are several parts of the editor that can be disabled. You can pass arguments to the <b>configure</b> script that disable certain features. Here's a brief list:</p>
<pre>
<b>--disable-browser</b> Disable the built-in file browser
<b>--disable-color</b> Disable color and syntax highlighting
<b>--disable-comment</b> Disable the comment/uncomment function
<b>--disable-extra</b> Disable the easter egg
<b>--disable-formatter</b> Disable the formatting tool
<b>--disable-help</b> Disable the built-in help texts
<b>--disable-histories</b> Disable the saving of search strings and cursor positions
<b>--disable-justify</b> Disable the justify/unjustify functions
<b>--disable-libmagic</b> Disable the use of libmagic for determining a file's syntax
<b>--disable-linenumbers</b> Disable line numbering
<b>--disable-linter</b> Disable the linting tool
<b>--disable-mouse</b> Disable mouse support
<b>--disable-multibuffer</b> Disable the opening of multiple file buffers
<b>--disable-nanorc</b> Disable the use of .nanorc files
<b>--disable-operatingdir</b> Disable the setting of an operating directory
<b>--disable-speller</b> Disable the spell-checking tool
<b>--disable-tabcomp</b> Disable the tab-completion functions
<b>--disable-wordcomp</b> Disable the word-completion function
<b>--disable-wrapping</b> Disable all hard-wrapping of text</pre>
<p>There's also the <b>--enable-tiny</b> option which disables everything above, as well as some larger chunks of the program (like the undo/redo code and the code for selecting text). Also, if you know you don't need other languages, you can use <b>--disable-nls</b> to disable internationalization and save a few kilobytes. And finally, there's always good old <b>strip</b> to remove all unneeded symbols.</p>
</blockquote>
<h3><a name="3.6"></a>3.6. Tell me more about this multibuffer stuff!</h3>
<blockquote><p>To use multiple file buffers, you must not have configured nano with <b>--disable-multibuffer</b> nor with <b>--enable-tiny</b> (use <b>nano -V</b> to check the compilation options). Then when you want to insert a file into its own buffer instead of into the current file, just hit <b>Meta-F</b> after typing <b>^R</b>. If you always want files to be loaded into their own buffers, use the <b>-F</b> or <b>--multibuffer</b> flag when you invoke nano, or add <b>set multibuffer</b> to your .nanorc file.</p>
<p>You can move between the buffers you have open with the <b>Meta-&lt;</b> and <b>Meta-&gt;</b> keys, or more easily without holding Shift: <b>Meta-,</b> and <b>Meta-.</b> (clear as mud, right? =-). When you have more than one buffer open, the ^X shortcut will say &quot;Close&quot;, instead of &quot;Exit&quot;.</p></blockquote>
<h3><a name="3.7"></a>3.7. Tell me more about this verbatim input stuff!</h3>
<blockquote><p>When you want to insert a literal character into the file you're editing, such as a control character that nano usually treats as a command, first press <b>Meta-V</b> (if you're not at a prompt, you'll get the message &quot;Verbatim Input&quot; on the status bar), then press the key(s) that generate the character you want.</p>
<p>Alternatively, if Unicode support is enabled (see section <a href="#5.3">5.3</a>), you can press <b>Meta-V</b> and then type a six-digit hexadecimal code (from 000000 to 10FFFF, case-insensitive), and the character with the corresponding value will be inserted. The status bar will change to &quot;Unicode Input: ......&quot; when you do this.</p></blockquote>
<h3><a name="3.8"></a>3.8. How do I make a .nanorc file that will be read when I start nano?</h3>
<blockquote><p>It's not hard at all! Simply copy the <b>sample.nanorc</b> from the doc/ directory in the nano source package (or from /usr/doc/nano on your system) to <b>.nanorc</b> in your home directory, and then edit it. If you didn't get a sample nanorc, the syntax of the file is simple: features are turned on and off by using the words <b>set</b> and <b>unset</b> followed by the long option name of the feature (see <b>man nanorc</b> for the full list of options). For example, &quot;set quickblank&quot; or &quot;set smarthome&quot;. Of course, for this to work, your nano must <b>not</b> have been compiled with <b>--disable-nanorc</b>.</p></blockquote>
<h3><a name="3.9"></a>3.9. Why does my self-compiled nano not read /etc/nanorc?</h3>
<blockquote><p>By default (see <a href="#3.3">3.3</a>), nano gets installed into /usr/local. This also means that, at startup, nano will read <b>/usr/local/etc/nanorc</b> instead of <b>/etc/nanorc</b>. You can make a symlink from the former to the latter if you want your self-compiled nano to read the same nanorc as the system-installed nano. Or you can configure your nano to overwrite the system nano (again, see <a href="#3.3">3.3</a>).</p></blockquote>
<hr width="100%">
<h1><a name="4"></a>4. Running</h1>
<h3><a name="4.1"></a>4.1. Alt+Up does nothing on a Linux console. How can I make it scroll?</h3>
<blockquote><p>On Debian and its derivatives, the <b>Alt+Up</b> keystroke on a Linux console
produces by default a 'KeyboardSignal', which normally does absolutely nothing and is useless
for the average user. To get the keystroke to do what it ought to do (scroll the viewport
one row up), run this in a Linux console:</p>
<p class="indented"><b>dumpkeys --full | sed s/KeyboardSignal/Up/ | sudo loadkeys -</b></p>
<p>You will need to run this command whenever you first switch to a Linux console.</p>
<p>Or you can (as root) execute the following little script just once:</p>
<p class="indented"><b>for file in /etc/console-setup/cached*.kmap.gz; do<br>
&nbsp;&nbsp;&nbsp;&nbsp;gunzip $file;<br>
&nbsp;&nbsp;&nbsp;&nbsp;sed -i 's/KeyboardSignal/Up/' ${file%.gz};<br>
&nbsp;&nbsp;&nbsp;&nbsp;gzip ${file%.gz};<br>
done</b></p></blockquote>
<h3><a name="4.2"></a>4.2. How can I make Ctrl+Shift+Left/Right select words on urxvt?</h3>
<blockquote><p>The urxvt terminal emulator produces non-standard escape sequences for the modified cursor keys. These deviant sequences are not listed in the terminfo database, which means that ncurses does not recognize them. The easiest way around this is to tell urxvt to produce xterm-compatible escape sequences for the relevant keystrokes. To achieve this, add the following lines to your ~/.Xresources file:</p>
<pre>
URxvt.iso14755_52: False
URxvt.keysym.C-S-Up: \033[1;6A
URxvt.keysym.C-S-Down: \033[1;6B
URxvt.keysym.C-S-Right: \033[1;6C
URxvt.keysym.C-S-Left: \033[1;6D
URxvt.keysym.M-Up: \033[1;3A
URxvt.keysym.M-Down: \033[1;3B
URxvt.keysym.M-Right: \033[1;3C
URxvt.keysym.M-Left: \033[1;3D
URxvt.keysym.M-Insert: \033[2;3~
URxvt.keysym.M-Delete: \033[3;3~
URxvt.keysym.M-Page_Up: \033[5;3~
URxvt.keysym.M-Page_Down: \033[6;3~</pre>
<p>Then run <b>xrdb ~/.Xresources</b> and restart your urxvt terminal. Now <b>Ctrl+Shift+Left</b> and <b>Ctrl+Shift+Right</b> will select words, <b>Alt+Up</b> and <b>Alt+Down</b> will scroll the text without moving the cursor, and several such things more.</p></blockquote>
<h3><a name="4.3"></a>4.3. Ack! My numeric keypad's keys don't work properly when NumLock is off! What can I do?</h3>
<blockquote><p>You can use the <b>-K</b> or <b>--rawsequences</b> option on the command line, or add the line <b>set rawsequences</b> to your .nanorc. However, nano's mouse support will be disabled if you do any of these things.</p></blockquote>
<h3><a name="4.4"></a>4.4. With what keystroke can I paste text from the clipboard into nano?</h3>
<blockquote><p>In most desktop environments <b>Shift+Insert</b> will paste the contents of the clipboard.</p></blockquote>
<h3><a name="4.5"></a>4.5. How do I select text for or paste text from the clipboard when nano's mouse support is turned on?</h3>
<blockquote><p>Try holding down the Shift key and selecting or pasting the text as you normally would.</p></blockquote>
<h3><a name="4.6"></a>4.6. When I paste text into a document, each line gets indented further than the last. Why? And how can I stop this?</h3>
<blockquote><p>You have the <i>autoindent</i> feature turned on. Hit <b>Meta-I</b> to turn it off, paste your text, and then hit <b>Meta-I</b> again to turn it back on.</p>
<p><i>Update:</i> Since version 4.8, nano will suppress auto-indentation during a paste (when your terminal understands <a href="https://en.wikipedia.org/wiki/Bracketed-paste">bracketed pastes</a>), so you no longer need to toggle it off and on manually.</p></blockquote>
<h3><a name="4.7"></a>4.7. When I paste from Windows into a remote nano, nano rewraps the lines. What gives?</h3>
<blockquote><p>When pasting from Windows, in some situations linefeeds are sent instead of carriage returns (Enters). And linefeeds are <b>^J</b>s, which make nano justify (rewrap) the current paragraph. To prevent these linefeeds from causing these unwanted justifications, add this line to your .nanorc on the remote Linux box: <b>unbind ^J main</b> or <b>bind ^J enter main</b>, depending on whether the paste contains CR + LF or only LF.</p>
<p><i>Update:</i> Since version 4.8, nano will ignore linefeed characters in a paste (when your terminal understands <a href="https://en.wikipedia.org/wiki/Bracketed-paste">bracketed pastes</a>), so you no longer need the above workaround.</p></blockquote>
<h3><a name="4.8"></a>4.8. I've compiled nano with color support, but I don't see any color when I run it!</h3>
<blockquote><p>If you want nano to actually use color, you have to specify the color configurations you want it to use in your .nanorc. Several example configurations are in the <b>syntax/</b> subdirectory of the nano source, which are normally installed to <b>/usr/local/share/nano/</b>. To enable all of them, uncomment the line <b># include "/usr/local/share/nano/*.nanorc"</b> in your nanorc. See also section <a href="#3.9">3.9</a>.</p></blockquote>
<h3><a name="4.9"></a>4.9. How do I make nano my default editor (in Pine, mutt, etc.)?</h3>
<blockquote><p>You need to make nano your $EDITOR. If you want this to be saved, you should put a line like this in your <b>.bashrc</b> if you use bash (or <b>.zshrc</b> if you believe in zsh):</p>
<p class="indented"><b>export EDITOR=/usr/local/bin/nano</b></p>
<p>or, if you use tcsh, put this in your <b>.cshrc</b> file:</p>
<p class="indented"><b>setenv EDITOR /usr/local/bin/nano</b></p>
<p>Change /usr/local/bin/nano to wherever nano is installed on your system. Type &quot;which nano&quot; to find out. This will not take effect until the next time you log in. So log out and back in again.</p>
<p>Then, on top of that, if you use Pine, you must go into setup (type <b>S</b> at the main menu), and then configure (type <b>C</b>). Hit Enter on the lines that say:</p>
<p class="indented"><b>[ ] enable-alternate-editor-cmd</b><br>
<b>[ ] enable-alternate-editor-implicitly</b></p>
<p>Then exit (<b>E</b>) and select Yes (<b>Y</b>).</p>
<p>If you're a mutt user, you should see an effect immediately the next time you log in. No further configuration is needed. However, if you want to let people know you use nano to compose your email messages, you can put a line like this in your <b>.muttrc</b>:</p>
<p class="indented"><b>my_hdr X-Composer: nano-x.y</b></p>
<p>Again, replace x.y with the version of nano you use.</p></blockquote>
<hr width="100%">
<h1><a name="5"></a>5. Internationalization</h1>
<h3><a name="5.1"></a>5.1. There's no translation for my language!</h3>
<blockquote><p>In June 2001, GNU nano entered the <a href="https://translationproject.org/html/welcome.html">Translation Project</a> and since then, translations should be managed from there.</p>
<p>If there isn't a translation for your language, you could ask <a href="https://translationproject.org/team/">your language team</a> to translate nano, or better still, join that team and do it yourself. Joining a team is easy. You just need to ask the team leader to add you, and then send a <a href="https://translationproject.org/disclaim.txt">translation disclaimer to the FSF</a> (this is necessary as nano is an official GNU package, but it does <b>not</b> mean that you transfer the rights of your work to the FSF, it's just so the FSF can legally manage them).</p>
<p>In any case, translating nano is easy. Just grab the latest <b>nano.pot</b> file listed on <a href="https://translationproject.org/domain/nano.html">nano's page</a> at the TP, and translate each <b>msgid</b> line into your native language on the <b>msgstr</b> line. When you're done, you should send it to the TP's central PO-file repository.</p></blockquote>
<h3><a name="5.2"></a>5.2. I don't like the translation for &lt;x&gt; in my language. How can I fix it?</h3>
<blockquote><p>The best way is to send an e-mail with your suggested corrections to the team's mailing list. The address is mentioned in the <code>Language-Team:</code> field in the relevant PO file. The team leader or the assigned translator can then make the changes reach the nano-devel list.</p></blockquote>
<h3><a name="5.3"></a>5.3. What is the status of Unicode support?</h3>
<blockquote><p>Unicode should be fully usable nowadays. When the encoding of your terminal is set to UTF-8, and your locale (mainly the LANG environment variable) is UTF-8 too, then you should be able to read, enter and save Unicode text.</p></blockquote>
<hr width="100%">
<h1><a name="6"></a>6. Advocacy and Licensing</h1>
<h3><a name="6.1"></a>6.1. Why should I use nano instead of Pico?</h3>
<blockquote><p>If you want features like undo/redo, syntax highlighting, line numbers, soft-wrapping, opening multiple files at once, an interface localized to your language, or search and replace with support for regular expressions, then you want nano.</p></blockquote>
<h3><a name="6.2"></a>6.2. Why should I use Pico instead of nano?</h3>
<blockquote><p>If you use your editor only to write emails or other texts and have no need for the above-mentioned features, then Pico will do fine for you.</p></blockquote>
<h3><a name="6.3"></a>6.3. What is so bad about the older Pine license?</h3>
<blockquote><p>The U of W license for older versions of Pine and Pico is not considered truly Free Software according to both the Free Software Foundation and the <a href="https://www.debian.org/social_contract#guidelines">Debian Free Software Guidelines</a>. The main problem regards the limitations on distributing derived works: according to UW, you can distribute their software, and you can modify it, but you can not do both, i.e. distribute modified binaries.</p></blockquote>
<h3><a name="6.4"></a>6.4. Okay, well, what mail program should I use then?</h3>
<blockquote><p>If you are looking to use a Free Software program similar to Pine, and Emacs is not your thing, you should definitely take a look at <a href="http://www.mutt.org/">mutt</a>. It is a full-screen, console based mail program that actually has a lot more flexibility than Pine, but has a keymap included in the distribution that allows you to use the same keystrokes as Pine would to send and receive mail. It's also under the GNU General Public License, version 2.0.</p>
<p>Of course, due to the license change you can now use the <a href="http://www.washington.edu/alpine/">Alpine distribution</a> of PINE as it is now considered Free Software, but you would be sacrificing many of nano's features to do so.</p></blockquote>
<hr width="100%">
<h1><a name="7"></a>7. Miscellaneous</h1>
<h3><a name="7.1"></a>7.1. Where can I ask questions or send suggestions?</h3>
<blockquote><p>There are three mailing lists for nano hosted at <a href="https://savannah.gnu.org/">Savannah</a>: info-nano, help-nano and nano-devel. info-nano is a very low traffic list where new versions of nano are announced (surprise!). help-nano is for getting help with the editor without needing to hear all of the development issues surrounding it. nano-devel is a normally low, sometimes high traffic list for discussing the present and future development of nano. Here are links to where you can sign up for a given list:</p>
<p>info-nano - <a href="https://lists.gnu.org/mailman/listinfo/info-nano/">https://lists.gnu.org/mailman/listinfo/info-nano/</a><br>
help-nano - <a href="https://lists.gnu.org/mailman/listinfo/help-nano/">https://lists.gnu.org/mailman/listinfo/help-nano/</a><br>
nano-devel - <a href="https://lists.gnu.org/mailman/listinfo/nano-devel/">https://lists.gnu.org/mailman/listinfo/nano-devel/</a></p></blockquote>
<h3><a name="7.2"></a>7.3. How do I submit a bug report or patch?</h3>
<blockquote>
<p>The best way to submit bugs is through the <a href="https://savannah.gnu.org/bugs/?group=nano">Savannah bug tracker</a>, as you can check whether the bug you are reporting has already been submitted, and it makes it easier for the maintainers to keep track of them.
<p>You can submit patches for nano via <a href="https://savannah.gnu.org/patch/?group=nano">Savannah's patch manager</a>.</p></blockquote>
<h3><a name="7.3"></a>7.3. I want to send the development team a big load of cash (or just a thank you).</h3>
<blockquote><p>That's fine. Send it <a href="mailto:nano-devel@gnu.org">our way</a>! Better yet, fix a <a href="https://savannah.gnu.org/bugs/?group=nano">bug</a> in the program or implement a <a href="https://nano-editor.org/dist/latest/TODO">cool feature</a> and send us that instead (though cash is fine too).</p></blockquote>
<h3><a name="7.4"></a>7.4. How do I join the development team?</h3>
<blockquote><p>The easiest way is to consistently send in good patches that add some needed functionality, fix a bug or two, and/or make the program more optimized/efficient. Then ask nicely and you will probably be added to the Savannah development list and be given write access after a while. There is a lot of responsibility that goes along with being a team member, so don't think it's just something to add to your resume.</p></blockquote>
<h3><a name="7.5"></a>7.5. Can I have write access to the git tree?</h3>
<blockquote><p>Re-read section <a href="#7.4">7.4</a> and you should know the answer.</p></blockquote>
<hr width="100%">
</body>
</html>

764
OGP64/usr/share/doc/nano/html/nano.1.html Normal file
View file

@ -0,0 +1,764 @@
<!-- Creator : groff version 1.22.4 -->
<!-- CreationDate: Wed May 1 08:26:02 2024 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="Content-Style" content="text/css">
<style type="text/css">
p { margin-top: 0; margin-bottom: 0; vertical-align: top }
pre { margin-top: 0; margin-bottom: 0; vertical-align: top }
table { margin-top: 0; margin-bottom: 0; vertical-align: top }
h1 { text-align: center }
</style>
<title>NANO</title>
</head>
<body>
<h1 align="center">NANO</h1>
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#NOTICE">NOTICE</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#EDITING">EDITING</a><br>
<a href="#OPTIONS">OPTIONS</a><br>
<a href="#TOGGLES">TOGGLES</a><br>
<a href="#FILES">FILES</a><br>
<a href="#NOTES">NOTES</a><br>
<a href="#BUGS">BUGS</a><br>
<a href="#HOMEPAGE">HOMEPAGE</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<hr>
<h2>NAME
<a name="NAME"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">nano -
Nano&rsquo;s ANOther text editor, inspired by Pico</p>
<h2>SYNOPSIS
<a name="SYNOPSIS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>nano</b>
[<i>options</i>]
[[<b>+</b><i>line</i>[<b>,</b><i>column</i>]]
<i>file</i>]...</p>
<p style="margin-left:11%; margin-top: 1em"><b>nano</b>
[<i>options</i>]
[<i>file</i>[<b>:</b><i>line</i>[<b>:</b><i>column</i>]]]...</p>
<p style="margin-left:11%; margin-top: 1em"><b>nano</b>
[<i>options</i>]
[[<b>+</b>[<b>crCR</b>]{<b>/</b>|<b>?</b>}<i>string</i>]
<i>file</i>]...</p>
<h2>NOTICE
<a name="NOTICE"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Since version
8.0, to be newcomer friendly, <b>^F</b> starts a forward
search, <b>^B</b> starts a backward search, <b>M-F</b>
searches the next occurrence forward, and <b>M-B</b>
searches the next occurrence backward. If you want those
keystrokes to do what they did before version 8.0, add the
following lines at the end of your <i>nanorc</i> file:</p>
<p style="margin-left:17%; margin-top: 1em"><b>bind ^F
forward main <br>
bind ^B back main <br>
bind M-F formatter main <br>
bind M-B linter main</b></p>
<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>nano</b> is
a small and friendly text editor. It copies the look and
feel of Pico, but is free software, and implements several
features that Pico lacks, such as: opening multiple files,
scrolling per line, undo/redo, syntax coloring, line
numbering, and soft-wrapping overlong lines.</p>
<p style="margin-left:11%; margin-top: 1em">When giving a
filename on the command line, the cursor can be put on a
specific line by adding the line number with a plus sign
(<b>+</b>) before the filename, and even in a specific
column by adding it with a comma. Negative numbers count
from the end of the file or line. The line and column
numbers may also be specified by gluing them with colons
after the filename. (When a filename contains a colon
followed by digits, escape the colon by preceding it with a
triple backslash.)</p>
<p style="margin-left:11%; margin-top: 1em">The cursor can
be put on the first or last occurrence of a specific string
by specifying that string after <b>+/</b> or <b>+?</b>
before the filename. The string can be made case sensitive
and/or caused to be interpreted as a regular expression by
inserting <b>c</b> and/or <b>r</b> after the <b>+</b> sign.
These search modes can be explicitly disabled by using the
uppercase variant of those letters: <b>C</b> and/or
<b>R</b>. When the string contains spaces, it needs to be
enclosed in quotes. To give an example: to open a file at
the first occurrence of the word &quot;Foo&quot;, you would
do:</p>
<p style="margin-left:17%; margin-top: 1em"><b>nano
+c/Foo</b> <i>file</i></p>
<p style="margin-left:11%; margin-top: 1em">As a special
case: if instead of a filename a dash (<b>-</b>) is given,
<b>nano</b> will read data from standard input.</p>
<h2>EDITING
<a name="EDITING"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Entering text
and moving around in a file is straightforward: typing the
letters and using the normal cursor movement keys. Commands
are entered by using the Control (^) and the Alt or Meta
(M-) keys. Typing <b>^K</b> deletes the current line and
puts it in the cutbuffer. Consecutive <b>^K</b>s will put
all deleted lines together in the cutbuffer. Any cursor
movement or executing any other command will cause the next
<b>^K</b> to overwrite the cutbuffer. A <b>^U</b> will paste
the current contents of the cutbuffer at the current cursor
position.</p>
<p style="margin-left:11%; margin-top: 1em">When a more
precise piece of text needs to be cut or copied, you can
mark its start with <b>^6</b>, move the cursor to its end
(the marked text will be highlighted), and then use
<b>^K</b> to cut it, or <b>M-6</b> to copy it to the
cutbuffer. You can also save the marked text to a file with
<b>^O</b>, or spell check it with <b>^T^T</b>.</p>
<p style="margin-left:11%; margin-top: 1em">On some
terminals, text can be selected also by holding down Shift
while using the arrow keys. Holding down the Ctrl or Alt key
too will increase the stride. Any cursor movement without
Shift being held will cancel such a selection.</p>
<p style="margin-left:11%; margin-top: 1em">Any valid
Unicode code point can be inserted into the buffer by typing
<b>M-V</b> followed by the hexadecimal digits of the code
point (concluded with <b>&lt;Space&gt;</b> or
<b>&lt;Enter&gt;</b> when it are fewer than six digits). A
literal control code (except <b>^J</b>) can be inserted by
typing <b>M-V</b> followed by the pertinent keystroke.</p>
<p style="margin-left:11%; margin-top: 1em">The two lines
at the bottom of the screen show some important commands;
the built-in help (<b>^G</b>) lists all the available ones.
The default key bindings can be changed via a <i>nanorc</i>
file -- see <b>nanorc</b>(5).</p>
<h2>OPTIONS
<a name="OPTIONS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>-A</b>,
<b>--smarthome</b></p>
<p style="margin-left:22%;">Make the Home key smarter. When
Home is pressed anywhere but at the very beginning of
non-whitespace characters on a line, the cursor will jump to
that beginning (either forwards or backwards). If the cursor
is already at that position, it will jump to the true
beginning of the line.</p>
<p style="margin-left:11%;"><b>-B</b>, <b>--backup</b></p>
<p style="margin-left:22%;">When saving a file, back up the
previous version of it, using the current filename suffixed
with a tilde (<b>~</b>).</p>
<p style="margin-left:11%;"><b>-C&nbsp;</b><i>directory</i>,
<b>--backupdir=</b><i>directory</i></p>
<p style="margin-left:22%;">Make and keep not just one
backup file, but make and keep a uniquely numbered one every
time a file is saved -- when backups are enabled
(<b>-B</b>). The uniquely numbered files are stored in the
specified <i>directory</i>.</p>
<p style="margin-left:11%;"><b>-D</b>,
<b>--boldtext</b></p>
<p style="margin-left:22%;">For the interface, use bold
instead of reverse video. This will be overridden by setting
the options <b>titlecolor</b>, <b>statuscolor</b>,
<b>keycolor</b>, <b>functioncolor</b>, <b>numbercolor</b>,
and/or <b>selectedcolor</b> in your nanorc file. See
<b>nanorc</b>(5).</p>
<p style="margin-left:11%;"><b>-E</b>,
<b>--tabstospaces</b></p>
<p style="margin-left:22%;">Convert each typed tab to
spaces -- to the number of spaces that a tab at that
position would take up. (Note: pasted tabs are not
converted.)</p>
<p style="margin-left:11%;"><b>-F</b>,
<b>--multibuffer</b></p>
<p style="margin-left:22%;">Read a file into a new buffer
by default.</p>
<p style="margin-left:11%;"><b>-G</b>, <b>--locking</b></p>
<p style="margin-left:22%;">Use vim-style file locking when
editing files.</p>
<p style="margin-left:11%;"><b>-H</b>,
<b>--historylog</b></p>
<p style="margin-left:22%;">Save the last hundred search
strings and replacement strings and executed commands, so
they can be easily reused in later sessions.</p>
<p style="margin-left:11%;"><b>-I</b>,
<b>--ignorercfiles</b></p>
<p style="margin-left:22%;">Don&rsquo;t look at the
system&rsquo;s <i>nanorc</i> nor at the user&rsquo;s
<i>nanorc</i>.</p>
<p style="margin-left:11%;"><b>-J&nbsp;</b><i>number</i>,
<b>--guidestripe=</b><i>number</i></p>
<p style="margin-left:22%;">Draw a vertical stripe at the
given column, to help judge the width of the text. (The
color of the stripe can be changed with <b>set
stripecolor</b> in your <i>nanorc</i> file.)</p>
<p style="margin-left:11%;"><b>-K</b>,
<b>--rawsequences</b></p>
<p style="margin-left:22%;">Interpret escape sequences
directly, instead of asking <b>ncurses</b> to translate
them. (If you need this option to get some keys to work
properly, it means that the terminfo terminal description
that is used does not fully match the actual behavior of
your terminal. This can happen when you ssh into a BSD
machine, for example.) Using this option disables
<b>nano</b>&rsquo;s mouse support.</p>
<p style="margin-left:11%;"><b>-L</b>,
<b>--nonewlines</b></p>
<p style="margin-left:22%;">Don&rsquo;t automatically add a
newline when a text does not end with one. (This can cause
you to save non-POSIX text files.)</p>
<p style="margin-left:11%;"><b>-M</b>,
<b>--trimblanks</b></p>
<p style="margin-left:22%;">Snip trailing whitespace from
the wrapped line when automatic hard-wrapping occurs or when
text is justified.</p>
<p style="margin-left:11%;"><b>-N</b>,
<b>--noconvert</b></p>
<p style="margin-left:22%;">Disable automatic conversion of
files from DOS/Mac format.</p>
<p style="margin-left:11%;"><b>-O</b>,
<b>--bookstyle</b></p>
<p style="margin-left:22%;">When justifying, treat any line
that starts with whitespace as the beginning of a paragraph
(unless auto-indenting is on).</p>
<p style="margin-left:11%;"><b>-P</b>,
<b>--positionlog</b></p>
<p style="margin-left:22%;">For the 200 most recent files,
log the last position of the cursor, and place it at that
position again upon reopening such a file.</p>
<p style="margin-left:11%;"><b>-Q
&quot;</b><i>regex</i><b>&quot;</b>,
<b>--quotestr=&quot;</b><i>regex</i><b>&quot;</b></p>
<p style="margin-left:22%;">Set the regular expression for
matching the quoting part of a line. The default value is
&quot;<b>^([&nbsp;\t]*([!#%:;&gt;|}]|//))+</b>&quot;. (Note
that <b>\t</b> stands for an actual Tab.) This makes it
possible to rejustify blocks of quoted text when composing
email, and to rewrap blocks of line comments when writing
source code.</p>
<p style="margin-left:11%;"><b>-R</b>,
<b>--restricted</b></p>
<p style="margin-left:22%;">Restricted mode: don&rsquo;t
read or write to any file not specified on the command line.
This means: don&rsquo;t read or write history files;
don&rsquo;t allow suspending; don&rsquo;t allow spell
checking; don&rsquo;t allow a file to be appended to,
prepended to, or saved under a different name if it already
has one; and don&rsquo;t make backup files. Restricted mode
can also be activated by invoking <b>nano</b> with any name
beginning with &rsquo;r&rsquo; (e.g. &quot;rnano&quot;).</p>
<p style="margin-left:11%;"><b>-S</b>,
<b>--softwrap</b></p>
<p style="margin-left:22%;">Display over multiple screen
rows lines that exceed the screen&rsquo;s width. (You can
make this soft-wrapping occur at whitespace instead of
rudely at the screen&rsquo;s edge, by using also
<b>--atblanks</b>.) (The old short option, <b>-$</b>, is
deprecated.)</p>
<p style="margin-left:11%;"><b>-T&nbsp;</b><i>number</i>,
<b>--tabsize=</b><i>number</i></p>
<p style="margin-left:22%;">Set the size (width) of a tab
to <i>number</i> columns. The value of <i>number</i> must be
greater than 0. The default value is <b>8</b>.</p>
<p style="margin-left:11%;"><b>-U</b>,
<b>--quickblank</b></p>
<p style="margin-left:22%;">Make status-bar messages
disappear after 1 keystroke instead of after 20. Note that
option <b>-c</b> (<b>--constantshow</b>) overrides this.
When option <b>--minibar</b> or <b>--zero</b> is in effect,
<b>--quickblank</b> makes a message disappear after 0.8
seconds instead of after the default 1.5 seconds.</p>
<p style="margin-left:11%;"><b>-V</b>, <b>--version</b></p>
<p style="margin-left:22%;">Show the current version number
and exit.</p>
<p style="margin-left:11%;"><b>-W</b>,
<b>--wordbounds</b></p>
<p style="margin-left:22%;">Detect word boundaries
differently by treating punctuation characters as part of a
word.</p>
<p style="margin-left:11%;"><b>-X
&quot;</b><i>characters</i><b>&quot;</b>,
<b>--wordchars=&quot;</b><i>characters</i><b>&quot;</b></p>
<p style="margin-left:22%;">Specify which other characters
(besides the normal alphanumeric ones) should be considered
as part of a word. When using this option, you probably want
to omit <b>-W</b> (<b>--wordbounds</b>).</p>
<p style="margin-left:11%;"><b>-Y&nbsp;</b><i>name</i>,
<b>--syntax=</b><i>name</i></p>
<p style="margin-left:22%;">Specify the name of the syntax
highlighting to use from among the ones defined in the
<i>nanorc</i> files.</p>
<p style="margin-left:11%;"><b>-Z</b>, <b>--zap</b></p>
<p style="margin-left:22%;">Let an unmodified Backspace or
Delete erase the marked region (instead of a single
character, and without affecting the cutbuffer).</p>
<p style="margin-left:11%;"><b>-a</b>,
<b>--atblanks</b></p>
<p style="margin-left:22%;">When doing soft line wrapping,
wrap lines at whitespace instead of always at the edge of
the screen.</p>
<p style="margin-left:11%;"><b>-b</b>,
<b>--breaklonglines</b></p>
<p style="margin-left:22%;">Automatically hard-wrap the
current line when it becomes overlong. (This option is the
opposite of <b>-w</b> (<b>--nowrap</b>) -- the last one
given takes effect.)</p>
<p style="margin-left:11%;"><b>-c</b>,
<b>--constantshow</b></p>
<p style="margin-left:22%;">Constantly show the cursor
position on the status bar. Note that this overrides option
<b>-U</b> (<b>--quickblank</b>).</p>
<p style="margin-left:11%;"><b>-d</b>,
<b>--rebinddelete</b></p>
<p style="margin-left:22%;">Interpret the Delete and
Backspace keys differently so that both Backspace and Delete
work properly. You should only use this option when on your
system either Backspace acts like Delete or Delete acts like
Backspace.</p>
<p style="margin-left:11%;"><b>-e</b>,
<b>--emptyline</b></p>
<p style="margin-left:22%;">Do not use the line below the
title bar, leaving it entirely blank.</p>
<p style="margin-left:11%;"><b>-f&nbsp;</b><i>file</i>,
<b>--rcfile=</b><i>file</i></p>
<p style="margin-left:22%;">Read only this <i>file</i> for
setting nano&rsquo;s options, instead of reading both the
system-wide and the user&rsquo;s nanorc files.</p>
<p style="margin-left:11%;"><b>-g</b>,
<b>--showcursor</b></p>
<p style="margin-left:22%;">Make the cursor visible in the
file browser (putting it on the highlighted item) and in the
help viewer. Useful for braille users and people with poor
vision.</p>
<p style="margin-left:11%;"><b>-h</b>, <b>--help</b></p>
<p style="margin-left:22%;">Show a summary of the available
command-line options and exit.</p>
<p style="margin-left:11%;"><b>-i</b>,
<b>--autoindent</b></p>
<p style="margin-left:22%;">Automatically indent a newly
created line to the same number of tabs and/or spaces as the
previous line (or as the next line if the previous line is
the beginning of a paragraph).</p>
<p style="margin-left:11%;"><b>-j</b>,
<b>--jumpyscrolling</b></p>
<p style="margin-left:22%;">Scroll the buffer contents per
half-screen instead of per line.</p>
<p style="margin-left:11%;"><b>-k</b>,
<b>--cutfromcursor</b></p>
<p style="margin-left:22%;">Make the &rsquo;Cut Text&rsquo;
command (normally <b>^K</b>) cut from the current cursor
position to the end of the line, instead of cutting the
entire line.</p>
<p style="margin-left:11%;"><b>-l</b>,
<b>--linenumbers</b></p>
<p style="margin-left:22%;">Display line numbers to the
left of the text area. (Any line with an anchor additionally
gets a mark in the margin.)</p>
<p style="margin-left:11%;"><b>-m</b>, <b>--mouse</b></p>
<p style="margin-left:22%;">Enable mouse support, if
available for your system. When enabled, mouse clicks can be
used to place the cursor, set the mark (with a double
click), and execute shortcuts. The mouse will work in the X
Window System, and on the console when gpm is running. Text
can still be selected through dragging by holding down the
Shift key.</p>
<p style="margin-left:11%;"><b>-n</b>, <b>--noread</b></p>
<p style="margin-left:22%;">Treat any name given on the
command line as a new file. This allows <b>nano</b> to write
to named pipes: it will start with a blank buffer, and will
write to the pipe when the user saves the &quot;file&quot;.
This way <b>nano</b> can be used as an editor in combination
with for instance <b>gpg</b> without having to write
sensitive data to disk first.</p>
<p style="margin-left:11%;"><b>-o&nbsp;</b><i>directory</i>,
<b>--operatingdir=</b><i>directory</i></p>
<p style="margin-left:22%;">Set the operating directory.
This makes <b>nano</b> set up something similar to a
chroot.</p>
<p style="margin-left:11%;"><b>-p</b>,
<b>--preserve</b></p>
<p style="margin-left:22%;">Preserve the XON and XOFF
sequences (<b>^Q</b> and <b>^S</b>) so they will be caught
by the terminal. Note that option <b>-/</b>
(<b>--modernbindings</b>) overrides this.</p>
<p style="margin-left:11%;"><b>-q</b>,
<b>--indicator</b></p>
<p style="margin-left:22%;">Display a &quot;scrollbar&quot;
on the righthand side of the edit window. It shows the
position of the viewport in the buffer and how much of the
buffer is covered by the viewport.</p>
<p style="margin-left:11%;"><b>-r&nbsp;</b><i>number</i>,
<b>--fill=</b><i>number</i></p>
<p style="margin-left:22%;">Set the target width for
justifying and automatic hard-wrapping at this <i>number</i>
of columns. If the value is 0 or less, wrapping will occur
at the width of the screen minus <i>number</i> columns,
allowing the wrap point to vary along with the width of the
screen if the screen is resized. The default value is
<b>-8</b>.</p>
<p style="margin-left:11%;"><b>-s &quot;</b><i>program</i>
[<i>argument</i> ...]<b>&quot;</b>,
<b>--speller=&quot;</b><i>program</i> [<i>argument</i>
...]<b>&quot;</b></p>
<p style="margin-left:22%;">Use this command to perform
spell checking and correcting, instead of using the built-in
corrector that calls <b>hunspell</b>(1) or
<b>spell</b>(1).</p>
<p style="margin-left:11%;"><b>-t</b>,
<b>--saveonexit</b></p>
<p style="margin-left:22%;">Save a changed buffer without
prompting (when exiting with <b>^X</b>).</p>
<p style="margin-left:11%;"><b>-u</b>, <b>--unix</b></p>
<p style="margin-left:22%;">Save a file by default in Unix
format. This overrides nano&rsquo;s default behavior of
saving a file in the format that it had. (This option has no
effect when you also use <b>--noconvert</b>.)</p>
<p style="margin-left:11%;"><b>-v</b>, <b>--view</b></p>
<p style="margin-left:22%;">Just view the file and disallow
editing: read-only mode. This mode allows the user to open
also other files for viewing, unless <b>--restricted</b> is
given too.</p>
<p style="margin-left:11%;"><b>-w</b>, <b>--nowrap</b></p>
<p style="margin-left:22%;">Do not automatically hard-wrap
the current line when it becomes overlong. This is the
default. (This option is the opposite of <b>-b</b>
(<b>--breaklonglines</b>) -- the last one given takes
effect.)</p>
<p style="margin-left:11%;"><b>-x</b>, <b>--nohelp</b></p>
<p style="margin-left:22%;">Don&rsquo;t show the two help
lines at the bottom of the screen.</p>
<p style="margin-left:11%;"><b>-y</b>,
<b>--afterends</b></p>
<p style="margin-left:22%;">Make Ctrl+Right and Ctrl+Delete
stop at word ends instead of beginnings.</p>
<p style="margin-left:11%;"><b>-!</b>, <b>--magic</b></p>
<p style="margin-left:22%;">When neither the file&rsquo;s
name nor its first line give a clue, try using libmagic to
determine the applicable syntax.</p>
<p style="margin-left:11%;"><b>-%</b>,
<b>--stateflags</b></p>
<p style="margin-left:22%;">Use the top-right corner of the
screen for showing some state flags: <b>I</b> when
auto-indenting, <b>M</b> when the mark is on, <b>L</b> when
hard-wrapping (breaking long lines), <b>R</b> when recording
a macro, and <b>S</b> when soft-wrapping. When the buffer is
modified, a star (<b>*</b>) is shown after the filename in
the center of the title bar.</p>
<p style="margin-left:11%;"><b>-_</b>, <b>--minibar</b></p>
<p style="margin-left:22%;">Suppress the title bar and
instead show information about the current buffer at the
bottom of the screen, in the space for the status bar. In
this &quot;mini bar&quot; the filename is shown on the left,
followed by an asterisk if the buffer has been modified. On
the right are displayed the current line and column number,
the code of the character under the cursor (in Unicode
format: U+xxxx), the same flags as are shown by
<b>--stateflags</b>, and a percentage that expresses how far
the cursor is into the file (linewise). When a file is
loaded or saved, and also when switching between buffers,
the number of lines in the buffer is displayed after the
filename. This number is cleared upon the next keystroke, or
replaced with an [i/n] counter when multiple buffers are
open. The line plus column numbers and the character code
are displayed only when <b>--constantshow</b> is used, and
can be toggled on and off with <b>M-C</b>. The state flags
are displayed only when <b>--stateflags</b> is used.</p>
<p style="margin-left:11%;"><b>-0</b>, <b>--zero</b></p>
<p style="margin-left:22%;">Hide all elements of the
interface (title bar, status bar, and help lines) and use
all rows of the terminal for showing the contents of the
buffer. The status bar appears only when there is a
significant message, and disappears after 1.5 seconds or
upon the next keystroke. With <b>M-Z</b> the title bar plus
status bar can be toggled. With <b>M-X</b> the help
lines.</p>
<p style="margin-left:11%;"><b>-/</b>,
<b>--modernbindings</b></p>
<p style="margin-left:22%;">Use key bindings similar to the
ones that most modern programs use: <b>^X</b> cuts,
<b>^C</b> copies, <b>^V</b> pastes, <b>^Z</b> undoes,
<b>^Y</b> redoes, <b>^F</b> searches forward, <b>^G</b>
searches next, <b>^S</b> saves, <b>^O</b> opens a file,
<b>^Q</b> quits, and (when the terminal permits) <b>^H</b>
shows help. Furthermore, <b>^A</b> sets the mark, <b>^R</b>
makes replacements, <b>^D</b> searches previous, <b>^P</b>
shows the position, <b>^T</b> goes to a line, <b>^W</b>
writes out a file, and <b>^E</b> executes a command. Note
that this overrides option <b>-p</b>
(<b>--preserve</b>).</p>
<h2>TOGGLES
<a name="TOGGLES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Several of the
above options can be switched on and off also while
<b>nano</b> is running. For example, <b>M-L</b> toggles the
hard-wrapping of long lines, <b>M-S</b> toggles
soft-wrapping, <b>M-N</b> toggles line numbers, <b>M-M</b>
toggles the mouse, <b>M-I</b> auto-indentation, and
<b>M-X</b> the help lines. See at the end of the <b>^G</b>
help text for a complete list.</p>
<p style="margin-left:11%; margin-top: 1em">The <b>M-X</b>
toggle is special: it works in all menus except the help
viewer and the linter. All other toggles work in the main
menu only.</p>
<h2>FILES
<a name="FILES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">When
<b>--rcfile</b> is given, <b>nano</b> will read just the
specified file for setting its options and syntaxes and key
bindings. Without that option, <b>nano</b> will read two
configuration files: first the system&rsquo;s <i>nanorc</i>
(if it exists), and then the user&rsquo;s <i>nanorc</i> (if
it exists), either <i>~/.nanorc</i> or
<i>$XDG_CONFIG_HOME/nano/nanorc</i> or
<i>~/.config/nano/nanorc</i>, whichever is encountered
first. See <b>nanorc</b>(5) for more information on the
possible contents of those files.</p>
<p style="margin-left:11%; margin-top: 1em">See
<i>/usr/share/nano/</i> and <i>/usr/share/nano/extra/</i>
for available syntax-coloring definitions.</p>
<h2>NOTES
<a name="NOTES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Option
<b>-z</b> (<b>--suspendable</b>) has been removed.
Suspension is enabled by default, reachable via <b>^T^Z</b>.
(If you want a plain <b>^Z</b> to suspend nano, add <b>bind
^Z suspend main</b> to your nanorc.)</p>
<p style="margin-left:11%; margin-top: 1em">When you want
to copy marked text from <b>nano</b> to the system&rsquo;s
clipboard, see one of the examples in the <b>nanorc</b>(5)
man page.</p>
<p style="margin-left:11%; margin-top: 1em">If no
alternative spell checker command is specified on the
command line nor in one of the <i>nanorc</i> files,
<b>nano</b> will check the <b>SPELL</b> environment variable
for one.</p>
<p style="margin-left:11%; margin-top: 1em">In some cases
<b>nano</b> will try to dump the buffer into an emergency
file. This will happen mainly if <b>nano</b> receives a
SIGHUP or SIGTERM or runs out of memory. It will write the
buffer into a file named <i>nano.save</i> if the buffer
didn&rsquo;t have a name already, or will add a
&quot;.save&quot; suffix to the current filename. If an
emergency file with that name already exists in the current
directory, it will add &quot;.save&quot; plus a number (e.g.
&quot;.save.1&quot;) to the current filename in order to
make it unique. In multibuffer mode, <b>nano</b> will write
all the open buffers to their respective emergency
files.</p>
<p style="margin-left:11%; margin-top: 1em">If you have any
question about how to use <b>nano</b> in some specific
situation, you can ask on <i>help-nano@gnu.org</i>.</p>
<h2>BUGS
<a name="BUGS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The recording
and playback of keyboard macros works correctly only on a
terminal emulator, not on a Linux console (VT), because the
latter does not by default distinguish modified from
unmodified arrow keys.</p>
<p style="margin-left:11%; margin-top: 1em">Please report
any other bugs that you encounter via: <i><br>
https://savannah.gnu.org/bugs/?group=nano</i>.</p>
<p style="margin-left:11%; margin-top: 1em">When nano
crashes, it will save any modified buffers to emergency
.save files. If you are able to reproduce the crash and you
want to get a backtrace, define the environment variable
<b>NANO_NOCATCH</b>.</p>
<h2>HOMEPAGE
<a name="HOMEPAGE"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><i>https://nano-editor.org/</i></p>
<h2>SEE ALSO
<a name="SEE ALSO"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><i><b>nanorc</b></i>(5)</p>
<p style="margin-left:11%; margin-top: 1em"><i>/usr/share/doc/nano/</i>
(or equivalent on your system)</p>
<hr>
</body>
</html>

2442
OGP64/usr/share/doc/nano/html/nano.html Normal file
View file

File diff suppressed because it is too large Load diff

1686
OGP64/usr/share/doc/nano/html/nanorc.5.html Normal file
View file

File diff suppressed because it is too large Load diff

188
OGP64/usr/share/doc/nano/html/rnano.1.html Normal file
View file

@ -0,0 +1,188 @@
<!-- Creator : groff version 1.22.4 -->
<!-- CreationDate: Wed May 1 08:26:02 2024 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="Content-Style" content="text/css">
<style type="text/css">
p { margin-top: 0; margin-bottom: 0; vertical-align: top }
pre { margin-top: 0; margin-bottom: 0; vertical-align: top }
table { margin-top: 0; margin-bottom: 0; vertical-align: top }
h1 { text-align: center }
</style>
<title>RNANO</title>
</head>
<body>
<h1 align="center">RNANO</h1>
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#OPTIONS">OPTIONS</a><br>
<a href="#BUGS">BUGS</a><br>
<a href="#HOMEPAGE">HOMEPAGE</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<hr>
<h2>NAME
<a name="NAME"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">rnano - a
restricted nano</p>
<h2>SYNOPSIS
<a name="SYNOPSIS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>rnano</b>
[<i>options</i>]
[[+<i>line</i>[,<i>column</i>]]&nbsp;<i>file</i>]...</p>
<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>rnano</b>
runs the <b>nano</b> editor in restricted mode. This allows
editing only the specified file or files, and doesn&rsquo;t
allow the user access to the filesystem nor to a command
shell.</p>
<p style="margin-left:11%; margin-top: 1em">In restricted
mode, <b>nano</b> will:</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">
<p>&bull;</p></td>
<td width="2%"></td>
<td width="86%">
<p>not make backups;</p></td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">
<p>&bull;</p></td>
<td width="2%"></td>
<td width="86%">
<p>not allow suspending;</p></td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">
<p>&bull;</p></td>
<td width="2%"></td>
<td width="86%">
<p>not allow spell checking;</p></td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">
<p>&bull;</p></td>
<td width="2%"></td>
<td width="86%">
<p>not read nor write the history files;</p></td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">
<p>&bull;</p></td>
<td width="2%"></td>
<td width="86%">
<p>not allow saving the current buffer under a different
name;</p> </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">
<p>&bull;</p></td>
<td width="2%"></td>
<td width="86%">
<p>not allow inserting another file or opening a new
buffer;</p> </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">
<p>&bull;</p></td>
<td width="2%"></td>
<td width="86%">
<p>not allow appending or prepending to any file.</p></td></tr>
</table>
<h2>OPTIONS
<a name="OPTIONS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>-h</b>,
<b>--help</b></p>
<p style="margin-left:22%;">Show the available command-line
options and exit.</p>
<p style="margin-left:11%; margin-top: 1em">For all
existing options, see the <b>nano</b>(1) man page.</p>
<h2>BUGS
<a name="BUGS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Please report
bugs via
<i>https://savannah.gnu.org/bugs/?group=nano</i>.</p>
<h2>HOMEPAGE
<a name="HOMEPAGE"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><i>https://nano-editor.org/</i></p>
<h2>SEE ALSO
<a name="SEE ALSO"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><i><b>nano</b></i>(1)</p>
<hr>
</body>
</html>