If a command line option that begins with '+' is followed by another option, the former is always treated as a starting line number and the latter is always treated as a filename. If a command line option that begins with '+' isn't followed by another option, it's always treated as a filename. Examples:
+If a command line option that begins with '+' is followed by another option, the former is always treated as a starting line and column number and the latter is always treated as a filename. If a command line option that begins with '+' isn't followed by another option, it's always treated as a filename. Examples:
To open '+filename.txt' starting on line 1: nano +filename.txt
To open '+filename.txt' starting on line 10: nano +10 +filename.txt
+ To open '+filename.txt' starting on line 1, column 20: nano +,20 +filename.txt
+ To open '+filename.txt' starting on line 10, column 20: nano +10,20 +filename.txt
To open '+filename.txt' starting on line 1 and 'filename.txt' starting on line 10 (if nano has been compiled with multibuffer support): nano +1 +filename.txt +20 filename.txt4.2. Ack! My Backspace/Delete/Enter/Meta/double bucky key doesn't seem to work! What can I do?
Try setting your $TERM variable to 'vt100'. nano doesn't yet support every term entry under the sun.
@@ -254,7 +256,8 @@7.5. Can I have CVS write access?
Re-read Section 7.4 and you should know the answer.
8. ChangeLog
-2006/11/25 - Add miscellaneous wording and capitalization fixes. (DLR)
+2007/01/01 - Update section 4.1 to describe how to open files with names beginning with '+' at specified columns as well as lines. (DLR)
+2006/11/25 - Add miscellaneous wording and capitalization fixes. (DLR)
2006/10/28 - Update various links for the 2.0 branch of nano. (DLR)
2006/10/06 - Update the question in section 4.13 to match the version of it in the answer section. (DLR)
2006/07/25 - Update section 5.3 again to not state "the latest development version" before 1.3.12, as it's no longer accurate. Also add some minor spacing fixes. (DLR)