[ { "path": ".github/workflows/fetch.yml", "content": "name: Fetch-upstream\non:\n schedule:\n - cron: '0 0 * * 1'\n workflow_dispatch:\n\njobs:\n fetch:\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v2\n with:\n fetch-depth: '5'\n\n - name: Fetch upstream (dirty hacks)\n run: |\n mv .github .github~ # hide it from git\n git reset --hard HEAD~3\n git pull git://git.savannah.gnu.org/nano.git\n mv .github~ .github\n\n - name: Commit this script\n run: |\n git add .\n git -c user.email='mail@beuke.org' -c user.name='Fabian Beuke' commit \\\n -m 'Merge pull request #9 from davidhcefx/patch-3'\n git push --force\n" }, { "path": ".gitignore", "content": "*~\n*.bak\n*.o\n*.orig\n*.patch\n*.swp\n.deps\n.libs\nMakefile\nMakefile.in\n\ncore\n.gdb_history\n.gdbinit\n\n/src/nano\n/src/revision.h\n\n/ABOUT-NLS\n/INSTALL\n/aclocal.m4\n/ar-lib\n/autom4te.cache\n/compile\n/config.cache\n/config.guess\n/config.h\n/config.h.in\n/config.log\n/config.rpath\n/config.status\n/config.sub\n/configure\n/depcomp\n/install-sh\n/intl\n/missing\n/mkinstalldirs\n/stamp-h1\n\n# Gettext m4 files:\n/m4/codeset.m4\n/m4/extern-inline.m4\n/m4/fcntl-o.m4\n/m4/gettext.m4\n/m4/glibc2.m4\n/m4/glibc21.m4\n/m4/host-cpu-c-abi.m4\n/m4/iconv.m4\n/m4/intdiv0.m4\n/m4/intl.m4\n/m4/intldir.m4\n/m4/intlmacosx.m4\n/m4/intmax.m4\n/m4/inttypes-pri.m4\n/m4/inttypes_h.m4\n/m4/lcmessage.m4\n/m4/lib-ld.m4\n/m4/lib-link.m4\n/m4/lib-prefix.m4\n/m4/lock.m4\n/m4/longlong.m4\n/m4/nls.m4\n/m4/po.m4\n/m4/printf-posix.m4\n/m4/progtest.m4\n/m4/size_max.m4\n/m4/stdint_h.m4\n/m4/threadlib.m4\n/m4/uintmax_t.m4\n/m4/visibility.m4\n/m4/wchar_t.m4\n/m4/wint_t.m4\n/m4/xsize.m4\n\n# Gnulib stuff:\n/gnulib/\n/lib/\n/m4/.gitignore\n/m4/gnulib-cache.m4\n/snippet/\n" }, { "path": "AUTHORS", "content": "This file lists people who have made significant contributions to the\nnano editor. Please see the ChangeLog for specific changes by author.\n----------------------------------------------------------------------\n\nChris Allegretta \n\t* Original program author and long-time maintainer.\n\nBenno Schulenberg \n\t* An array of small bug fixes, the cut-word and block-jump\n\t routines, text selection by holding Shift, macro recording\n\t and replay, extra key bindings, the --indicator, --minibar,\n\t and --zero options, and braced functions in string binds.\n\t Current maintainer.\n\nDavid Lawrence Ramsey \n\t* Multiple-buffer support, operating-dir option (-o), bug fixes\n\t for display routines, wrapping code, spelling fixes, parts of\n\t UTF-8 support, softwrap overhaul, constantshow mode, undoable\n\t indentations, undoable justifications, justifiable regions,\n\t and numerous other fixes. Former stable-series maintainer.\n\nJordi Mallach \n\t* Debian package maintainer, fellow bug squasher, translator\n\t for Catalan. Former head of internationalization support.\n\nAdam Rogoyski \n\t* New write_file() function, read_file() optimization, mouse\n\t support, resize support, nohelp (-x) option, justify function,\n\t follow symlink option and bugfixes, and much more.\n\nRobert Siemborski \n\t* Miscellaneous cut, display, replace, and other bug fixes,\n\t original and new \"magic line\" code, read_line() function,\n\t new edit display routines.\n\nRocco Corsi \n\t* Internal spelling code, many optimizations and bug fixes\n\t for findnextstr() and search-related functions, various\n\t display and file-handling fixes.\n\nDavid Benbennick \n\t* Wrap and justify bugfixes/enhancements, new color syntax\n\t code, memleak fixes, parts of the UTF-8 support, and other\n\t miscellaneous fixes.\n\nMike Frysinger \n\t* Whitespace display mode, --enable-utf8/--disable-utf8 configure\n\t options for ncurses, many new color regexes and improvements to\n\t existing ones in syntax/*.nanorc, the move from svn to git, the\n\t conversion to gnulib, and miscellaneous bug fixes. Former\n\t Gentoo package maintainer.\n\nMark Majeres \n\t* A functional undo/redo system, and coloring nano's interface.\n\nMahyar Abbaspour \n\t* Improved handling of SIGWINCH.\n\nMike Scalora \n\t* The comment/uncomment feature.\n\nFaissal Bensefia \n\t* Line numbers.\n\nSumedh Pendurkar \n\t* The word-completion feature.\n\nRishabh Dave \n\t* Searchable help.\n\nMarco Diego Aurélio Mesquita \n\t* Filtering text through an external command.\n\t* Placing anchors (bookmarks) and jumping to them.\n\nBrand Huntsman \n\t* The delayed parsing of syntax files.\n" }, { "path": "COPYING", "content": "\n\t\t GNU GENERAL PUBLIC LICENSE\n\t\t Version 3, 29 June 2007\n\n Copyright (C) 2007 Free Software Foundation, Inc. \n Everyone is permitted to copy and distribute verbatim copies\n of this license document, but changing it is not allowed.\n\n\t\t\t Preamble\n\n The GNU General Public License is a free, copyleft license for\nsoftware and other kinds of works.\n\n The licenses for most software and other practical works are designed\nto take away your freedom to share and change the works. By contrast,\nthe GNU General Public License is intended to guarantee your freedom to\nshare and change all versions of a program--to make sure it remains free\nsoftware for all its users. We, the Free Software Foundation, use the\nGNU General Public License for most of our software; it applies also to\nany other work released this way by its authors. You can apply it to\nyour programs, too.\n\n When we speak of free software, we are referring to freedom, not\nprice. Our General Public Licenses are designed to make sure that you\nhave the freedom to distribute copies of free software (and charge for\nthem if you wish), that you receive source code or can get it if you\nwant it, that you can change the software or use pieces of it in new\nfree programs, and that you know you can do these things.\n\n To protect your rights, we need to prevent others from denying you\nthese rights or asking you to surrender the rights. Therefore, you have\ncertain responsibilities if you distribute copies of the software, or if\nyou modify it: responsibilities to respect the freedom of others.\n\n For example, if you distribute copies of such a program, whether\ngratis or for a fee, you must pass on to the recipients the same\nfreedoms that you received. You must make sure that they, too, receive\nor can get the source code. And you must show them these terms so they\nknow their rights.\n\n Developers that use the GNU GPL protect your rights with two steps:\n(1) assert copyright on the software, and (2) offer you this License\ngiving you legal permission to copy, distribute and/or modify it.\n\n For the developers' and authors' protection, the GPL clearly explains\nthat there is no warranty for this free software. For both users' and\nauthors' sake, the GPL requires that modified versions be marked as\nchanged, so that their problems will not be attributed erroneously to\nauthors of previous versions.\n\n Some devices are designed to deny users access to install or run\nmodified versions of the software inside them, although the manufacturer\ncan do so. This is fundamentally incompatible with the aim of\nprotecting users' freedom to change the software. The systematic\npattern of such abuse occurs in the area of products for individuals to\nuse, which is precisely where it is most unacceptable. Therefore, we\nhave designed this version of the GPL to prohibit the practice for those\nproducts. If such problems arise substantially in other domains, we\nstand ready to extend this provision to those domains in future versions\nof the GPL, as needed to protect the freedom of users.\n\n Finally, every program is threatened constantly by software patents.\nStates should not allow patents to restrict development and use of\nsoftware on general-purpose computers, but in those that do, we wish to\navoid the special danger that patents applied to a free program could\nmake it effectively proprietary. To prevent this, the GPL assures that\npatents cannot be used to render the program non-free.\n\n The precise terms and conditions for copying, distribution and\nmodification follow.\n\n\t\t TERMS AND CONDITIONS\n\n 0. Definitions.\n\n \"This License\" refers to version 3 of the GNU General Public License.\n\n \"Copyright\" also means copyright-like laws that apply to other kinds of\nworks, such as semiconductor masks.\n \n \"The Program\" refers to any copyrightable work licensed under this\nLicense. Each licensee is addressed as \"you\". \"Licensees\" and\n\"recipients\" may be individuals or organizations.\n\n To \"modify\" a work means to copy from or adapt all or part of the work\nin a fashion requiring copyright permission, other than the making of an\nexact copy. The resulting work is called a \"modified version\" of the\nearlier work or a work \"based on\" the earlier work.\n\n A \"covered work\" means either the unmodified Program or a work based\non the Program.\n\n To \"propagate\" a work means to do anything with it that, without\npermission, would make you directly or secondarily liable for\ninfringement under applicable copyright law, except executing it on a\ncomputer or modifying a private copy. Propagation includes copying,\ndistribution (with or without modification), making available to the\npublic, and in some countries other activities as well.\n\n To \"convey\" a work means any kind of propagation that enables other\nparties to make or receive copies. Mere interaction with a user through\na computer network, with no transfer of a copy, is not conveying.\n\n An interactive user interface displays \"Appropriate Legal Notices\"\nto the extent that it includes a convenient and prominently visible\nfeature that (1) displays an appropriate copyright notice, and (2)\ntells the user that there is no warranty for the work (except to the\nextent that warranties are provided), that licensees may convey the\nwork under this License, and how to view a copy of this License. If\nthe interface presents a list of user commands or options, such as a\nmenu, a prominent item in the list meets this criterion.\n\n 1. Source Code.\n\n The \"source code\" for a work means the preferred form of the work\nfor making modifications to it. \"Object code\" means any non-source\nform of a work.\n\n A \"Standard Interface\" means an interface that either is an official\nstandard defined by a recognized standards body, or, in the case of\ninterfaces specified for a particular programming language, one that\nis widely used among developers working in that language.\n\n The \"System Libraries\" of an executable work include anything, other\nthan the work as a whole, that (a) is included in the normal form of\npackaging a Major Component, but which is not part of that Major\nComponent, and (b) serves only to enable use of the work with that\nMajor Component, or to implement a Standard Interface for which an\nimplementation is available to the public in source code form. A\n\"Major Component\", in this context, means a major essential component\n(kernel, window system, and so on) of the specific operating system\n(if any) on which the executable work runs, or a compiler used to\nproduce the work, or an object code interpreter used to run it.\n\n The \"Corresponding Source\" for a work in object code form means all\nthe source code needed to generate, install, and (for an executable\nwork) run the object code and to modify the work, including scripts to\ncontrol those activities. However, it does not include the work's\nSystem Libraries, or general-purpose tools or generally available free\nprograms which are used unmodified in performing those activities but\nwhich are not part of the work. For example, Corresponding Source\nincludes interface definition files associated with source files for\nthe work, and the source code for shared libraries and dynamically\nlinked subprograms that the work is specifically designed to require,\nsuch as by intimate data communication or control flow between those\nsubprograms and other parts of the work.\n\n The Corresponding Source need not include anything that users\ncan regenerate automatically from other parts of the Corresponding\nSource.\n\n The Corresponding Source for a work in source code form is that\nsame work.\n\n 2. Basic Permissions.\n\n All rights granted under this License are granted for the term of\ncopyright on the Program, and are irrevocable provided the stated\nconditions are met. This License explicitly affirms your unlimited\npermission to run the unmodified Program. The output from running a\ncovered work is covered by this License only if the output, given its\ncontent, constitutes a covered work. This License acknowledges your\nrights of fair use or other equivalent, as provided by copyright law.\n\n You may make, run and propagate covered works that you do not\nconvey, without conditions so long as your license otherwise remains\nin force. You may convey covered works to others for the sole purpose\nof having them make modifications exclusively for you, or provide you\nwith facilities for running those works, provided that you comply with\nthe terms of this License in conveying all material for which you do\nnot control copyright. Those thus making or running the covered works\nfor you must do so exclusively on your behalf, under your direction\nand control, on terms that prohibit them from making any copies of\nyour copyrighted material outside their relationship with you.\n\n Conveying under any other circumstances is permitted solely under\nthe conditions stated below. Sublicensing is not allowed; section 10\nmakes it unnecessary.\n\n 3. Protecting Users' Legal Rights From Anti-Circumvention Law.\n\n No covered work shall be deemed part of an effective technological\nmeasure under any applicable law fulfilling obligations under article\n11 of the WIPO copyright treaty adopted on 20 December 1996, or\nsimilar laws prohibiting or restricting circumvention of such\nmeasures.\n\n When you convey a covered work, you waive any legal power to forbid\ncircumvention of technological measures to the extent such circumvention\nis effected by exercising rights under this License with respect to\nthe covered work, and you disclaim any intention to limit operation or\nmodification of the work as a means of enforcing, against the work's\nusers, your or third parties' legal rights to forbid circumvention of\ntechnological measures.\n\n 4. Conveying Verbatim Copies.\n\n You may convey verbatim copies of the Program's source code as you\nreceive it, in any medium, provided that you conspicuously and\nappropriately publish on each copy an appropriate copyright notice;\nkeep intact all notices stating that this License and any\nnon-permissive terms added in accord with section 7 apply to the code;\nkeep intact all notices of the absence of any warranty; and give all\nrecipients a copy of this License along with the Program.\n\n You may charge any price or no price for each copy that you convey,\nand you may offer support or warranty protection for a fee.\n\n 5. Conveying Modified Source Versions.\n\n You may convey a work based on the Program, or the modifications to\nproduce it from the Program, in the form of source code under the\nterms of section 4, provided that you also meet all of these conditions:\n\n a) The work must carry prominent notices stating that you modified\n it, and giving a relevant date.\n\n b) The work must carry prominent notices stating that it is\n released under this License and any conditions added under section\n 7. This requirement modifies the requirement in section 4 to\n \"keep intact all notices\".\n\n c) You must license the entire work, as a whole, under this\n License to anyone who comes into possession of a copy. This\n License will therefore apply, along with any applicable section 7\n additional terms, to the whole of the work, and all its parts,\n regardless of how they are packaged. This License gives no\n permission to license the work in any other way, but it does not\n invalidate such permission if you have separately received it.\n\n d) If the work has interactive user interfaces, each must display\n Appropriate Legal Notices; however, if the Program has interactive\n interfaces that do not display Appropriate Legal Notices, your\n work need not make them do so.\n\n A compilation of a covered work with other separate and independent\nworks, which are not by their nature extensions of the covered work,\nand which are not combined with it such as to form a larger program,\nin or on a volume of a storage or distribution medium, is called an\n\"aggregate\" if the compilation and its resulting copyright are not\nused to limit the access or legal rights of the compilation's users\nbeyond what the individual works permit. Inclusion of a covered work\nin an aggregate does not cause this License to apply to the other\nparts of the aggregate.\n\n 6. Conveying Non-Source Forms.\n\n You may convey a covered work in object code form under the terms\nof sections 4 and 5, provided that you also convey the\nmachine-readable Corresponding Source under the terms of this License,\nin one of these ways:\n\n a) Convey the object code in, or embodied in, a physical product\n (including a physical distribution medium), accompanied by the\n Corresponding Source fixed on a durable physical medium\n customarily used for software interchange.\n\n b) Convey the object code in, or embodied in, a physical product\n (including a physical distribution medium), accompanied by a\n written offer, valid for at least three years and valid for as\n long as you offer spare parts or customer support for that product\n model, to give anyone who possesses the object code either (1) a\n copy of the Corresponding Source for all the software in the\n product that is covered by this License, on a durable physical\n medium customarily used for software interchange, for a price no\n more than your reasonable cost of physically performing this\n conveying of source, or (2) access to copy the\n Corresponding Source from a network server at no charge.\n\n c) Convey individual copies of the object code with a copy of the\n written offer to provide the Corresponding Source. This\n alternative is allowed only occasionally and noncommercially, and\n only if you received the object code with such an offer, in accord\n with subsection 6b.\n\n d) Convey the object code by offering access from a designated\n place (gratis or for a charge), and offer equivalent access to the\n Corresponding Source in the same way through the same place at no\n further charge. You need not require recipients to copy the\n Corresponding Source along with the object code. If the place to\n copy the object code is a network server, the Corresponding Source\n may be on a different server (operated by you or a third party)\n that supports equivalent copying facilities, provided you maintain\n clear directions next to the object code saying where to find the\n Corresponding Source. Regardless of what server hosts the\n Corresponding Source, you remain obligated to ensure that it is\n available for as long as needed to satisfy these requirements.\n\n e) Convey the object code using peer-to-peer transmission, provided\n you inform other peers where the object code and Corresponding\n Source of the work are being offered to the general public at no\n charge under subsection 6d.\n\n A separable portion of the object code, whose source code is excluded\nfrom the Corresponding Source as a System Library, need not be\nincluded in conveying the object code work.\n\n A \"User Product\" is either (1) a \"consumer product\", which means any\ntangible personal property which is normally used for personal, family,\nor household purposes, or (2) anything designed or sold for incorporation\ninto a dwelling. In determining whether a product is a consumer product,\ndoubtful cases shall be resolved in favor of coverage. For a particular\nproduct received by a particular user, \"normally used\" refers to a\ntypical or common use of that class of product, regardless of the status\nof the particular user or of the way in which the particular user\nactually uses, or expects or is expected to use, the product. A product\nis a consumer product regardless of whether the product has substantial\ncommercial, industrial or non-consumer uses, unless such uses represent\nthe only significant mode of use of the product.\n\n \"Installation Information\" for a User Product means any methods,\nprocedures, authorization keys, or other information required to install\nand execute modified versions of a covered work in that User Product from\na modified version of its Corresponding Source. The information must\nsuffice to ensure that the continued functioning of the modified object\ncode is in no case prevented or interfered with solely because\nmodification has been made.\n\n If you convey an object code work under this section in, or with, or\nspecifically for use in, a User Product, and the conveying occurs as\npart of a transaction in which the right of possession and use of the\nUser Product is transferred to the recipient in perpetuity or for a\nfixed term (regardless of how the transaction is characterized), the\nCorresponding Source conveyed under this section must be accompanied\nby the Installation Information. But this requirement does not apply\nif neither you nor any third party retains the ability to install\nmodified object code on the User Product (for example, the work has\nbeen installed in ROM).\n\n The requirement to provide Installation Information does not include a\nrequirement to continue to provide support service, warranty, or updates\nfor a work that has been modified or installed by the recipient, or for\nthe User Product in which it has been modified or installed. Access to a\nnetwork may be denied when the modification itself materially and\nadversely affects the operation of the network or violates the rules and\nprotocols for communication across the network.\n\n Corresponding Source conveyed, and Installation Information provided,\nin accord with this section must be in a format that is publicly\ndocumented (and with an implementation available to the public in\nsource code form), and must require no special password or key for\nunpacking, reading or copying.\n\n 7. Additional Terms.\n\n \"Additional permissions\" are terms that supplement the terms of this\nLicense by making exceptions from one or more of its conditions.\nAdditional permissions that are applicable to the entire Program shall\nbe treated as though they were included in this License, to the extent\nthat they are valid under applicable law. If additional permissions\napply only to part of the Program, that part may be used separately\nunder those permissions, but the entire Program remains governed by\nthis License without regard to the additional permissions.\n\n When you convey a copy of a covered work, you may at your option\nremove any additional permissions from that copy, or from any part of\nit. (Additional permissions may be written to require their own\nremoval in certain cases when you modify the work.) You may place\nadditional permissions on material, added by you to a covered work,\nfor which you have or can give appropriate copyright permission.\n\n Notwithstanding any other provision of this License, for material you\nadd to a covered work, you may (if authorized by the copyright holders of\nthat material) supplement the terms of this License with terms:\n\n a) Disclaiming warranty or limiting liability differently from the\n terms of sections 15 and 16 of this License; or\n\n b) Requiring preservation of specified reasonable legal notices or\n author attributions in that material or in the Appropriate Legal\n Notices displayed by works containing it; or\n\n c) Prohibiting misrepresentation of the origin of that material, or\n requiring that modified versions of such material be marked in\n reasonable ways as different from the original version; or\n\n d) Limiting the use for publicity purposes of names of licensors or\n authors of the material; or\n\n e) Declining to grant rights under trademark law for use of some\n trade names, trademarks, or service marks; or\n\n f) Requiring indemnification of licensors and authors of that\n material by anyone who conveys the material (or modified versions of\n it) with contractual assumptions of liability to the recipient, for\n any liability that these contractual assumptions directly impose on\n those licensors and authors.\n\n All other non-permissive additional terms are considered \"further\nrestrictions\" within the meaning of section 10. If the Program as you\nreceived it, or any part of it, contains a notice stating that it is\ngoverned by this License along with a term that is a further\nrestriction, you may remove that term. If a license document contains\na further restriction but permits relicensing or conveying under this\nLicense, you may add to a covered work material governed by the terms\nof that license document, provided that the further restriction does\nnot survive such relicensing or conveying.\n\n If you add terms to a covered work in accord with this section, you\nmust place, in the relevant source files, a statement of the\nadditional terms that apply to those files, or a notice indicating\nwhere to find the applicable terms.\n\n Additional terms, permissive or non-permissive, may be stated in the\nform of a separately written license, or stated as exceptions;\nthe above requirements apply either way.\n\n 8. Termination.\n\n You may not propagate or modify a covered work except as expressly\nprovided under this License. Any attempt otherwise to propagate or\nmodify it is void, and will automatically terminate your rights under\nthis License (including any patent licenses granted under the third\nparagraph of section 11).\n\n However, if you cease all violation of this License, then your\nlicense from a particular copyright holder is reinstated (a)\nprovisionally, unless and until the copyright holder explicitly and\nfinally terminates your license, and (b) permanently, if the copyright\nholder fails to notify you of the violation by some reasonable means\nprior to 60 days after the cessation.\n\n Moreover, your license from a particular copyright holder is\nreinstated permanently if the copyright holder notifies you of the\nviolation by some reasonable means, this is the first time you have\nreceived notice of violation of this License (for any work) from that\ncopyright holder, and you cure the violation prior to 30 days after\nyour receipt of the notice.\n\n Termination of your rights under this section does not terminate the\nlicenses of parties who have received copies or rights from you under\nthis License. If your rights have been terminated and not permanently\nreinstated, you do not qualify to receive new licenses for the same\nmaterial under section 10.\n\n 9. Acceptance Not Required for Having Copies.\n\n You are not required to accept this License in order to receive or\nrun a copy of the Program. Ancillary propagation of a covered work\noccurring solely as a consequence of using peer-to-peer transmission\nto receive a copy likewise does not require acceptance. However,\nnothing other than this License grants you permission to propagate or\nmodify any covered work. These actions infringe copyright if you do\nnot accept this License. Therefore, by modifying or propagating a\ncovered work, you indicate your acceptance of this License to do so.\n\n 10. Automatic Licensing of Downstream Recipients.\n\n Each time you convey a covered work, the recipient automatically\nreceives a license from the original licensors, to run, modify and\npropagate that work, subject to this License. You are not responsible\nfor enforcing compliance by third parties with this License.\n\n An \"entity transaction\" is a transaction transferring control of an\norganization, or substantially all assets of one, or subdividing an\norganization, or merging organizations. If propagation of a covered\nwork results from an entity transaction, each party to that\ntransaction who receives a copy of the work also receives whatever\nlicenses to the work the party's predecessor in interest had or could\ngive under the previous paragraph, plus a right to possession of the\nCorresponding Source of the work from the predecessor in interest, if\nthe predecessor has it or can get it with reasonable efforts.\n\n You may not impose any further restrictions on the exercise of the\nrights granted or affirmed under this License. For example, you may\nnot impose a license fee, royalty, or other charge for exercise of\nrights granted under this License, and you may not initiate litigation\n(including a cross-claim or counterclaim in a lawsuit) alleging that\nany patent claim is infringed by making, using, selling, offering for\nsale, or importing the Program or any portion of it.\n\n 11. Patents.\n\n A \"contributor\" is a copyright holder who authorizes use under this\nLicense of the Program or a work on which the Program is based. The\nwork thus licensed is called the contributor's \"contributor version\".\n\n A contributor's \"essential patent claims\" are all patent claims\nowned or controlled by the contributor, whether already acquired or\nhereafter acquired, that would be infringed by some manner, permitted\nby this License, of making, using, or selling its contributor version,\nbut do not include claims that would be infringed only as a\nconsequence of further modification of the contributor version. For\npurposes of this definition, \"control\" includes the right to grant\npatent sublicenses in a manner consistent with the requirements of\nthis License.\n\n Each contributor grants you a non-exclusive, worldwide, royalty-free\npatent license under the contributor's essential patent claims, to\nmake, use, sell, offer for sale, import and otherwise run, modify and\npropagate the contents of its contributor version.\n\n In the following three paragraphs, a \"patent license\" is any express\nagreement or commitment, however denominated, not to enforce a patent\n(such as an express permission to practice a patent or covenant not to\nsue for patent infringement). To \"grant\" such a patent license to a\nparty means to make such an agreement or commitment not to enforce a\npatent against the party.\n\n If you convey a covered work, knowingly relying on a patent license,\nand the Corresponding Source of the work is not available for anyone\nto copy, free of charge and under the terms of this License, through a\npublicly available network server or other readily accessible means,\nthen you must either (1) cause the Corresponding Source to be so\navailable, or (2) arrange to deprive yourself of the benefit of the\npatent license for this particular work, or (3) arrange, in a manner\nconsistent with the requirements of this License, to extend the patent\nlicense to downstream recipients. \"Knowingly relying\" means you have\nactual knowledge that, but for the patent license, your conveying the\ncovered work in a country, or your recipient's use of the covered work\nin a country, would infringe one or more identifiable patents in that\ncountry that you have reason to believe are valid.\n \n If, pursuant to or in connection with a single transaction or\narrangement, you convey, or propagate by procuring conveyance of, a\ncovered work, and grant a patent license to some of the parties\nreceiving the covered work authorizing them to use, propagate, modify\nor convey a specific copy of the covered work, then the patent license\nyou grant is automatically extended to all recipients of the covered\nwork and works based on it.\n\n A patent license is \"discriminatory\" if it does not include within\nthe scope of its coverage, prohibits the exercise of, or is\nconditioned on the non-exercise of one or more of the rights that are\nspecifically granted under this License. You may not convey a covered\nwork if you are a party to an arrangement with a third party that is\nin the business of distributing software, under which you make payment\nto the third party based on the extent of your activity of conveying\nthe work, and under which the third party grants, to any of the\nparties who would receive the covered work from you, a discriminatory\npatent license (a) in connection with copies of the covered work\nconveyed by you (or copies made from those copies), or (b) primarily\nfor and in connection with specific products or compilations that\ncontain the covered work, unless you entered into that arrangement,\nor that patent license was granted, prior to 28 March 2007.\n\n Nothing in this License shall be construed as excluding or limiting\nany implied license or other defenses to infringement that may\notherwise be available to you under applicable patent law.\n\n 12. No Surrender of Others' Freedom.\n\n If conditions are imposed on you (whether by court order, agreement or\notherwise) that contradict the conditions of this License, they do not\nexcuse you from the conditions of this License. If you cannot convey a\ncovered work so as to satisfy simultaneously your obligations under this\nLicense and any other pertinent obligations, then as a consequence you may\nnot convey it at all. For example, if you agree to terms that obligate you\nto collect a royalty for further conveying from those to whom you convey\nthe Program, the only way you could satisfy both those terms and this\nLicense would be to refrain entirely from conveying the Program.\n\n 13. Use with the GNU Affero General Public License.\n\n Notwithstanding any other provision of this License, you have\npermission to link or combine any covered work with a work licensed\nunder version 3 of the GNU Affero General Public License into a single\ncombined work, and to convey the resulting work. The terms of this\nLicense will continue to apply to the part which is the covered work,\nbut the special requirements of the GNU Affero General Public License,\nsection 13, concerning interaction through a network will apply to the\ncombination as such.\n\n 14. Revised Versions of this License.\n\n The Free Software Foundation may publish revised and/or new versions of\nthe GNU General Public License from time to time. Such new versions will\nbe similar in spirit to the present version, but may differ in detail to\naddress new problems or concerns.\n\n Each version is given a distinguishing version number. If the\nProgram specifies that a certain numbered version of the GNU General\nPublic License \"or any later version\" applies to it, you have the\noption of following the terms and conditions either of that numbered\nversion or of any later version published by the Free Software\nFoundation. If the Program does not specify a version number of the\nGNU General Public License, you may choose any version ever published\nby the Free Software Foundation.\n\n If the Program specifies that a proxy can decide which future\nversions of the GNU General Public License can be used, that proxy's\npublic statement of acceptance of a version permanently authorizes you\nto choose that version for the Program.\n\n Later license versions may give you additional or different\npermissions. However, no additional obligations are imposed on any\nauthor or copyright holder as a result of your choosing to follow a\nlater version.\n\n 15. Disclaimer of Warranty.\n\n THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY\nAPPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT\nHOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY\nOF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,\nTHE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR\nPURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM\nIS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF\nALL NECESSARY SERVICING, REPAIR OR CORRECTION.\n\n 16. Limitation of Liability.\n\n IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING\nWILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS\nTHE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY\nGENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE\nUSE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF\nDATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD\nPARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),\nEVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF\nSUCH DAMAGES.\n\n 17. Interpretation of Sections 15 and 16.\n\n If the disclaimer of warranty and limitation of liability provided\nabove cannot be given local legal effect according to their terms,\nreviewing courts shall apply local law that most closely approximates\nan absolute waiver of all civil liability in connection with the\nProgram, unless a warranty or assumption of liability accompanies a\ncopy of the Program in return for a fee.\n\n\t\t END OF TERMS AND CONDITIONS\n\n\t How to Apply These Terms to Your New Programs\n\n If you develop a new program, and you want it to be of the greatest\npossible use to the public, the best way to achieve this is to make it\nfree software which everyone can redistribute and change under these terms.\n\n To do so, attach the following notices to the program. It is safest\nto attach them to the start of each source file to most effectively\nstate the exclusion of warranty; and each file should have at least\nthe \"copyright\" line and a pointer to where the full notice is found.\n\n \n Copyright (C) \n\n This program is free software: you can redistribute it and/or modify\n it under the terms of the GNU General Public License as published by\n the Free Software Foundation, either version 3 of the License, or\n (at your option) any later version.\n\n This program is distributed in the hope that it will be useful,\n but WITHOUT ANY WARRANTY; without even the implied warranty of\n MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n GNU General Public License for more details.\n\n You should have received a copy of the GNU General Public License\n along with this program. If not, see .\n\nAlso add information on how to contact you by electronic and paper mail.\n\n If the program does terminal interaction, make it output a short\nnotice like this when it starts in an interactive mode:\n\n Copyright (C) \n This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n This is free software, and you are welcome to redistribute it\n under certain conditions; type `show c' for details.\n\nThe hypothetical commands `show w' and `show c' should show the appropriate\nparts of the General Public License. Of course, your program's commands\nmight be different; for a GUI interface, you would use an \"about box\".\n\n You should also get your employer (if you work as a programmer) or school,\nif any, to sign a \"copyright disclaimer\" for the program, if necessary.\nFor more information on this, and how to apply and follow the GNU GPL, see\n.\n\n The GNU General Public License does not permit incorporating your program\ninto proprietary programs. If your program is a subroutine library, you\nmay consider it more useful to permit linking proprietary applications with\nthe library. If this is what you want to do, use the GNU Lesser General\nPublic License instead of this License. But first, please read\n.\n\n" }, { "path": "COPYING.DOC", "content": "\t\tGNU Free Documentation License\n\t\t Version 1.2, November 2002\n\n\n Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.\n 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA\n Everyone is permitted to copy and distribute verbatim copies\n of this license document, but changing it is not allowed.\n\n\n0. PREAMBLE\n\nThe purpose of this License is to make a manual, textbook, or other\nfunctional and useful document \"free\" in the sense of freedom: to\nassure everyone the effective freedom to copy and redistribute it,\nwith or without modifying it, either commercially or noncommercially.\nSecondarily, this License preserves for the author and publisher a way\nto get credit for their work, while not being considered responsible\nfor modifications made by others.\n\nThis License is a kind of \"copyleft\", which means that derivative\nworks of the document must themselves be free in the same sense. It\ncomplements the GNU General Public License, which is a copyleft\nlicense designed for free software.\n\nWe have designed this License in order to use it for manuals for free\nsoftware, because free software needs free documentation: a free\nprogram should come with manuals providing the same freedoms that the\nsoftware does. But this License is not limited to software manuals;\nit can be used for any textual work, regardless of subject matter or\nwhether it is published as a printed book. We recommend this License\nprincipally for works whose purpose is instruction or reference.\n\n\n1. APPLICABILITY AND DEFINITIONS\n\nThis License applies to any manual or other work, in any medium, that\ncontains a notice placed by the copyright holder saying it can be\ndistributed under the terms of this License. Such a notice grants a\nworld-wide, royalty-free license, unlimited in duration, to use that\nwork under the conditions stated herein. The \"Document\", below,\nrefers to any such manual or work. Any member of the public is a\nlicensee, and is addressed as \"you\". You accept the license if you\ncopy, modify or distribute the work in a way requiring permission\nunder copyright law.\n\nA \"Modified Version\" of the Document means any work containing the\nDocument or a portion of it, either copied verbatim, or with\nmodifications and/or translated into another language.\n\nA \"Secondary Section\" is a named appendix or a front-matter section of\nthe Document that deals exclusively with the relationship of the\npublishers or authors of the Document to the Document's overall subject\n(or to related matters) and contains nothing that could fall directly\nwithin that overall subject. (Thus, if the Document is in part a\ntextbook of mathematics, a Secondary Section may not explain any\nmathematics.) The relationship could be a matter of historical\nconnection with the subject or with related matters, or of legal,\ncommercial, philosophical, ethical or political position regarding\nthem.\n\nThe \"Invariant Sections\" are certain Secondary Sections whose titles\nare designated, as being those of Invariant Sections, in the notice\nthat says that the Document is released under this License. If a\nsection does not fit the above definition of Secondary then it is not\nallowed to be designated as Invariant. The Document may contain zero\nInvariant Sections. If the Document does not identify any Invariant\nSections then there are none.\n\nThe \"Cover Texts\" are certain short passages of text that are listed,\nas Front-Cover Texts or Back-Cover Texts, in the notice that says that\nthe Document is released under this License. A Front-Cover Text may\nbe at most 5 words, and a Back-Cover Text may be at most 25 words.\n\nA \"Transparent\" copy of the Document means a machine-readable copy,\nrepresented in a format whose specification is available to the\ngeneral public, that is suitable for revising the document\nstraightforwardly with generic text editors or (for images composed of\npixels) generic paint programs or (for drawings) some widely available\ndrawing editor, and that is suitable for input to text formatters or\nfor automatic translation to a variety of formats suitable for input\nto text formatters. A copy made in an otherwise Transparent file\nformat whose markup, or absence of markup, has been arranged to thwart\nor discourage subsequent modification by readers is not Transparent.\nAn image format is not Transparent if used for any substantial amount\nof text. A copy that is not \"Transparent\" is called \"Opaque\".\n\nExamples of suitable formats for Transparent copies include plain\nASCII without markup, Texinfo input format, LaTeX input format, SGML\nor XML using a publicly available DTD, and standard-conforming simple\nHTML, PostScript or PDF designed for human modification. Examples of\ntransparent image formats include PNG, XCF and JPG. Opaque formats\ninclude proprietary formats that can be read and edited only by\nproprietary word processors, SGML or XML for which the DTD and/or\nprocessing tools are not generally available, and the\nmachine-generated HTML, PostScript or PDF produced by some word\nprocessors for output purposes only.\n\nThe \"Title Page\" means, for a printed book, the title page itself,\nplus such following pages as are needed to hold, legibly, the material\nthis License requires to appear in the title page. For works in\nformats which do not have any title page as such, \"Title Page\" means\nthe text near the most prominent appearance of the work's title,\npreceding the beginning of the body of the text.\n\nA section \"Entitled XYZ\" means a named subunit of the Document whose\ntitle either is precisely XYZ or contains XYZ in parentheses following\ntext that translates XYZ in another language. (Here XYZ stands for a\nspecific section name mentioned below, such as \"Acknowledgements\",\n\"Dedications\", \"Endorsements\", or \"History\".) To \"Preserve the Title\"\nof such a section when you modify the Document means that it remains a\nsection \"Entitled XYZ\" according to this definition.\n\nThe Document may include Warranty Disclaimers next to the notice which\nstates that this License applies to the Document. These Warranty\nDisclaimers are considered to be included by reference in this\nLicense, but only as regards disclaiming warranties: any other\nimplication that these Warranty Disclaimers may have is void and has\nno effect on the meaning of this License.\n\n\n2. VERBATIM COPYING\n\nYou may copy and distribute the Document in any medium, either\ncommercially or noncommercially, provided that this License, the\ncopyright notices, and the license notice saying this License applies\nto the Document are reproduced in all copies, and that you add no other\nconditions whatsoever to those of this License. You may not use\ntechnical measures to obstruct or control the reading or further\ncopying of the copies you make or distribute. However, you may accept\ncompensation in exchange for copies. If you distribute a large enough\nnumber of copies you must also follow the conditions in section 3.\n\nYou may also lend copies, under the same conditions stated above, and\nyou may publicly display copies.\n\n\n3. COPYING IN QUANTITY\n\nIf you publish printed copies (or copies in media that commonly have\nprinted covers) of the Document, numbering more than 100, and the\nDocument's license notice requires Cover Texts, you must enclose the\ncopies in covers that carry, clearly and legibly, all these Cover\nTexts: Front-Cover Texts on the front cover, and Back-Cover Texts on\nthe back cover. Both covers must also clearly and legibly identify\nyou as the publisher of these copies. The front cover must present\nthe full title with all words of the title equally prominent and\nvisible. You may add other material on the covers in addition.\nCopying with changes limited to the covers, as long as they preserve\nthe title of the Document and satisfy these conditions, can be treated\nas verbatim copying in other respects.\n\nIf the required texts for either cover are too voluminous to fit\nlegibly, you should put the first ones listed (as many as fit\nreasonably) on the actual cover, and continue the rest onto adjacent\npages.\n\nIf you publish or distribute Opaque copies of the Document numbering\nmore than 100, you must either include a machine-readable Transparent\ncopy along with each Opaque copy, or state in or with each Opaque copy\na computer-network location from which the general network-using\npublic has access to download using public-standard network protocols\na complete Transparent copy of the Document, free of added material.\nIf you use the latter option, you must take reasonably prudent steps,\nwhen you begin distribution of Opaque copies in quantity, to ensure\nthat this Transparent copy will remain thus accessible at the stated\nlocation until at least one year after the last time you distribute an\nOpaque copy (directly or through your agents or retailers) of that\nedition to the public.\n\nIt is requested, but not required, that you contact the authors of the\nDocument well before redistributing any large number of copies, to give\nthem a chance to provide you with an updated version of the Document.\n\n\n4. MODIFICATIONS\n\nYou may copy and distribute a Modified Version of the Document under\nthe conditions of sections 2 and 3 above, provided that you release\nthe Modified Version under precisely this License, with the Modified\nVersion filling the role of the Document, thus licensing distribution\nand modification of the Modified Version to whoever possesses a copy\nof it. In addition, you must do these things in the Modified Version:\n\nA. Use in the Title Page (and on the covers, if any) a title distinct\n from that of the Document, and from those of previous versions\n (which should, if there were any, be listed in the History section\n of the Document). You may use the same title as a previous version\n if the original publisher of that version gives permission.\nB. List on the Title Page, as authors, one or more persons or entities\n responsible for authorship of the modifications in the Modified\n Version, together with at least five of the principal authors of the\n Document (all of its principal authors, if it has fewer than five),\n unless they release you from this requirement.\nC. State on the Title page the name of the publisher of the\n Modified Version, as the publisher.\nD. Preserve all the copyright notices of the Document.\nE. Add an appropriate copyright notice for your modifications\n adjacent to the other copyright notices.\nF. Include, immediately after the copyright notices, a license notice\n giving the public permission to use the Modified Version under the\n terms of this License, in the form shown in the Addendum below.\nG. Preserve in that license notice the full lists of Invariant Sections\n and required Cover Texts given in the Document's license notice.\nH. Include an unaltered copy of this License.\nI. Preserve the section Entitled \"History\", Preserve its Title, and add\n to it an item stating at least the title, year, new authors, and\n publisher of the Modified Version as given on the Title Page. If\n there is no section Entitled \"History\" in the Document, create one\n stating the title, year, authors, and publisher of the Document as\n given on its Title Page, then add an item describing the Modified\n Version as stated in the previous sentence.\nJ. Preserve the network location, if any, given in the Document for\n public access to a Transparent copy of the Document, and likewise\n the network locations given in the Document for previous versions\n it was based on. These may be placed in the \"History\" section.\n You may omit a network location for a work that was published at\n least four years before the Document itself, or if the original\n publisher of the version it refers to gives permission.\nK. For any section Entitled \"Acknowledgements\" or \"Dedications\",\n Preserve the Title of the section, and preserve in the section all\n the substance and tone of each of the contributor acknowledgements\n and/or dedications given therein.\nL. Preserve all the Invariant Sections of the Document,\n unaltered in their text and in their titles. Section numbers\n or the equivalent are not considered part of the section titles.\nM. Delete any section Entitled \"Endorsements\". Such a section\n may not be included in the Modified Version.\nN. Do not retitle any existing section to be Entitled \"Endorsements\"\n or to conflict in title with any Invariant Section.\nO. Preserve any Warranty Disclaimers.\n\nIf the Modified Version includes new front-matter sections or\nappendices that qualify as Secondary Sections and contain no material\ncopied from the Document, you may at your option designate some or all\nof these sections as invariant. To do this, add their titles to the\nlist of Invariant Sections in the Modified Version's license notice.\nThese titles must be distinct from any other section titles.\n\nYou may add a section Entitled \"Endorsements\", provided it contains\nnothing but endorsements of your Modified Version by various\nparties--for example, statements of peer review or that the text has\nbeen approved by an organization as the authoritative definition of a\nstandard.\n\nYou may add a passage of up to five words as a Front-Cover Text, and a\npassage of up to 25 words as a Back-Cover Text, to the end of the list\nof Cover Texts in the Modified Version. Only one passage of\nFront-Cover Text and one of Back-Cover Text may be added by (or\nthrough arrangements made by) any one entity. If the Document already\nincludes a cover text for the same cover, previously added by you or\nby arrangement made by the same entity you are acting on behalf of,\nyou may not add another; but you may replace the old one, on explicit\npermission from the previous publisher that added the old one.\n\nThe author(s) and publisher(s) of the Document do not by this License\ngive permission to use their names for publicity for or to assert or\nimply endorsement of any Modified Version.\n\n\n5. COMBINING DOCUMENTS\n\nYou may combine the Document with other documents released under this\nLicense, under the terms defined in section 4 above for modified\nversions, provided that you include in the combination all of the\nInvariant Sections of all of the original documents, unmodified, and\nlist them all as Invariant Sections of your combined work in its\nlicense notice, and that you preserve all their Warranty Disclaimers.\n\nThe combined work need only contain one copy of this License, and\nmultiple identical Invariant Sections may be replaced with a single\ncopy. If there are multiple Invariant Sections with the same name but\ndifferent contents, make the title of each such section unique by\nadding at the end of it, in parentheses, the name of the original\nauthor or publisher of that section if known, or else a unique number.\nMake the same adjustment to the section titles in the list of\nInvariant Sections in the license notice of the combined work.\n\nIn the combination, you must combine any sections Entitled \"History\"\nin the various original documents, forming one section Entitled\n\"History\"; likewise combine any sections Entitled \"Acknowledgements\",\nand any sections Entitled \"Dedications\". You must delete all sections\nEntitled \"Endorsements\".\n\n\n6. COLLECTIONS OF DOCUMENTS\n\nYou may make a collection consisting of the Document and other documents\nreleased under this License, and replace the individual copies of this\nLicense in the various documents with a single copy that is included in\nthe collection, provided that you follow the rules of this License for\nverbatim copying of each of the documents in all other respects.\n\nYou may extract a single document from such a collection, and distribute\nit individually under this License, provided you insert a copy of this\nLicense into the extracted document, and follow this License in all\nother respects regarding verbatim copying of that document.\n\n\n7. AGGREGATION WITH INDEPENDENT WORKS\n\nA compilation of the Document or its derivatives with other separate\nand independent documents or works, in or on a volume of a storage or\ndistribution medium, is called an \"aggregate\" if the copyright\nresulting from the compilation is not used to limit the legal rights\nof the compilation's users beyond what the individual works permit.\nWhen the Document is included in an aggregate, this License does not\napply to the other works in the aggregate which are not themselves\nderivative works of the Document.\n\nIf the Cover Text requirement of section 3 is applicable to these\ncopies of the Document, then if the Document is less than one half of\nthe entire aggregate, the Document's Cover Texts may be placed on\ncovers that bracket the Document within the aggregate, or the\nelectronic equivalent of covers if the Document is in electronic form.\nOtherwise they must appear on printed covers that bracket the whole\naggregate.\n\n\n8. TRANSLATION\n\nTranslation is considered a kind of modification, so you may\ndistribute translations of the Document under the terms of section 4.\nReplacing Invariant Sections with translations requires special\npermission from their copyright holders, but you may include\ntranslations of some or all Invariant Sections in addition to the\noriginal versions of these Invariant Sections. You may include a\ntranslation of this License, and all the license notices in the\nDocument, and any Warranty Disclaimers, provided that you also include\nthe original English version of this License and the original versions\nof those notices and disclaimers. In case of a disagreement between\nthe translation and the original version of this License or a notice\nor disclaimer, the original version will prevail.\n\nIf a section in the Document is Entitled \"Acknowledgements\",\n\"Dedications\", or \"History\", the requirement (section 4) to Preserve\nits Title (section 1) will typically require changing the actual\ntitle.\n\n\n9. TERMINATION\n\nYou may not copy, modify, sublicense, or distribute the Document except\nas expressly provided for under this License. Any other attempt to\ncopy, modify, sublicense or distribute the Document is void, and will\nautomatically terminate your rights under this License. However,\nparties who have received copies, or rights, from you under this\nLicense will not have their licenses terminated so long as such\nparties remain in full compliance.\n\n\n10. FUTURE REVISIONS OF THIS LICENSE\n\nThe Free Software Foundation may publish new, revised versions\nof the GNU Free Documentation License from time to time. Such new\nversions will be similar in spirit to the present version, but may\ndiffer in detail to address new problems or concerns. See\nhttp://www.gnu.org/copyleft/.\n\nEach version of the License is given a distinguishing version number.\nIf the Document specifies that a particular numbered version of this\nLicense \"or any later version\" applies to it, you have the option of\nfollowing the terms and conditions either of that specified version or\nof any later version that has been published (not as a draft) by the\nFree Software Foundation. If the Document does not specify a version\nnumber of this License, you may choose any version ever published (not\nas a draft) by the Free Software Foundation.\n\n\nADDENDUM: How to use this License for your documents\n\nTo use this License in a document you have written, include a copy of\nthe License in the document and put the following copyright and\nlicense notices just after the title page:\n\n Copyright (c) YEAR YOUR NAME.\n Permission is granted to copy, distribute and/or modify this document\n under the terms of the GNU Free Documentation License, Version 1.2\n or any later version published by the Free Software Foundation;\n with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.\n A copy of the license is included in the section entitled \"GNU\n Free Documentation License\".\n\nIf you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,\nreplace the \"with...Texts.\" line with this:\n\n with the Invariant Sections being LIST THEIR TITLES, with the\n Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.\n\nIf you have Invariant Sections without Cover Texts, or some other\ncombination of the three, merge those two alternatives to suit the\nsituation.\n\nIf your document contains nontrivial examples of program code, we\nrecommend releasing these examples in parallel under your choice of\nfree software license, such as the GNU General Public License,\nto permit their use in free software.\n" }, { "path": "ChangeLog", "content": "Changes between v8.7 and v9.0:\n------------------------------\n\nBenno Schulenberg (92):\n bindings: assign M-< and M-> to the sideways-scrolling functions\n build: add move.c to the list of files that contain translatable strings\n build: avoid three warnings when compiling against glibc-2.43\n build: exclude whole-window sideways scrolling from the tiny version\n bump version numbers and add a news item for the 9.0 release\n copyright: update the years for significantly changed files\n copyright: update the years for significantly changed files\n copyright: update the years for the FSF\n display: add extra variable, to avoid one-way toggling of SOLO_SIDESCROLL\n display: begin looking for new start matches at the correct place\n display: correct the previous commit -- the -1 is needed when going left\n display: draw the \"<\" marker only if part of the line is onscreen\n display: for narrow windows, fall back to single-line sidescrolling\n display: let option --jumpyscrolling affect also sideways scrolling\n display: put cursor at CUSHION columns from edge when scrolling sideways\n display: redraw the screen also when 'brink' is not what it should be\n display: store `brink` per buffer, to keep the viewport stable\n display: when scrolling sideways, refresh edit window only if mark is on\n docs: add an Exit Status section to the man page and the manual\n docs: add a notice about the changed sideways scrolling behavior\n docs: add a section about the recording and replaying of keyboard macros\n docs: add ^B among the list of keystrokes for --modernbindings\n docs: add notices about the reassignment of the M-< and M-> keystrokes\n docs: adjust the cheatsheet for the new functions and changed bindings\n docs: adjust the description of `scrollright` for the changed behavior\n docs: adjust the description of `scrollright` for the improved behavior\n docs: advise the use of --sysconfdir=/etc when configuring nano\n docs: copy the 8.7.1 news item from the release branch\n docs: document the new bindable `scrollleft` and `scrollright` functions\n docs: document the new --solosidescroll and 'set solosidescroll' options\n docs: explain what \"overlong\" means for --breaklonglines\n docs: in the cheatsheet, place Ctrl+L in the Special movement section\n docs: mention that M-Left, M-Right, M-Up, and M-Down are valid keynames\n docs: reshuffle the --solosidescroll option to match the order in --help\n docs: trim stuff that is more than four years old from the changelog\n docs: use rebindable names M-Up and M-Down instead of Alt+Up and Alt+Down\n feedback: prevent interpretation of %s and similar in a filename\n files: include also the slash when re-adding the filename to the path\n gnulib: update to a recent version, to allow compiling against glibc-2.43\n gnulib: update to its current upstream state\n help: group the sideways scrolling keystrokes with the horizontal movers\n history: create the ~/.local directory with limited access rights\n input: allow `recordmacro` and `runmacro` to continue cuts and copies\n input: prevent also a string bind from breaking a chain of cuts or copies\n input: prevent most toggles from breaking a series of cuts or copies\n mouse: allow clicking before the answer to place cursor at its beginning\n moving: ignore `scrollleft` and `scrollright` when softwrapping\n moving: ignore `scrollleft` and `scrollright` with --solosidescroll too\n moving: make the minimum step for sideways scrolling two cells\n moving: stay in the viewport when stepping to a longer line\n moving: when scrolling sideways, search also upward for a longer line\n new default feature: smooth whole-window sideways scrolling\n new feature: bindable functions for scrolling a tabsize left or right\n new feature: clicking in the scrollbar jumps to the corresponding line\n options: accept --solosidescroll and 'set solosidescroll'\n rcfile: allow rebinding M-Left, M-Right, M-Up, and M-Down\n syntax: elisp: remove file -- something specific to Emacs is not for nano\n syntax: groff, man: colorize also \\\" tail comments and \\# line comments\n syntax: guile: colorize more syntax words and procedure names\n syntax: nanorc: colorize M-Left, M-Right, M-Up, M-Down as valid keynames\n syntax: python: colorize also the `match` and `case` keywords\n syntax: python: require a blank after the keyword `match`\n syntaxes: add a license line to the files created by Mark Oteiza\n tweaks: add a comment for an unclear fragment of code\n tweaks: avoid having to restore the original click coordinates\n tweaks: condense the Python coloring rules, and reword a comment\n tweaks: condense two oververbose comments\n tweaks: correct a comment\n tweaks: correct and simplify the logic from the previous two commits\n tweaks: defend against hypothetical format specifiers\n tweaks: give the three \"debugging\" feedback messages a more unusual color\n tweaks: lowercase subsequent words in section titles, to be less pompous\n tweaks: move a function to a more logical place\n tweaks: no need to be overpolite when giving directions\n tweaks: normalize brace placement after the previous change\n tweaks: reduce the scope of two variables\n tweaks: refer to two renamed gnulib modules with their adjusted names\n tweaks: remove an unneeded parameter from get_mouseinput()\n tweaks: rename a type, away from a double abbreviation\n tweaks: rename a variable, away from a double abbreviation\n tweaks: rename a variable, for contrast, and to be more fitting\n tweaks: rename a variable, to be more fitting\n tweaks: rename a variable, to be more fitting and away from an abbrev\n tweaks: rename a variable whose function has changed over time\n tweaks: rename three functions, to be more accurate\n tweaks: rename two functions, reword some comments, rewrap a line\n tweaks: rename two variables, away from abbreviations\n tweaks: reorder a list of keys, starting with singles, ending with group\n tweaks: replace the three instances of impersonal \"one\" with direct \"you\"\n tweaks: reshuffle or transmute a few lines, to elide an 'if'\n tweaks: slightly adjust a wording\n tweaks: slightly improve three comments in the sample nanorc\n\nCharles Mirabile (1):\n macro: cancel the recording if nothing was entered between start and stop\n\n\nChanges between v8.6 and v8.7:\n------------------------------\n\nBenno Schulenberg (17):\n build: avoid a warning when configured with --disable-multibuffer\n bump version numbers and add a news item for the 8.7 release\n display: regenerate the screen after a resize during a spell check\n display: regenerate the screen only before and after waiting for input\n display: upon resize, redraw the subwindows only when fully initialized\n docs: add example of copy-to-clipboard-with-OSC52 to the sample nanorc\n docs: mention that `execute` can pipe buffer or region to the command\n gnulib: update to its current upstream state\n moving: prevent a negative relative jump from going beyond top of buffer\n new feature: execute a command without capturing the output\n startup: register the handler for SIGWINCH much earlier\n text: when blanking a line due to --autoindent, keep the mark in sync\n tweaks: improve a few comments, drop one, and unwrap some lines\n tweaks: improve the punctuation of one item in the sample nanorc\n tweaks: replace a remaining double dash with a true emdash\n tweaks: reshuffle some #ifdefs, and rename a function\n tweaks: unwrap three lines, for esthetics\n\n\nChanges between v8.5 and v8.6:\n------------------------------\n\nBenno Schulenberg (22):\n browser: let a refresh also reread the file list, like it used to\n browser: redo the layout only when an actual resize occurred\n browser: redo the layout when the window _might_ have resized\n bump version numbers and add a news item for the 8.6 release\n completion: don't stop looking for candidates one byte too early\n display: when resizing, redraw the bottom bars also when in file browser\n docs: document the ++/-- prefix feature for the `gotoline` function\n gnulib: update to its current upstream state\n history: do not forget anchors when line number is given on command line\n new feature: interpret a line number prefixed with ++ or -- as relative\n rcfile: accept also {}} in a string bind, for symmetry with {{}\n syntax: po: colorize also the %b and %B format specifiers\n tweaks: normalize the indentation after the previous change\n tweaks: put two related checks together, like they are elsewhere\n tweaks: remove a check for a symbol that never gets defined\n tweaks: rename a parameter, and invert its logic\n tweaks: reshuffle a condition to a better place, like it is elsewhere\n tweaks: reshuffle a few lines, for density and to elide an 'else'\n tweaks: reshuffle some lines, to group things better\n tweaks: split the goto function into an interactive and command-line one\n tweaks: swap two symbolic menu names, for giggles\n tweaks: use a direct parameter instead of an intermediary boolean\n\n\nChanges between v8.4 and v8.5:\n------------------------------\n\nBenno Schulenberg (44):\n anchor: change the aspect of any anchor to a dagger (†)\n bindings: always bind ^Q in the WriteOut menu, not only for --saveonexit\n bindings: do not list ^L twice (in main help text and help lines)\n bindings: let ^L just center the cursor, not cycle it -- let M-% cycle it\n bindings: lowercase an ASCII character in a locale-proof manner\n build: fix compilation for config with --enable-tiny --enable-histories\n build: fix compilation when configured with --disable-histories\n build: fix compilation when configured with --disable-utf8\n build: swap two linker arguments, to enable compilation on Cygwin\n bump version numbers and add a news item for the 8.5 release\n docs: add a suggested key combo for wiping all anchors to sample nanorc\n docs: in cheatsheet, equalize the spacing in three consecutive blocks\n docs: mention that --positionlog also saves the positions of anchors\n docs: reword the descriptions of --operatingdir and 'set operatingdir'\n feedback: change the appearance of anchors when they will be saved\n feedback: change the level of a certain message, to show it is special\n feedback: report the setting and removing of an anchor just once\n feedback: show in mini bar the presence of an anchor on the cursor line\n feedback: suppress \"Jumped to anchor\" when line numbers are active\n feedback: suppress \"Removed anchor\" when the mini bar is hidden\n gnulib: pull in the fix for a cross-compilation failure\n gnulib: update to its current upstream state\n history: always save the last cursor position, also for line=1,column=1\n history: always save the positions of any anchors\n history: reverse the order in the file-positions list, to latest first\n menus: reshuffle an item, to avoid truncating its help-line label\n moving: make cycling (M-%) independent from centering (^L)\n new feature: exit with an error status (2) for ^X^Q and ^O^Q\n new feature: save and restore anchors when the first line has an anchor\n options: accept --whitespacedisplay and 'set whitespacedisplay'\n syntax: default: show hard spaces with a lightgrey background\n syntaxes: add a license line to files that were created by Mike Frysinger\n syntaxes: use character classes instead of range expressions\n tweaks: avoid using toupper() and tolower() where easily possible\n tweaks: elide an auxiliary variable that is no longer needed\n tweaks: elide the unneeded passing around of three parameters\n tweaks: elide the unneeded use of an auxiliary function\n tweaks: in the browser, implement M-\\ and M-/ in a slightly denser way\n tweaks: properly tag some keywords in texi doc, instead of using quotes\n tweaks: random unimportant edits here and there\n tweaks: rename 'use_utf8' to 'using_utf8', and make it a global variable\n tweaks: shorten a URL, and update it to use https\n tweaks: use reallocations, instead of new allocations plus frees\n tweaks: use the correct modifier, to avoid a warning on 32-bit machines\n\nPeter Michaux (1):\n build: add the 'm4/host-cpu-c-abi.m4' file to .gitignore\n\n\nChanges between v8.3 and v8.4:\n------------------------------\n\nBenno Schulenberg (40):\n bump version numbers and add a news item for the 8.4 release\n copyright: update the years for the FSF\n docs: add a suggestion to the FAQ on how to configure nano for git\n docs: change two interface colors in the sample nanorc\n docs: improve the description of the `constantshow` bindable function\n docs: in the FAQ, replace an old item with an item about Byte Order Marks\n docs: replace a word that is better not used in the plural\n docs: use proper emdashes instead of double hyphens: \"--\" => \"\\(em\"\n execute: retain what the user typed before a tool was invoked\n feedback: warn when the cursor sits on a Byte Order Mark (BOM)\n gnulib: update to its current upstream state\n input: adjust file browser and help viewer for changed bracketed pastes\n input: implement bracketed pastes in a different manner\n input: make bracketed paste more robust against loss of closing sequence\n input: remove a special-case workaround\n input: remove single-keycode detection from the bracketed-paste routine\n input: robustness is good, but dropping a key code is not a good idea\n input: wait a bit for \"~\" when bracketed-paste sequence is incomplete\n prompt: accept tabs in an external paste as literal tabs\n prompt: beep when an external paste contains a command code\n syntax: groff: highlight the zeroeth macro argument too\n syntax: man: highlight some escapes, like \\& and \\(em, specially\n syntax: po: colorize also a 'msgctxt' line, and the 'c++-format' flag\n syntax: po: colorize also format specifiers like \"%.6f\"\n syntax: po: colorize also format specifiers like \"%\"\n syntax: po: colorize also Python's \"%(name)x\" format specifiers\n syntax: po: colorize also the %llu and %hhi format specifiers\n syntax: po: colorize also the Python-specific conversion specifier \"%r\"\n tweaks: add a translator hint for the three changed file-writing prompts\n tweaks: add missing closing quotes, as reported by `mandoc -T lint ...`\n tweaks: avoid running tolower() on an out-of-range value\n tweaks: change the man-page markup of options that take an argument\n tweaks: condense a fragment of code\n tweaks: consistently use \"\\fR\" for switching back to normal, roman font\n tweaks: prevent some color keywords from getting hyphenated in man page\n tweaks: prevent some more keywords from getting hyphenated\n tweaks: remove an unwanted newline from a debugging message\n tweaks: remove three redundant pairs of parentheses from a nanorc regex\n tweaks: remove two commented-out lines and two unused variables\n tweaks: swap two fragments of code, to allow unwrapping a line\n\nBrand Huntsman (1):\n files: improve the wording of the normal file-writing prompts\n\n\nChanges between v8.2 and v8.3:\n------------------------------\n\nBenno Schulenberg (16):\n build: fix a compilation error with gcc-15\n bump version numbers and add a news item for the 8.3 release\n docs: add Shift+PgUp/PgDown to the FAQ item about urxvt modified keys\n docs: clarify the possible effects of a misuse of braced function names\n docs: put a space after \"|\" and before \"{enter}\" in the sample nanorc\n gnulib: update to its current upstream state\n syntax: groff: correct the mistaken .rof extension to .roff\n syntax: groff: recognize also the .mom extension\n syntax: makefile: colorize also multiple targets\n syntax: markdown: accept also digit 0 in a list marker\n syntax: spec: colorize all canonical architecture names\n tweaks: add a small clarifying comment\n tweaks: add a translator hint\n tweaks: adjust another translator hint, and add two more\n tweaks: adjust a translator hint, and add another one\n tweaks: drop six unneeded casts\n\nLIU Hao (1):\n syntax: asm: add end-of-word anchors to the keywords\n\nLukáš Zaoral (1):\n memory: avoid a leak when linter aborts after producing parsable output\n\n\nChanges between v8.1 and v8.2:\n------------------------------\n\nBenno Schulenberg (22):\n bindings: at a Yes-No-All prompt, accept also ^A for \"All\"\n bindings: let the central numpad key (with Ctrl) center the current line\n bump version numbers and add a news item for the 8.2 release\n docs: do not quote the argument of 'include' statements in sample nanorc\n docs: mention former maintainership last among an author's contributions\n docs: mention the availability of ^Y, ^N, and ^A at a Yes-No prompt\n docs: trim stuff that is more than four years old from the changelog\n gnulib: update to its current upstream state\n macro: insert it in keystroke buffer without discarding latter's contents\n moving: for Alt+Home/Alt+End, refresh the screen when the mark is on\n syntax: autoconf: colorize the keywords 'case', 'esac', and 'ifelse' too\n syntax: awk: add a missing \"|\" between \"\\?\" and \":\"\n syntax: awk: colorize escape sequences specially\n syntax: awk: rewrite a regex more densely, and add the missing ~ operator\n syntax: man: colorize also the .MT .ME .EX .EE .SY .OP and .YS macros\n syntax: nanorc: an unquoted argument of 'include' may not contain blanks\n tweaks: delete three redundant checks from the undo/redo code\n tweaks: improve or rewrap six comments, and add two missing ones\n tweaks: move a condition to the only place that needs it\n tweaks: rename a symbol, away from an obscure abbreviation\n tweaks: reshuffle a seldom-used function to the end of an if-else series\n tweaks: unwrap three lines that don't need to be wrapped\n\nCollin Funk (1):\n build: update a symbol that was renamed in gnulib\n\n\nChanges between v8.0 and v8.1:\n------------------------------\n\nBenno Schulenberg (56):\n bindings: let ^L put the cursor line at center, then top, then bottom\n build: check for the correct function in an #ifdef\n build: require version 0.20 of gettext for building nano from git\n build: use the standard `autoreconf` invocation\n bump version numbers and add a news item for the 8.1 release\n docs: add 'set colonparsing' to the sample nanorc\n docs: add the Alt+Home/Alt+End shortcuts to the cheatsheet\n docs: avert hyphenation of the technical words \"ncurses\" and \"terminfo\"\n docs: correct the description of --bold, as function tags are unaffected\n docs: document the new --listsyntaxes (-z) option\n docs: don't say any more that -z was removed, as it has been repurposed\n docs: explain the behavior of the new function `cycle`\n docs: explain the details of --colonparsing / -@ / 'set colonparsing'\n docs: extend the FAQ item about urxvt modified keys, with M-Home/M-End\n docs: properly escape a literal '@' in the texi document\n docs: remove the 'filename:linenumber' format from the synopsis\n files: avoid mistakenly setting the column number to a given line number\n files: look for digits and colons starting from the end of the filename\n files: when a filename with a colon and digits exists, open that file\n files: with --rectrict, prevent invoking the browser and toggling backups\n general: disable the type-ahead checking that ncurses normally does\n gnulib: update to its current upstream state\n help: regroup the `center` item, placing it with the new `cycle`\n help: show option -Y/--syntax in --help output also in restricted mode\n input: drop recognition of the urxvt escape sequences for M-Home/M-End\n input: make sure that a string-bind return value is non-negative\n input: provide for urxvt setting a high bit or sending an extra escape\n input: recognize the raw Xterm escape sequences for Alt+Home and Alt+End\n minibar: do not falsely report that a new, empty file is in Mac format\n moving: use edit_scroll() only when scrolling one row is enough\n new feature: add bindable function `cycle` that pushes cursor line around\n new feature: option -z lists the names of available syntaxes\n options: remove the deprecated synonym -$ of -S/--softwrap\n options: require --colonparsing/-@ to parse colon+number after a filename\n rcfile: remove old bindable function 'nowrap', alias of 'breaklonglines'\n startup: do not activate --modernbindings when name starts with \"e\"\n syntaxes: mention the original author of most of the syntax files\n syntax: man: colorize some of the things that manipulate hyphenation\n syntax: patch: recognize also the .rej extension\n text: do not check for + mark while getting input but in do_tab()\n tweaks: add a space after a '+', for consistent formatting\n tweaks: discard a bracketed paste in the help viewer with fewer beeps\n tweaks: drop two redundant conditions\n tweaks: elide unhelpful occurrences of the word \"will\"\n tweaks: exclude the colon-parsing code from the tiny version\n tweaks: extend the deprecation period of 'set nowrap' and prefix 'bright'\n tweaks: implement do_center() with a single call instead of three\n tweaks: in FAQ, use 'id' attribute instead of empty anchor with 'name'\n tweaks: make a comment more accurate, and unabbreviate a variable name\n tweaks: make the inclusion condition for do_center() more strict\n tweaks: remove the now unneeded special keycode INDENT_KEY\n tweaks: reshuffle a declaration, adjust a comment, normalize indentation\n tweaks: reshuffle some lines, to put vaguely related things together\n tweaks: rewrap some lines, for more even lengths\n tweaks: simplify a condition, to match the same condition five lines back\n tweaks: slightly reword a phrase in the explanation of --colonparsing\n\nJaroslav Fowkes (1):\n syntax: fortran: fix a typo (a missing backslash)\n\n\nChanges between v7.2 and v8.0:\n------------------------------\n\nAndy Koppe (2):\n input: scroll on mousewheel events instead of moving the cursor\n rcfile: map the gray #rgb codes (#111 to #EEE) to the xterm grayscale\n\nBenjamin Valentin (1):\n new feature: interpret also : when opening a file\n\nBenno Schulenberg (155):\n bindings: allow speller and friends to be rebound also in restricted mode\n bindings: in the tiny version, bind M-6 only in main, not at the prompts\n bindings: let move the cursor to top/bottom of viewport\n bindings: let M-\" place/remove an anchor, and let M-' jump to one\n bindings: let M-& show the ncurses version+patch, as a small Easter egg\n bindings: make ^F start a forward search by default\n bindings: make ^F start a forward search by default\n bindings: set up modern bindings also when binary's name starts with \"e\"\n bindings: show ^- instead of ^/ for 'flipgoto' when on a Linux console\n bindings: with --modern, do not let ^Q^Q quit nano without saving\n bindings: with --modern, use ^H for Help when the terminal allows it\n browser: report an error instead of crashing when the folder disappears\n browser: restore typing position at prompt after \"^R name ^T ^F ^V ^C\"\n bump version numbers and add a news item for the 8.0 release\n chars: add a helper function for stripping leading blanks from a string\n copyright: update the years for the FSF\n display: add a wnoutrefresh() call for NetBSD, to force a cursor update\n display: do not attempt to draw a line that is outside the viewport\n display: draw a new magic line rightaway when there are multiline regexes\n display: show the help lines down to the tiniest possible terminal size\n docs: add a caveat in the FAQ about bracketed pastes\n docs: add a clarifying note to the description of --tabstospaces\n docs: add an example binding for normalizing Unicode to the sample nanorc\n docs: add a reference to the 'help-nano' mailing list\n docs: add M-C and M-Z to the cheatsheet, and reshuffle for balance\n docs: add ^T^S (spell check) and M-S (softwrap) to the cheatsheet\n docs: add two examples of custom key bindings to the nanorc manpage\n docs: adjust an example help line in the README to the current state\n docs: adjust the cheatsheet for the changed meanings of ^F, ^B, M-F, M-B\n docs: clarify that a fileregex is matched against the absolute filename\n docs: delete a remark about libvte that is no longer relevant\n docs: describe nano more specifically as a text editor\n docs: document the : thing for cursor positioning\n docs: document the new bindable functions 'toprow' and 'bottomrow'\n docs: document the new --modernbindings option\n docs: fix a ten-year-old typo, reported by `correctmost`\n docs: improve the description of the 'flipexecute' bindable function\n docs: in a synopsis, use braces around a choice of required parts\n docs: in the sample nanorc, set the guidestripe to a soft grey\n docs: mention backreferences (for replacements with regular expressions)\n docs: mention how to get the old behavior of ^F, ^B, M-F, and M-B back\n docs: mention that a restricted nano does not access the history files\n docs: mention that 'light' background colors do not work on Linux console\n docs: mention that --modernbindings overrides --preserve\n docs: mention the changed meanings of ^F/^B and also in the texi manual\n docs: mention the missing two options that override --bold\n docs: say \"mini bar\", not \"minibar\", when referring to the actual bar\n docs: trim stuff that is more than five years old from the changelog\n docs: use a space after #, like everywhere else in the sample nanorc\n editing: adjust the mark before trimming redundant blanks\n execute: show \"Older\" and \"Newer\" in the help lines, to allow rebinding\n feedback: drop an unnecessary warning, to not bother the user\n feedback: lowercase a letter, as the phrase is not a full sentence\n feedback: raise the level of \"Macro is empty\", to match similar messages\n feedback: suppress filename and linecount when --zero is active\n feedback: suppress format-conversion messages for --zero and --mini\n files: do not allow M-U to remove text read from standard input\n files: run `chmod` and `chown` on the descriptor, not on the filename\n formatter: do not crash when the formatter command is empty\n general: include the Copy function (M-6 or ^C) into the tiny version\n general: let the constant-show toggle override the zero-interface mode\n gnulib: update to current upstream state, to make a fresh checkout work\n gnulib: update to its current upstream state\n help: give the \"Replace with\" prompt its own help text\n help: mention M-Home and M-End in the help text and help lines\n help: rebalance the help items when --preserve is used\n help: restore ^H and ^D as the primary shortcuts for Backspace and Delete\n help: show ^F/^B as primary shortcuts for search, not as secondary\n indicator: do not oversize the scroller when softwrapping\n input: avoid hanging after a 39-character paste on a VSCode terminal\n input: flush the keystroke buffer upon any kind of error condition\n input: for one bump of the mousewheel scroll two lines, not three\n input: intercept a spurious keycode and say what the actual problem is\n input: let the handler of string binds return a byte whenever possible\n input: neutralize two spurious keycodes from VTE terminals\n input: prevent 'macro_length' from underflowing when hammering M-:\n input: recognize certain escape sequences for F13 to F16 again\n input: snip the `recordmacro` and `runmacro` keystrokes in a better way\n input: store key codes in the macro buffer as they come in from ncurses\n input: store keystroke in macro buffer only when about to interpret it [reverted]\n justify: keep as much of the marked region onscreen as possible\n justify: keep the cursor at the original end of a marked region\n justify: recompute the multidata for paragraphs larger than the viewport\n justify: set the correct starting point also with --cutfromcursor\n justify: set `x = 0` for the undo item, for when using --cutfromcursor\n linter: do not mess up the input stream when the linter command is empty\n linter: use a format string, to deflect format-string attacks\n memory: prevent a leak by freeing a possibly already existing color combo\n minibar: mention the file format when it's DOS or Mac\n moving: preserve horizontal position when jumping to top or bottom row\n new feature: functions that jump to the top or bottom of the viewport\n new feature: option --modernbindings sets up more widespread key bindings\n options: make --modernbindings actually override --preserve\n rcfile: add bindable functions for moving the cursor to top or bottom row\n rcfile: avoid crashing on an include path that is way too long\n replacing: stash the string to be replaced while asking for replacement\n revert the previous commit -- forget about -? as a synonym for --help\n screen: recalculate the multidata when detecting the need for it\n search: avoid a crash after a nested search, reported by `correctmost`\n search: avoid crashing after searching a help text during a regex replace\n shutdown: ignore a modified buffer when in view mode\n softwrap: adjust start-of-screen when the 'edittop' line is hard-wrapped\n softwrap: realign start-of-screen when redoing an automatic hard-wrap\n softwrap: remember the actual breaking point when wrapping at blanks\n startup: use a format string, to deflect format-string attacks\n syntax: c: require a preceding blank when a line comment contains a quote\n syntax: javascript: recognize also the .mjs extension\n syntax: makefile: ensure that the key always produces a tab\n syntax: makefile, sh: recognize also a fresh Makefile and fresh .profile\n syntax: nanorc: colorize {toprow} and {bottomrow} for string binds\n syntax: sh: recognize more shells than `sh` on a shebang line for busybox\n tweaks: add a comment that refers to the VTE spurious-code issue\n tweaks: add a missing 'type' attribute to a \n\n\n\n\n

The GNU nano editor FAQ

\n

Table of Contents

\n

1. General

\n

\n 1.1. What is GNU nano?
\n 1.2. What is the history behind nano?
\n 1.3. Why the name change from TIP?
\n 1.4. What is the current version of nano?
\n 1.5. I want to read the manpage without having to download the program!\n

\n

2. Where to get GNU nano.

\n

\n 2.1. FTP and WWW sites that carry nano.
\n 2.2. RedHat and derivatives (.rpm) packages.
\n 2.3. Debian (.deb) packages.
\n 2.4. By git (for the brave).\n

\n

3. Installation and Configuration

\n

\n 3.1. How do I install the RPM or DEB package?
\n 3.2. Compiling from source: WHAT THE HECK DO I DO NOW?
\n 3.3. Why does everything go into /usr/local?
\n 3.4. nano should automatically run strip on the binary when installing it!
\n 3.5. How can I make the executable smaller? This is too bloated!
\n 3.6. Tell me more about this multibuffer stuff!
\n 3.7. Tell me more about this verbatim input stuff!
\n 3.8. How do I make a .nanorc file that nano will read when I start it?
\n 3.9. Why does my self-compiled nano not read /etc/nanorc?
\n

\n

4. Running

\n

\n 4.1. Alt+Up does nothing on a Linux console. How can I make it scroll?
\n 4.2. How can I make Ctrl+Shift+Left/Right select words on urxvt?
\n 4.3. How do I remove an unwanted Byte Order Mark?
\n 4.4. With what keystroke can I paste text from the clipboard into nano?
\n 4.5. How do I select text for or paste text from the clipboard when nano's mouse support is turned on?
\n 4.6. When I paste text into a document, each line gets indented further than the last. Why? And how can I stop this?
\n 4.7. When I paste from Windows into a remote nano, nano rewraps the lines. What gives?
\n 4.8. I've compiled nano with color support, but I don't see any color when I run it!
\n 4.9. How do I make nano my default editor (in Pine, mutt, git, ...)?
\n

\n

5. Internationalization

\n

\n 5.1. There's no translation for my language!
\n 5.2. I don't like the translation for <x> in my language. How can I fix it?
\n 5.3. What is the status of Unicode support?\n

\n

6. Advocacy and Licensing

\n

\n 6.1. Why should I use nano instead of Pico?
\n 6.2. Why should I use Pico instead of nano?
\n 6.3. What is so bad about the older Pine license?
\n 6.4. Okay, well, what mail program should I use then?\n

\n

7. Miscellaneous

\n

\n 7.1. Where can I ask questions or send suggestions?
\n 7.2. How do I submit a bug report or patch?
\n 7.3. I want to send the development team a big load of cash (or just a thank you).
\n 7.4. How do I join the development team?
\n 7.5. Can I have write access to the git tree?\n

\n
\n\n

1. General

\n

1.1. What is GNU nano?

\n

GNU nano was designed to be a free replacement for the Pico text editor, part of the Pine email suite from The University of Washington. It aimed to "emulate Pico as closely as is reasonable and then include extra functionality".

\n

1.2. What is the history behind nano?

\n

Funny you should ask!

\n

In the beginning...

\n

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.

\n

Then came Debian...

\n

The Debian GNU/Linux distribution, known for its strict standards in distributing truly "free" 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 GNU sense of the word.

\n

The event...

\n

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.

\n

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.

\n

In February 2001, nano was declared an official GNU program by Richard Stallman. nano also reached its first production release on March 22, 2001.

\n

1.3. Why the name change from TIP?

\n

On January 10, 2000, TIP was officially renamed to nano because of a namespace conflict with another program called 'tip'. The original 'tip' program "establishes a full duplex terminal connection to a remote host", 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).

\n

1.4. What is the current version of nano?

\n

The current version of nano should be 9.0. Of course, you should always check the nano homepage to see what the latest and greatest version is.

\n

1.5. I want to read the man page without having to download the program!

\n

Jeez, demanding, aren't we? Okay, look here.

\n
\n\n

2. Where to get GNU nano.

\n

2.1. Web sites that carry nano.

\n

The nano source tarballs can be downloaded from the following web sites:

\n \n
\n

2.2. RPM packages (RedHat, OpenSuse, and derivatives).

\n
\n \n
\n

2.3. Deb packages (Debian and derivatives):

\n

Debian users can check out the current nano packages for:

\n \n

You can also have a look at the Package Pool to see all the available binary and source packages.

\n
\n

2.4. By git (for the brave).

\n

For the \"bleeding edge\" current version of nano, you can use git to download the current source code. Note: 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 the hacking document for info on getting and building nano from git.

\n
\n\n

3. Installation and Configuration

\n

3.1. How do I install the RPM or DEB package?

\n

It's simple really! As root, type rpm -Uvh nano-x.y-1*.rpm if you have a RedHat-ish system or dpkg -i nano_x.y-1*.deb if you have a Debian-ish system, where x.y is the version number of nano. There are other programs to install packages, and if you wish to use those, knock yourself out.

\n

3.2. Compiling from source: WHAT THE HECK DO I DO NOW?

\n

Okay, take a deep breath, this really isn't hard. Unpack the nano source with a command like:

\n

tar -xvf nano-x.y.tar.gz

\n

Then you need to run configure with any options you might want (if any).

\n

The average case is this:

\n

cd nano-x.y/
\n ./configure
\n make
\n make install   #(as root, of course)

\n

3.3. Why does everything go into /usr/local?

\n

Well, that's what the configure script defaults to. If you wish to change this, simply do this:

\n

./configure --prefix=/usr

\n

This will put nano into /usr/bin when you run make install.

\n

3.4. nano should automatically run strip on the binary when installing it!

\n

It does when you use make install-strip. The default make install does not, and will not, run strip automatically.

\n

3.5. How can I make the executable smaller? This is too bloated!

\n

Actually, there are several parts of the editor that can be disabled. You can pass arguments to the configure script that disable certain features. Here's a brief list:

\n 
\n    --disable-browser       Disable the built-in file browser\n    --disable-color         Disable color and syntax highlighting\n    --disable-comment       Disable the comment/uncomment function\n    --disable-extra         Disable the easter egg\n    --disable-formatter     Disable the formatting tool\n    --disable-help          Disable the built-in help texts\n    --disable-histories     Disable the saving of search strings and cursor positions\n    --disable-justify       Disable the justify/unjustify functions\n    --disable-libmagic      Disable the use of libmagic for determining a file's syntax\n    --disable-linenumbers   Disable line numbering\n    --disable-linter        Disable the linting tool\n    --disable-mouse         Disable mouse support\n    --disable-multibuffer   Disable the opening of multiple file buffers\n    --disable-nanorc        Disable the use of .nanorc files\n    --disable-operatingdir  Disable the setting of an operating directory\n    --disable-speller       Disable the spell-checking tool\n    --disable-tabcomp       Disable the tab-completion functions\n    --disable-wordcomp      Disable the word-completion function\n    --disable-wrapping      Disable all hard-wrapping of text
\n

There's also the --enable-tiny 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 --disable-nls to disable internationalization and save a few kilobytes. And finally, there's always good old strip to remove all unneeded symbols.

\n
\n

3.6. Tell me more about this multibuffer stuff!

\n

To use multiple file buffers, you must not have configured nano with --disable-multibuffer nor with --enable-tiny (use nano -V 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 Meta-F after typing ^R. If you always want files to be loaded into their own buffers, use the -F or --multibuffer flag when you invoke nano, or add set multibuffer to your .nanorc file.

\n

You can move between the buffers you have open with the Meta-< and Meta-> keys, or more easily without holding Shift: Meta-, and Meta-. (clear as mud, right? =-). When you have more than one buffer open, the ^X shortcut will say "Close", instead of "Exit".

\n

3.7. Tell me more about this verbatim input stuff!

\n

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 Meta-V (if you're not at a prompt, you'll get the message "Verbatim Input" on the status bar), then press the key(s) that generate the character you want.

\n

Alternatively, if Unicode support is enabled (see section 5.3), you can press Meta-V 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 "Unicode Input: ......" when you do this.

\n

3.8. How do I make a .nanorc file that will be read when I start nano?

\n

It's not hard at all! Simply copy the sample.nanorc from the doc/ directory in the nano source package (or from /usr/doc/nano on your system) to .nanorc 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 set and unset followed by the long option name of the feature (see man nanorc for the full list of options). For example, "set quickblank" or "set smarthome". Of course, for this to work, your nano must not have been compiled with --disable-nanorc.

\n

3.9. Why does my self-compiled nano not read /etc/nanorc?

\n

By default (see 3.3), nano gets installed into /usr/local. This also means that, at startup, nano reads /usr/local/etc/nanorc instead of /etc/nanorc. 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 simply configure your nano with --sysconfdir=/etc.

\n
\n\n

4. Running

\n

4.1. Alt+Up does nothing on a Linux console. How can I make it scroll?

\n

On Debian and its derivatives, the Alt+Up keystroke on a Linux console\n produces by default a 'KeyboardSignal', which normally does absolutely nothing and is useless\n for the average user. To get the keystroke to do what it ought to do (scroll the viewport\n one row up), run this in a Linux console:

\n

dumpkeys --full | sed s/KeyboardSignal/Up/ | sudo loadkeys -

\n

You will need to run this command whenever you first switch to a Linux console.

\n

Or you can (as root) execute the following little script just once:

\n

for file in /etc/console-setup/cached*.kmap.gz; do
\n     gunzip $file;
\n     sed -i 's/KeyboardSignal/Up/' ${file%.gz};
\n     gzip ${file%.gz};
\n done

\n

4.2. How can I make Ctrl+Shift+Left/Right select words on urxvt?

\n

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:

\n
\n    URxvt.iso14755_52: False\n\n    URxvt.keysym.C-S-Up: \\033[1;6A\n    URxvt.keysym.C-S-Down: \\033[1;6B\n    URxvt.keysym.C-S-Right: \\033[1;6C\n    URxvt.keysym.C-S-Left: \\033[1;6D\n\n    URxvt.keysym.M-Up: \\033[1;3A\n    URxvt.keysym.M-Down: \\033[1;3B\n    URxvt.keysym.M-Right: \\033[1;3C\n    URxvt.keysym.M-Left: \\033[1;3D\n\n    URxvt.keysym.M-Home: \\033[1;3H\n    URxvt.keysym.M-End: \\033[1;3F\n\n    URxvt.keysym.M-Insert: \\033[2;3~\n    URxvt.keysym.M-Delete: \\033[3;3~\n\n    URxvt.keysym.M-Page_Up: \\033[5;3~\n    URxvt.keysym.M-Page_Down: \\033[6;3~\n    URxvt.keysym.S-Page_Up: \\033[5;2~\n    URxvt.keysym.S-Page_Down: \\033[6;2~
\n

Then run xrdb ~/.Xresources and restart your urxvt terminal. Now Ctrl+Shift+Left and Ctrl+Shift+Right will select words, Alt+Up and Alt+Down will scroll the text without moving the cursor, and several such things more.

\n

4.3. How do I remove an unwanted Byte Order Mark?

\n

To check whether a file contains a Byte Order Mark (BOM), open the file and type Ctrl+Home. If there is a BOM, the status bar will tell you so. Now type Delete to remove the BOM, and ^S to save the file.

\n

If you've accidentally deleted a Byte Order Mark from a file that needs it, and you want to restore it, then type: Ctrl+Home Alt+V feff Enter. Verify that the BOM is back with Ctrl+Home, and save the file with ^S. (Note that on Unix, files should not contain a BOM.)

\n

4.4. With what keystroke can I paste text from the clipboard into nano?

\n

In most desktop environments Shift+Insert pastes the contents of the clipboard.

\n

4.5. How do I select text for or paste text from the clipboard when nano's mouse support is turned on?

\n

Try holding down the Shift key and selecting or pasting the text as you normally would.

\n

4.6. When I paste text into a document, each line gets indented further than the last. Why? And how can I stop this?

\n

You have the autoindent feature turned on. Hit Meta-I to turn it off, paste your text, and then hit Meta-I again to turn it back on.

\n

Update: Since version 4.8, nano suppresses auto-indentation during a paste (when your terminal understands bracketed pastes), so you no longer need to toggle it off and on manually.

\n

4.7. When I paste from Windows into a remote nano, nano rewraps the lines. What gives?

\n

When pasting from Windows, in some situations linefeeds are sent instead of carriage returns (Enters). And linefeeds are ^Js, 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: unbind ^J main or bind ^J enter main, depending on whether the paste contains CR + LF or only LF.

\n

Update: Since version 4.8, nano ignores linefeed characters in a paste (when your terminal understands bracketed pastes), so you no longer need the above workaround.

\n

4.8. I've compiled nano with color support, but I don't see any color when I run it!

\n

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 syntax/ subdirectory of the nano source, which are normally installed to /usr/local/share/nano/. To enable all of them, uncomment the line # include \"/usr/local/share/nano/*.nanorc\" in your nanorc. See also section 3.9.

\n

4.9. How do I make nano my default editor (in Pine, mutt, git, ...)?

\n

You need to make nano your $EDITOR. If you want this to be saved, you should put a line like this in your .bashrc if you use bash (or .zshrc if you believe in zsh):

\n

export EDITOR=/usr/local/bin/nano

\n

Change /usr/local/bin/nano to wherever nano is installed on your system. Type "which nano" to find out. This will not take effect until the next time you log in. So log out and back in again.

\n

Then, on top of that, if you use Pine, you must go into setup (type S at the main menu), and then configure (type C). Hit Enter on the lines that say:

\n

[ ] enable-alternate-editor-cmd
\n [ ] enable-alternate-editor-implicitly

\n

Then exit (E) and select Yes (Y).

\n

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 .muttrc:

\n

my_hdr X-Composer: nano-x.y

\n

Again, replace x.y with the version of nano you use.

\n

To use nano to edit your git commit messages, you can run:

\n

git config --global core.editor \"nano --guide=74 --nohelp +1\"

\n

Note the +1 at the end — it makes nano start always at the top of the edit window. The guidestripe helps you keep the text within a reasonable width.

\n
\n\n

5. Internationalization

\n

5.1. There's no translation for my language!

\n

In June 2001, GNU nano entered the Translation Project and since then, translations should be managed from there.

\n

If there isn't a translation for your language, you could ask your language team 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 translation disclaimer to the FSF (this is necessary as nano is an official GNU package, but it does not mean that you transfer the rights of your work to the FSF, it's just so the FSF can legally manage them).

\n

In any case, translating nano is easy. Just grab the latest nano.pot file listed on nano's page at the TP, and translate each msgid line into your native language on the msgstr line. When you're done, you should send it to the TP's central PO-file repository.

\n

5.2. I don't like the translation for <x> in my language. How can I fix it?

\n

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 Language-Team: field in the relevant PO file. The team leader or the assigned translator can then make the changes reach the nano-devel list.

\n

5.3. What is the status of Unicode support?

\n

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.

\n
\n\n

6. Advocacy and Licensing

\n

6.1. Why should I use nano instead of Pico?

\n

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.

\n

6.2. Why should I use Pico instead of nano?

\n

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.

\n

6.3. What is so bad about the older Pine license?

\n

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 Debian Free Software Guidelines. 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.

\n

6.4. Okay, well, what mail program should I use then?

\n

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 mutt. 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.

\n

Of course, due to the license change you can now use the Alpine distribution of PINE as it is now considered Free Software, but you would be sacrificing many of nano's features to do so.

\n
\n\n

7. Miscellaneous

\n

7.1. Where can I ask questions or send suggestions?

\n

There are three mailing lists for nano hosted at Savannah: 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:

\n

info-nano - https://lists.gnu.org/mailman/listinfo/info-nano/
\n help-nano - https://lists.gnu.org/mailman/listinfo/help-nano/
\n nano-devel - https://lists.gnu.org/mailman/listinfo/nano-devel/

\n

7.3. How do I submit a bug report or patch?

\n
\n

The best way to submit bugs is through the Savannah bug tracker, 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.\n

You can submit patches for nano via Savannah's patch manager.

\n

7.3. I want to send the development team a big load of cash (or just a thank you).

\n

That's fine. Send it our way! Better yet, fix a bug in the program or implement a cool feature and send us that instead (though cash is fine too).

\n

7.4. How do I join the development team?

\n

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.

\n

7.5. Can I have write access to the git tree?

\n

Re-read section 7.4 and you should know the answer.

\n
\n\n\n\n" }, { "path": "doc/nano.1", "content": ".\\\" Copyright (C) 1999-2011, 2013-2026 Free Software Foundation, Inc.\n.\\\"\n.\\\" This document is dual-licensed. You may distribute and/or modify it\n.\\\" under the terms of either of the following licenses:\n.\\\"\n.\\\" * The GNU General Public License, as published by the Free Software\n.\\\" Foundation, version 3 or (at your option) any later version. You\n.\\\" should have received a copy of the GNU General Public License\n.\\\" along with this program. If not, see\n.\\\" .\n.\\\"\n.\\\" * The GNU Free Documentation License, as published by the Free\n.\\\" Software Foundation, version 1.2 or (at your option) any later\n.\\\" version, with no Invariant Sections, no Front-Cover Texts, and no\n.\\\" Back-Cover Texts. You should have received a copy of the GNU Free\n.\\\" Documentation License along with this program. If not, see\n.\\\" .\n.\\\"\n.TH NANO 1 \"April 2026\" \"GNU nano 9.0\"\n\n.SH NAME\nnano \\- Nano's ANOther text editor, inspired by Pico\n\n.SH SYNOPSIS\n.B nano\n.RI [ options \"] [[\\fB+\" line [\\fB, column \"]] \" file ]...\n.sp\n.BR nano \" [\" \\fIoptions \"] [[\" + [ crCR ]{ / | ? } \\fIstring \"] \" \\fIfile ]...\n\n.SH NOTICES\nSince version 9.0, all lines are scrolled horizontally together\n(when the cursor approaches the edge), by just the amount needed,\ninstead of scrolling only the current line by a large step.\nIf you prefer the old behavior, you can use \\fB\\-\\-solo\\fR on the\ncommand line or \\fBset \\%solosidescroll\\fR in your \\fInanorc\\fR.\n.sp\nAlso since version 9.0, keystrokes \\fBM\\-<\\fR and \\fBM\\->\\fR have\nbeen reassigned to the \\fBscrollleft\\fR and \\fBscrollright\\fR functions.\nIf you want those keystrokes to do what they did before version 9.0,\nadd these two lines at the end of your \\fInanorc\\fR file:\n.sp\n.RS 4\n.B bind M\\-< prevbuf main\n.br\n.B bind M\\-> nextbuf main\n.RE\n.sp\nSince version 8.0, to be newcomer friendly, \\fB^F\\fR starts a forward search,\n\\fB^B\\fR starts a backward search, \\fBM\\-F\\fR searches the next occurrence\nforward, and \\fBM\\-B\\fR searches the next occurrence backward. If you want\nthose keystrokes to do what they did before version 8.0, add the following\nfour lines at the end of your \\fInanorc\\fR file:\n.sp\n.RS 4\n.B bind ^F forward main\n.br\n.B bind ^B back main\n.br\n.B bind M\\-F formatter main\n.br\n.B bind M\\-B linter main\n.RE\n.sp\n\n.SH DESCRIPTION\n\\fBnano\\fR is a small and friendly text editor. It copies the look and feel\nof Pico, but is free software, and implements several features that Pico\nlacks, such as: opening multiple files, scrolling per line, undo/redo,\nsyntax coloring, line numbering, and soft-wrapping overlong lines.\n.sp\nWhen giving a filename on the command line, the cursor can be put on a\nspecific line by adding the line number with a plus sign (\\fB+\\fR) before\nthe filename, and even in a specific column by adding it with a comma.\nNegative numbers count from the end of the file or line.\n.sp\nThe cursor can be put on the first or last occurrence of a specific string\nby specifying that string after \\fB+/\\fR or \\fB+?\\fR before the filename.\nThe string can be made case sensitive and/or caused to be interpreted as a\nregular expression by inserting \\fBc\\fR and/or \\fBr\\fR after the \\fB+\\fR sign.\nThese search modes can be explicitly disabled by using the uppercase variant\nof those letters: \\fBC\\fR and/or \\fBR\\fR. When the string contains spaces,\nit needs to be enclosed in quotes. To give an example: to open a file at\nthe first occurrence of the word \"Foo\", you would do:\n.sp\n.RS 4\n.BI \"nano +c/Foo \" file\n.RE\n.sp\nAs a special case: if instead of a filename a dash (\\fB\\-\\fR) is given,\n\\fBnano\\fR will read data from standard input.\n\n.SH EDITING\nEntering text and moving around in a file is straightforward: typing the\nletters and using the normal cursor movement keys. Commands are entered\nby using the Control (^) and the Alt or Meta (M\\-) keys.\nTyping \\fB^K\\fR deletes the current line and puts it in the cutbuffer.\nConsecutive \\fB^K\\fRs put all deleted lines together in the cutbuffer.\nAny cursor movement or executing any other command causes the next\n\\fB^K\\fR to overwrite the cutbuffer. A \\fB^U\\fR pastes the current\ncontents of the cutbuffer at the current cursor position.\n.sp\nWhen a more precise piece of text needs to be cut or copied, you can mark\nits start with \\fB^6\\fR, move the cursor to its end (the marked text is\nhighlighted), and then use \\fB^K\\fR to cut it, or \\fBM\\-6\\fR to copy it to\nthe cutbuffer. You can also save the marked text to a file with \\fB^O\\fR,\nor spell check it with \\fB^T^T\\fR.\n.sp\nOn some terminals, text can be selected also by holding down Shift while\nusing the arrow keys. Holding down the Ctrl or Alt key too increases\nthe stride.\nAny cursor movement without Shift being held cancels such a selection.\n.sp\nAny valid Unicode code point can be inserted into the buffer by typing\n\\fBM\\-V\\fR followed by the hexadecimal digits of the code point (concluded\nwith \\fB\\fR or \\fB\\fR when it are fewer than six digits).\nA literal control code (except \\fB^J\\fR) can be inserted by typing\n\\fBM\\-V\\fR followed by the pertinent keystroke.\n.sp\nThe two lines at the bottom of the screen show some important commands;\nthe built-in help (\\fB^G\\fR) lists all the available ones.\nThe default key bindings can be changed via a \\fInanorc\\fR file \\[em] see\n.BR nanorc (5).\n\n.SH OPTIONS\n.TP\n.BR \\-A \", \" \\-\\-smarthome\nMake the Home key smarter. When Home is pressed anywhere but at the\nvery beginning of non-whitespace characters on a line, the cursor jumps\nto that beginning (either forwards or backwards). If the cursor is\nalready at that position, it jumps to the true beginning of the line.\n.TP\n.BR \\-B \", \" \\-\\-backup\nWhen saving a file, back up the previous version of it, using the current\nfilename suffixed with a tilde (\\fB\\[ti]\\fR).\n.TP\n.BI \\-C \" directory\\fR, \" \\-\\-backupdir= directory\nMake and keep not just one backup file, but make and keep a uniquely numbered\none every time a file is saved \\[em] when backups are enabled (\\fB\\-B\\fR).\nThe uniquely numbered files are stored in the specified \\fIdirectory\\fR.\n.TP\n.BR \\-D \", \" \\-\\-boldtext\nFor the interface, use bold instead of reverse video.\nThis can be overridden for specific elements by setting the options\n\\fB\\%titlecolor\\fR, \\fB\\%statuscolor\\fR, \\fB\\%promptcolor\\fR,\n\\fB\\%minicolor\\fR, \\fB\\%keycolor\\fR, \\fB\\%numbercolor\\fR, and/or\n\\fB\\%selectedcolor\\fR in your \\fInanorc\\fR file. See \\fBnanorc\\fR(5).\n.TP\n.BR \\-E \", \" \\-\\-tabstospaces\nConvert each typed tab to spaces \\[em] to the number of spaces\nthat a tab at that position would take up.\n(Note: pasted tabs are not converted.)\n.TP\n.BR \\-F \", \" \\-\\-multibuffer\nRead a file into a new buffer by default.\n.TP\n.BR \\-G \", \" \\-\\-locking\nUse vim-style file locking when editing files.\n.TP\n.BR \\-H \", \" \\-\\-historylog\nSave the last hundred search strings and replacement strings and\nexecuted commands, so they can be easily reused in later sessions.\n.TP\n.BR \\-I \", \" \\-\\-ignorercfiles\nDon't look at the system's \\fInanorc\\fR nor at the user's \\fInanorc\\fR.\n.TP\n.BI \\-J \" number\\fR, \" \\-\\-guidestripe= number\nDraw a vertical stripe at the given column, to help judge the width of the\ntext. (The color of the stripe can be changed with \\fBset \\%stripecolor\\fR\nin your \\fInanorc\\fR file.)\n.TP\n.BR \\-K \", \" \\-\\-rawsequences\nInterpret escape sequences directly, instead of asking \\fI\\%ncurses\\fR\nto translate them. (If you need this option to get some keys to work\nproperly, it means that the \\fI\\%terminfo\\fR terminal description that\nis used does not fully match the actual behavior of your terminal.\nThis can happen when you ssh into a BSD machine, for example.)\nUsing this option disables \\fBnano\\fR's mouse support.\n.TP\n.BR \\-L \", \" \\-\\-nonewlines\nDon't automatically add a newline when a text does not end with one.\n(This can cause you to save non-POSIX text files.)\n.TP\n.BR \\-M \", \" \\-\\-trimblanks\nSnip trailing whitespace from the wrapped line when automatic\nhard-wrapping occurs or when text is justified.\n.TP\n.BR \\-N \", \" \\-\\-noconvert\nDisable automatic conversion of files from DOS format.\n.TP\n.BR \\-O \", \" \\-\\-bookstyle\nWhen justifying, treat any line that starts with whitespace as the\nbeginning of a paragraph (unless auto-indenting is on).\n.TP\n.BR \\-P \", \" \\-\\-positionlog\nFor the 200 most recent files, log the last position of the cursor,\nand place it at that position again upon reopening such a file.\nAlso save and restore the positions of any anchors.\n.TP\n.BI \"\\-Q \"\"\" regex\\fB\"\\fR, \" \\-\\-quotestr=\"\"\" regex \"\"\"\"\nSet the regular expression for matching the quoting part of a line.\nThe default value is \"\\fB^([\\ \\\\t]*([!#%:;>|}]|//))+\\fR\".\n(Note that \\fB\\\\t\\fR stands for an actual Tab.)\nThis makes it possible to rejustify blocks of quoted text when composing\nemail, and to rewrap blocks of line comments when writing source code.\n.TP\n.BR \\-R \", \" \\-\\-restricted\nRead and write only the \\fIfile\\fR (or files) specified on the command line.\nThis means: don't read or write the history files; don't allow suspending;\ndon't allow spell checking; don't allow executing any command in the shell;\ndon't allow the current buffer to be saved under a different name; don't\nallow appending or prepending to any file; and don't make backup files.\n.sp\nAs an exception, before the specified file or files, the \\fInanorc\\fR files\nare read, to allow customization. If customization should not be allowed,\nuse option \\fB\\-I\\fR (\\fB\\-\\-ignorercfiles\\fR) as well.\n.sp\nWhen no \\fIfile\\fR is specified on the command line, restricted mode\nallows you to save the contents that you type into the new buffer\nunder any name, except that existing files may not be overwritten.\nIf the places where this new file may be created should be limited,\nthen use option \\fB\\-o\\fR (\\fB\\-\\-operatingdir\\fR) as well.\n.sp\nRestricted mode can also be activated by invoking \\fBnano\\fR\nwith a name beginning with 'r' (for example: \\fBrnano\\fR).\n.TP\n.BR \\-S \", \" \\-\\-softwrap\nDisplay over multiple screen rows lines that exceed the screen's width.\n(You can make this soft-wrapping occur at whitespace instead of rudely at\nthe screen's edge, by using also \\fB\\-\\-atblanks\\fR.)\n.TP\n.BI \\-T \" number\\fR, \" \\-\\-tabsize= number\nSet the size (width) of a tab to \\fInumber\\fR columns. The value of\n\\fInumber\\fR must be greater than 0. The default value is \\fB8\\fR.\n.TP\n.BR \\-U \", \" \\-\\-quickblank\nMake status-bar messages disappear after 1 keystroke instead of after 20.\nNote that option \\fB\\-c\\fR (\\fB\\-\\-constantshow\\fR) overrides this.\nWhen option \\fB\\-\\-minibar\\fR or \\fB\\-\\-zero\\fR is in effect,\n\\fB\\-\\-quickblank\\fR makes a message disappear after\n0.8 seconds instead of after the default 1.5 seconds.\n.\n.TP\n.BR \\-V \", \" \\-\\-version\nShow the current version number and exit.\n.TP\n.BR \\-W \", \" \\-\\-wordbounds\nDetect word boundaries differently by treating punctuation\ncharacters as part of a word.\n.TP\n.BI \"\\-X \"\"\" characters\\fB\"\\fR, \" \\-\\-wordchars=\"\"\" characters \"\"\"\"\nSpecify which other characters (besides the normal alphanumeric ones)\nshould be considered as part of a word. When using this option, you\nprobably want to omit \\fB\\-W\\fR (\\fB\\-\\-wordbounds\\fR).\n.TP\n.BI \\-Y \" name\\fR, \" \\-\\-syntax= name\nSpecify the name of the syntax highlighting to use from among the ones\ndefined in the \\fInanorc\\fR files.\n.TP\n.BR \\-Z \", \" \\-\\-zap\nLet an unmodified Backspace or Delete erase the marked region\n(instead of a single character, and without affecting the cutbuffer).\n.TP\n.BR \\-a \", \" \\-\\-atblanks\nWhen doing soft line wrapping, wrap lines at whitespace\ninstead of always at the edge of the screen.\n.TP\n.BR \\-b \", \" \\-\\-breaklonglines\nAutomatically hard-wrap the current line when it becomes overlong,\nthat is: when it becomes wider than the value given with \\fB\\-r\\fR\n(\\fB\\-\\-fill\\fR). The default value for \\fB\\-r\\fR is the terminal's\nwidth minus eight.\n(This option is the opposite of \\fB\\-w\\fR (\\fB\\-\\-nowrap\\fR) \\[em]\nthe last one given takes effect.)\n.TP\n.BR \\-c \", \" \\-\\-constantshow\nConstantly report the cursor position on the status bar.\nNote that this overrides option \\fB\\-U\\fR (\\fB\\-\\-quickblank\\fR).\n.TP\n.BR \\-d \", \" \\-\\-rebinddelete\nInterpret the Delete and Backspace keys differently so that both Backspace\nand Delete work properly. You should only use this option when on your\nsystem either Backspace acts like Delete or Delete acts like Backspace.\n.TP\n.BR \\-e \", \" \\-\\-emptyline\nDo not use the line below the title bar, leaving it entirely blank.\n.TP\n.BI \\-f \" file\\fR, \" \\-\\-rcfile= file\nRead only this \\fIfile\\fR for setting nano's options, instead of reading\nboth the system-wide and the user's \\fInanorc\\fR files.\n.TP\n.BR \\-g \", \" \\-\\-showcursor\nMake the cursor visible in the file browser (putting it on the\nhighlighted item) and in the help viewer. Useful for braille users\nand people with poor vision.\n.TP\n.BR \\-h \", \" \\-\\-help\nShow a summary of the available command-line options and exit.\n.TP\n.BR \\-i \", \" \\-\\-autoindent\nAutomatically indent a newly created line to the same number of tabs\nand/or spaces as the previous line (or as the next line if the previous\nline is the beginning of a paragraph).\n.TP\n.BR \\-j \", \" \\-\\-jumpyscrolling\nScroll the buffer contents per half-screen instead of per line.\n.TP\n.BR \\-k \", \" \\-\\-cutfromcursor\nMake the 'Cut Text' command (normally \\fB^K\\fR) cut from the current cursor\nposition to the end of the line, instead of cutting the entire line.\n.TP\n.BR \\-l \", \" \\-\\-linenumbers\nDisplay line numbers to the left of the text area.\n(Any line with an anchor additionally gets a mark in the margin.)\n.TP\n.BR \\-m \", \" \\-\\-mouse\nEnable mouse support, if available for your system. When enabled, mouse\nclicks can be used to place the cursor, set the mark (with a double\nclick), and execute shortcuts. The mouse works in the X Window\nSystem, and on the console when gpm is running. Text can still be\nselected through dragging by holding down the Shift key.\n.TP\n.BR \\-n \", \" \\-\\-noread\nTreat any name given on the command line as a new file. This allows\n\\fBnano\\fR to write to named pipes: it starts with a blank buffer,\nand writes to the pipe when the user saves the \\[lq]file\\[rq]. This way\n\\fBnano\\fR can be used as an editor in combination with for instance\n\\fBgpg\\fR without having to write sensitive data to disk first.\n.TP\n.BI \\-o \" directory\\fR, \" \\-\\-operatingdir= directory\nChange to the given \\fIdirectory\\fR, and allow reading and writing\nfiles only in this directory and its subdirectories.\n.TP\n.BR \\-p \", \" \\-\\-preserve\nPreserve the XOFF and XON sequences (\\fB^S\\fR and \\fB^Q\\fR) so that\nthey are caught by the terminal (stopping and resuming the output).\nNote that option \\fB\\-/\\fR (\\fB\\-\\-modernbindings\\fR) overrides this.\n.TP\n.BR \\-q \", \" \\-\\-indicator\nDisplay a \\[lq]scrollbar\\[rq] on the righthand side of the edit window.\nIt shows the position of the viewport in the buffer\nand how much of the buffer is covered by the viewport.\n.TP\n.BI \\-r \" number\\fR, \" \\-\\-fill= number\nSet the target width for justifying and automatic hard-wrapping at this\n\\fInumber\\fR of columns. If the value is 0 or less, wrapping occurs\nat the width of the screen minus \\fInumber\\fR columns, allowing the wrap\npoint to vary along with the width of the screen if the screen is resized.\nThe default value is \\fB\\-8\\fR.\n.TP\n.B \"\\-s \"\"\\fIprogram\\fR [\\fIargument \\fR...]\\fB\"\"\\fR, \\fB\\-\\-speller=\"\"\\fIprogram\\fR [\\fIargument \\fR...]\\fB\"\"\"\nUse this command to perform spell checking and correcting, instead of\nusing the built-in corrector that calls \\fBhunspell\\fR(1) or \\fBspell\\fR(1).\n.TP\n.BR \\-t \", \" \\-\\-saveonexit\nSave a changed buffer without prompting (when exiting with \\fB^X\\fR).\n.TP\n.BR \\-u \", \" \\-\\-unix\nSave a file by default in Unix format. This overrides nano's\ndefault behavior of saving a file in the format that it had.\n(This option has no effect when you also use \\fB\\-\\-noconvert\\fR.)\n.TP\n.BR \\-v \", \" \\-\\-view\nJust view the file and disallow editing: read-only mode.\nThis mode allows the user to open also other files for viewing,\nunless \\fB\\-\\-restricted\\fR is given too.\n.TP\n.BR \\-w \", \" \\-\\-nowrap\nDo not automatically hard-wrap the current line when it becomes overlong.\nThis is the default. (This option is the opposite of \\fB\\-b\\fR\n(\\fB\\-\\-breaklonglines\\fR) \\[em] the last one given takes effect.)\n.TP\n.BR \\-x \", \" \\-\\-nohelp\nDon't show the two help lines at the bottom of the screen.\n.TP\n.BR \\-y \", \" \\-\\-afterends\nMake Ctrl+Right and Ctrl+Delete stop at word ends instead of beginnings.\n.TP\n.BR \\-z \", \" \\-\\-listsyntaxes\nList the names of the available syntaxes and exit.\n.TP\n.BR \\-! \", \" \\-\\-magic\nWhen neither the file's name nor its first line give a clue,\ntry using \\fI\\%libmagic\\fR to determine the applicable syntax.\n.TP\n.BR \\-@ \", \" \\-\\-colonparsing\nWhen a filename given on the command line ends in a colon plus digits\nand this filename does not exist, then snip the colon plus digits and\nunderstand the digits as a line number. If the trimmed filename does\nnot exist either, then repeat the process and understand the obtained\ntwo numbers as line and column number. But if the doubly trimmed\nfilename does not exist either, then forget the trimming and accept\nthe original filename as is. To disable this colon parsing for some\nfile, use \\fB+1\\fR or similar before the relevant filename.\n.TP\n.BR \\-% \", \" \\-\\-stateflags\nUse the top-right corner of the screen for showing some state flags:\n\\fBI\\fR when auto-indenting, \\fBM\\fR when the mark is on, \\fBL\\fR when\nhard-wrapping (breaking long lines), \\fBR\\fR when recording a macro,\nand \\fBS\\fR when soft-wrapping.\nWhen the buffer is modified, a star (\\fB*\\fR) is shown after the\nfilename in the center of the title bar.\n.TP\n.BR \\-_ \", \" \\-\\-minibar\nSuppress the title bar and instead show information about\nthe current buffer at the bottom of the screen, in the space\nfor the status bar. In this \\[lq]mini bar\\[rq] the filename is shown\non the left, followed by an asterisk if the buffer has been modified.\nOn the right are displayed the current line and column number, the\ncode of the character under the cursor (in Unicode format: U+xxxx),\nthe same flags as are shown by \\fB\\-\\-stateflags\\fR, and a percentage\nthat expresses how far the cursor is into the file (linewise).\nWhen a file is loaded or saved, and also when switching between buffers,\nthe number of lines in the buffer is displayed after the filename.\nThis number is cleared upon the next keystroke, or replaced with an\n[i/n] counter when multiple buffers are open.\nThe line plus column numbers and the character code are displayed only when\n\\fB\\-\\-constantshow\\fR is used, and can be toggled on and off with \\fBM\\-C\\fR.\nThe state flags are displayed only when \\fB\\-\\-stateflags\\fR is used.\n.TP\n.BR \\-0 \", \" \\-\\-zero\nHide all elements of the interface (title bar, status bar, and help lines)\nand use all rows of the terminal for showing the contents of the buffer.\nThe status bar appears only when there is a significant message,\nand disappears after 1.5 seconds or upon the next keystroke.\nWith \\fBM\\-Z\\fR the title bar plus status bar can be toggled.\nWith \\fBM\\-X\\fR the help lines.\n.TP\n.BR \\-1 \", \" \\-\\-solosidescroll\nWhen the cursor approaches the right edge of the edit window, scroll only the\ncurrent line sideways by a large amount, instead of scrolling all visible lines\nsideways by just the amount needed to keep the cursor in view.\nThis latter whole-window smooth sideways scrolling is the new default behavior.\nThe single-line jerky sideways scrolling enabled by this option was the old\nbehavior \\[em] the only behavior that \\fBnano\\fR knew.\n.TP\n.BR \\-/ \", \" \\-\\-modernbindings\nUse key bindings similar to the ones that most modern programs use:\n\\fB^X\\fR cuts, \\fB^C\\fR copies, \\fB^V\\fR pastes,\n\\fB^Z\\fR undoes, \\fB^Y\\fR redoes,\n\\fB^F\\fR searches forward, \\fB^G\\fR searches next,\n\\fB^S\\fR saves, \\fB^O\\fR opens a file, \\fB^Q\\fR quits,\nand (when the terminal permits) \\fB^H\\fR shows help.\nFurthermore, \\fB^A\\fR sets the mark, \\fB^B\\fR searches backward,\n\\fB^D\\fR searches previous, \\fB^R\\fR makes replacements,\n\\fB^P\\fR shows the position, \\fB^T\\fR goes to a line,\n\\fB^W\\fR writes out a file, and \\fB^E\\fR executes a command.\nNote that this option overrides option \\fB\\-p\\fR (\\fB\\-\\-\\%preserve\\fR).\n\n.SH TOGGLES\nSeveral of the above options can be switched on and off also while\n\\fBnano\\fR is running. For example, \\fBM\\-L\\fR toggles the\nhard-wrapping of long lines, \\fBM\\-S\\fR toggles soft-wrapping,\n\\fBM\\-N\\fR toggles line numbers, \\fBM\\-M\\fR toggles the mouse,\n\\fBM\\-I\\fR auto-indentation, and \\fBM\\-X\\fR the help lines.\nSee at the end of the \\fB^G\\fR help text for a complete list.\n.sp\nThe \\fBM\\-X\\fR toggle is special: it works in all menus except\nthe help viewer and the linter. All other toggles work in\nthe main menu only.\n\n.SH FILES\nWhen \\fB\\-\\-rcfile\\fR is given, \\fBnano\\fR reads just the specified file\nfor setting its options and syntaxes and key bindings. Without that\noption, \\fBnano\\fR reads two configuration files: first the system's\n\\fInanorc\\fR (if it exists), and then the user's \\fInanorc\\fR (if it\nexists), either \\fI\\%\\[ti]/.nanorc\\fR or \\fI\\%$XDG_CONFIG_HOME/\\:nano/\\:nanorc\\fR\nor \\fI\\%\\[ti]/.config/\\:nano/\\:nanorc\\fR, whichever is encountered first. See\n.BR nanorc (5)\nfor more information on the possible contents of those files.\n.sp\nSee \\fI/usr/\\:share/\\:nano/\\fR and \\fI/usr/\\:share/\\:nano/\\:extra/\\fR\nfor available syntax-coloring definitions.\n\n.SH EXIT STATUS\n.TP\n.B 0\nThe editor finished normally.\n.TP\n.B 1\nAn invalid option or option argument was given.\n.TP\n.B 2\nThe last open buffer was discarded (with \\fB^O^Q\\fR or \\fB^X^Q\\fR).\n\n.SH NOTES\nSuspension is enabled by default, reachable via \\fB^T^Z\\fR.\n(If you want a plain \\fB^Z\\fR to suspend nano, add\n\\fBbind ^Z suspend main\\fR to your \\fInanorc\\fR.)\n.sp\nAt a Yes-No prompt, \\fB^Y\\fR can be used for \"Yes\", \\fB^N\\fR for \"No\",\nand \\fB^A\\fR for \"All\".\n(And when exiting, \\fB^Q\\fR can be used for \"Quit with error\".)\nThese unlisted bindings work in any locale.\n.sp\nWhen you want to copy marked text from \\fBnano\\fR to the system's clipboard,\nsee one of the examples in the \\fBnanorc\\fR(5) man page.\n.sp\nIf no alternative spell checker command is specified on the command\nline nor in one of the \\fInanorc\\fR files, \\fBnano\\fR checks the\n\\fBSPELL\\fR environment variable for one.\n.sp\nIn some cases \\fBnano\\fR tries to dump the buffer into an emergency file.\nThis happens mainly if \\fBnano\\fR receives a SIGHUP or SIGTERM or runs out\nof memory. It writes the buffer into a file named \\fInano.save\\fR if the\nbuffer didn't have a name already, or adds a \".save\" suffix to the current\nfilename. If an emergency file with that name already exists in the\ncurrent directory, it adds \".save\" plus a number (for example: \".save.1\") to\nthe current filename in order to make it unique. In multibuffer mode,\n\\fBnano\\fR writes all open buffers to their respective emergency files.\n.sp\nIf you have any question about how to use \\fBnano\\fR in some specific\nsituation, you can ask on \\fIhelp\\-nano@gnu.org\\fR.\n\n.SH BUGS\nThe recording and playback of keyboard macros works correctly only on a\nterminal emulator, not on a Linux console (VT), because the latter does\nnot by default distinguish modified from unmodified arrow keys.\n.sp\nPlease report any other bugs that you encounter via:\n.br\n.IR https://savannah.gnu.org/bugs/?group=nano .\n.sp\nWhen nano crashes, it saves any modified buffers to emergency \\fI.save\\fR files.\nIf you are able to reproduce the crash and you want to get a backtrace, define\nthe environment variable \\fBNANO_NOCATCH\\fR.\n\n.SH HOMEPAGE\n.I https://nano\\-editor.org/\n\n.SH SEE ALSO\n.BR nanorc (5)\n.sp\n\\fI/usr/share/doc/nano/\\fR (or equivalent on your system)\n" }, { "path": "doc/nano.texi", "content": "\\input texinfo\n\n@c %**start of header\n@setfilename nano.info\n@settitle The GNU nano text editor\n@c %**end of header\n\n@documentencoding UTF-8\n\n@documentdescription\nThe complete manual for the GNU nano text editor.\n@end documentdescription\n\n@smallbook\n@set EDITION 0.9\n@set VERSION 9.0\n@set UPDATED April 2026\n\n@dircategory Editors\n@direntry\n* nano: (nano). Small and friendly text editor.\n@end direntry\n\n@comment Prevent the black square at the end of an overlong line.\n@finalout\n\n\n@titlepage\n\n@title GNU @command{nano}\n@subtitle a small and friendly text editor\n@subtitle version 9.0\n\n@author Chris Allegretta\n\n@page\n\nThis manual documents the GNU @command{nano} text editor.\n@sp 1\nThe contents of this manual are part of the GNU @command{nano} distribution.\n\n@sp 5\nCopyright @copyright{} 1999-2009, 2014-2026 Free Software Foundation, Inc.\n@sp 1\nThis document is dual-licensed. You may distribute and/or modify it\nunder the terms of either of the following licenses:\n@sp 1\n* The GNU General Public License, as published by the Free Software\n Foundation, version 3 or (at your option) any later version. You\n should have received a copy of the GNU General Public License along\n with this program. If not, see @url{https://www.gnu.org/licenses/}.\n@sp 1\n* The GNU Free Documentation License, as published by the Free Software\n Foundation, version 1.2 or (at your option) any later version, with no\n Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.\n You should have received a copy of the GNU Free Documentation License\n along with this program. If not, see @url{https://www.gnu.org/licenses/}.\n\n@sp 5\nYou may contact the original author by e-mail: @email{chrisa@@asty.org}\n\nOr contact the current maintainer: @email{bensberg@@coevern.nl}\n\n@sp 1\nFor suggesting improvements: @email{nano-devel@@gnu.org}\n\n@end titlepage\n\n\n@macro blankline\n@iftex\n@sp 1\n@end iftex\n@end macro\n\n\n@ifnottex\n\n@node Top\n@top\n\nThis manual documents GNU @command{nano}, version 9.0.\n\n@menu\n* Introduction::\n* Invoking::\n* Editor basics::\n* The help viewer::\n* The file browser::\n* Command-line options::\n* Feature toggles::\n* Nanorc files::\n* Pico compatibility::\n* Building and its options::\n@end menu\n\n@end ifnottex\n\n\n@node Introduction\n@chapter Introduction\n\nGNU @command{nano} is a small and friendly text editor. Besides\nbasic text editing, @command{nano} offers features like undo/redo,\nsyntax coloring, interactive search-and-replace, auto-indentation,\nline numbers, word completion, file locking, backup files, and\ninternationalization support.\n\nThe original goal for @command{nano} was to be a complete bug-for-bug\nemulation of Pico. But currently the goal is to be as compatible\nas is reasonable while offering a superset of Pico's functionality.\n@xref{Pico compatibility} for more details on how @command{nano} and\nPico differ.\n\n@blankline\nSince version 4.0, @command{nano} no longer hard-wraps overlong\nlines by default. It also by default uses linewise scrolling, and by\ndefault includes the line below the title bar in the editing area.\nIn case you want the old, Pico behavior back, you can use the\nfollowing options: @option{--breaklonglines},\n@option{--jumpyscrolling}, and @option{--emptyline}\n(or @option{-bje}).\n\n@blankline\nSince version 8.0, @kbd{^F} starts a forward search, @kbd{^B} starts\na backward search, @kbd{M-F} searches the next occurrence forward,\nand @kbd{M-B} searches the next occurrence backward. If you want\nthose keystrokes to do what they did before version 8.0, see the\nrebindings in the sample nanorc file.\n\n@blankline\nSince version 9.0, all lines are scrolled horizontally together\n(when the cursor approaches the edge), by just the amount needed,\ninstead of scrolling only the current line by a large step.\nIf you prefer the old behavior, you can use @code{--solo} on the\ncommand line or @code{set solosidescroll} in your nanorc.\n\n@blankline\nAlso since version 9.0, keystrokes @kbd{M-<} and @kbd{M->} have been\nreassigned to the @code{scrollleft} and @code{scrollright} functions.\nIf you want those keystrokes to do what they did before version 9.0,\nsee the rebindings in the sample nanorc file.\n\n@blankline\nPlease report bugs via @url{https://savannah.gnu.org/bugs/?group=nano}.\n\n@blankline\nQuestions about using nano you can ask at @email{help-nano@@gnu.org}.\n\n@blankline\nFor background information see @url{https://nano-editor.org/}.\n\n\n@node Invoking\n@chapter Invoking\n\nThe usual way to invoke @command{nano} is:\n\n@blankline\n@example\n@code{nano [FILE]}\n@end example\n@blankline\n\nBut it is also possible to specify one or more options (@pxref{Command-line options}),\nand to edit several files in a row.\n\nThe cursor can be put on a specific line of a file by adding\nthe line number with a plus sign before the filename, and even\nin a specific column by adding it with a comma.\nNegative numbers count from the end of the file or line.\n\nThe cursor can be put on the first or last occurrence of a specific string\nby specifying that string after @code{+/} or @code{+?} before the filename.\nThe string can be made case sensitive and/or caused to be interpreted as a\nregular expression by inserting a @code{c} and/or @code{r} after the plus sign.\nThese search modes can be explicitly disabled by using the uppercase variant\nof those letters: @code{C} and/or @code{R}. When the string contains spaces,\nit needs to be enclosed in quotes.\nA more complete command synopsis thus is:\n\n@blankline\n@example\n@code{nano [OPTION]@dots{} [[+LINE[,COLUMN]|+[crCR]@{/|?@}STRING] FILE]@dots{}}\n@end example\n@blankline\n\nNormally, however, you set your preferred options in a @file{nanorc}\nfile (@pxref{Nanorc files}). And when using @code{set positionlog}\n(making @command{nano} remember the cursor position when you close a file),\nyou will rarely need to specify a line number.\n\nAs a special case: when instead of a filename a dash is given, @command{nano}\nwill read data from standard input. This means you can pipe the output of\na command straight into a buffer, and then edit it.\n\n\n@node Editor basics\n@chapter Editor basics\n\n@menu\n* Screen layout::\n* Entering text::\n* Commands::\n* The cutbuffer::\n* The mark::\n* Searching and replacing::\n* Using the mouse::\n* Anchors::\n* Macros::\n* Exit status::\n@end menu\n\n@node Screen layout\n@section Screen layout\n\nThe default screen of @command{nano} consists of four areas.\nFrom top to bottom these are: the title bar, the edit window,\nthe status bar, and two help lines.\n\nThe title bar consists of\nthree sections: left, center and right. The section on the left\ndisplays the version of @command{nano} being used. The center section\ndisplays the current filename, or \"New Buffer\" if the file has not yet\nbeen named. The section on the right displays \"Modified\" if the\nfile has been modified since it was last saved or opened.\n\nThe status bar is the third line from the bottom of the screen. It\nshows important and informational messages. Any error messages that\noccur from using the editor appear on the status bar. Any questions\nthat are asked of the user are asked on the status bar, and any user\ninput (search strings, filenames, etc.) is input on the status bar.\n\nThe two help lines at the bottom of the screen show some of the most\nessential functions of the editor.\n\n@node Entering text\n@section Entering text\n\n@command{nano} is a \"modeless\" editor. This means that all keystrokes,\nwith the exception of Control and Meta sequences, enter text into the\nfile being edited.\n\nCharacters not present on the keyboard can be entered in two ways:\n\n@itemize @bullet\n@item\nFor characters with a single-byte code,\npressing the Esc key twice and then typing a three-digit decimal number\n(from @kbd{000} to @kbd{255}) makes @command{nano} behave as if you\ntyped the key with that value.\n\n@item\nFor any possible character, pressing @kbd{M-V} (Alt+V) and then typing a\nseries of hexadecimal digits (at most six, or concluded with @kbd{Enter} or\n@kbd{Space}) enters the corresponding Unicode character into the buffer.\n@end itemize\n\nFor example, typing @kbd{Esc Esc 2 3 4} enters the character \"ê\" ---\nuseful when writing about a French party. Typing @kbd{M-V 0 0 2 2 c 4}\nenters the symbol \"⋄\", a little diamond.\n\nTyping @kbd{M-V} followed by anything other than a hexadecimal digit\nenters this keystroke verbatim into the buffer, allowing the user\nto insert literal control codes (except @code{^J}) or escape sequences.\n\n@node Commands\n@section Commands\n\nCommands are given by using the Control key (Ctrl, shown as @kbd{^})\nor the Meta key (Alt or Cmd, shown as @kbd{M-}).\n\n@itemize @bullet\n@item\nA control-key sequence is entered by holding down the Ctrl key and\npressing the desired key.\n\n@item\nA meta-key sequence is entered by holding down the Meta key (normally\nthe Alt key) and pressing the desired key.\n@end itemize\n\nIf for some reason on your system the combinations with Ctrl or Alt do\nnot work, you can generate them by using the Esc key. A control-key\nsequence is generated by pressing the Esc key twice and then pressing\nthe desired key, and a meta-key sequence by pressing the Esc key once\nand then pressing the desired key.\n\n@node The cutbuffer\n@section The cutbuffer\n\nText can be cut from a file a whole line at a time with @kbd{^K}.\nThe cut line is stored in the cutbuffer. Consecutive strokes of @kbd{^K}\nadd each cut line to this buffer, but a @kbd{^K}\nafter any other keystroke overwrites the entire cutbuffer.\n\nThe contents of the cutbuffer can be pasted at the current cursor position\nwith @kbd{^U}.\n\nA line of text can be copied into the cutbuffer (without cutting it)\nwith @kbd{M-6}.\n\n@node The mark\n@section The mark\n\nText can be selected by first 'setting the Mark' with @kbd{^6}\nor @kbd{M-A} and then moving the cursor to the other end of the portion\nto be selected. The selected portion of text is highlighted.\nThis selection can now be cut or copied in its entirety with a single\n@kbd{^K} or @kbd{M-6}. Or the selection can be used to limit the scope of\na search-and-replace (@kbd{^\\}) or spell-checking session (@kbd{^T^T}).\n\nOn some terminals, text can be selected also by holding down @kbd{Shift}\nwhile using the cursor keys. Holding down the @kbd{Ctrl} or @kbd{Alt}\nkey too increases the stride. Such a selection is cancelled\nupon any cursor movement where @kbd{Shift} isn't held.\n\nCutting or copying selected text toggles off the mark automatically.\nIf needed, it can be toggled off manually with another @kbd{^6} or @kbd{M-A}.\n\n@node Searching and replacing\n@section Searching and replacing\n\nWith the Search command (@kbd{^F} or @kbd{^W}) you can search the\ncurrent buffer for the occurrence of any string. The default search\nmode is forward, case-insensitive, and for literal strings. But one\ncan search backwards by toggling @kbd{M-B}, search case sensitively\nwith @kbd{M-C}, and interpret regular expressions in the search string\nwith @kbd{M-R}.\n\nWith the Replace command (@kbd{M-R} or @kbd{^\\}) you can replace\na given string (or regular expression) with another string.\nWhen a regular expression contains fragments between parentheses,\nthe replacement string can refer back to these fragments via\n@code{\\1} to @code{\\9}.\n\nFor each occurrence of the search string you are asked whether to\nreplace it. You can choose Yes (replace it), or No (skip this one),\nor All (replace all remaining occurrences without asking any more),\nor Cancel (stop with replacing, but replacements that have already\nbeen made will not be undone).\n\nIf before a replacing session starts a region is marked, then\nonly occurrences of the search string within the marked region\nwill be replaced.\n\nA regular expression always covers just one line --- it cannot span\nmultiple lines. And neither a search string nor a replacement string\ncan contain a newline (LF).\n\n@node Using the mouse\n@section Using the mouse\n\nWhen mouse support has been configured and enabled, a single mouse click\nplaces the cursor at the indicated position. Clicking a second time in\nthe same position toggles the mark. Clicking in the two help lines\nexecutes the selected shortcut. To be able to select text with the\nleft button, or paste text with the middle button, hold down the\nShift key during those actions.\n\nThe mouse works in the X Window System, and on the console when gpm\nis running.\n\n@node Anchors\n@section Anchors\n\nWith @kbd{M-Ins} you can place an anchor (a kind of bookmark) at\nthe current line. With @kbd{M-PgUp} and @kbd{M-PgDn} you can jump\nto an anchor in the backward/forward direction. This jumping wraps\naround at the top and bottom.\n\nWhen an operation removes a line with an anchor, the new line with the\ncursor inherits the anchor. But after performing an operation on the\nentire buffer (like formatting it, piping it through a command, or\ndoing an external spell check on it), any anchors that were present\nare gone.\n\nWhen @option{--positionlog} or @code{set positionlog} is active, anchors\nare saved when the file is closed, and restored when the file is reopened.\n\nAnchors are visualized in the left margin if line numbers are active,\nand are always visualized (on the right-hand side) in the mini bar.\n\n@node Macros\n@section Macros\n\nTo record a series of keystrokes that you need to perform many times,\nstart the recording with @kbd{M-:}, carefully type the series of keystrokes,\nand then stop the recording by using @kbd{M-:} again. The recorded result\nis called a keyboard macro. You can replay this macro with @kbd{M-;},\nas many times as needed.\n\nWhen you type @kbd{M-:} (recordmacro) by mistake, then type @kbd{M-:}\nagain right away, to cancel the recording. An existing macro is then\nnot overwritten.\n\nNote: the recording and playback of keyboard macros works correctly only\non a terminal emulator, not on a Linux console (VT), because the latter\ndoes not by default distinguish modified from unmodified cursor keys.\n\n@node Exit status\n@section Exit status\n\nThe exit status is @code{0} when @command{nano} finished normally,\n@code{1} when an invalid option or option argument was given,\nand @code{2} when the last open buffer was discarded\n(with @kbd{^O^Q} or @kbd{^X^Q}).\n\n\n@node The help viewer\n@chapter The help viewer\n\nThe built-in help in @command{nano} is available by pressing @kbd{^G}.\nIt is fairly self-explanatory. It documents the various parts of the\neditor and the available keystrokes. Navigation is via the @kbd{^Y} (Page Up)\nand @kbd{^V} (Page Down) keys. @kbd{^X} exits from the help viewer.\n\n\n@node The file browser\n@chapter The file browser\n\nWhen in the Read-File (@kbd{^R}) or Write-Out menu (@kbd{^O}),\npressing @kbd{^T} invokes the file browser.\nHere, you can navigate directories in a graphical manner in order to\nfind the desired file.\n\nBasic movement in the file browser is accomplished with the arrow and\nother cursor-movement keys. More targeted movement is accomplished by\nsearching, via @kbd{^W} or @kbd{w}, or by changing directory, via\n@kbd{^_} or @kbd{g}. The behavior of the @kbd{Enter} key (or @kbd{s})\nvaries by what is currently selected.\nIf the currently selected object is a directory, the file browser\nenters and displays the contents of the directory. If the object is a\nfile, this filename and path are copied to the status bar, and the file\nbrowser exits.\n\n\n@node Command-line options\n@chapter Command-line options\n\n@command{nano} accepts the following options from the command line:\n\n@table @option\n\n@item -A\n@itemx --smarthome\nMake the Home key smarter. When Home is pressed anywhere but at the\nvery beginning of non-whitespace characters on a line, the cursor jumps\nto that beginning (either forwards or backwards). If the cursor is\nalready at that position, it jumps to the true beginning of the line.\n\n@item -B\n@itemx --backup\nWhen saving a file, back up the previous version of it, using the current\nfilename suffixed with a tilde (@code{~}).\n\n@item -C @var{directory}\n@itemx --backupdir=@var{directory}\nMake and keep not just one backup file, but make and keep a uniquely\nnumbered one every time a file is saved --- when backups are enabled.\nThe uniquely numbered files are stored in the specified directory.\n\n@item -D\n@itemx --boldtext\nFor the interface, use bold instead of reverse video.\nThis can be overridden for specific elements\nby setting the options @code{titlecolor}, @code{statuscolor},\n@code{promptcolor}, @code{minicolor}, @code{keycolor},\n@code{numbercolor}, and/or @code{selectedcolor} in your\nnanorc file. @xref{@code{set keycolor}} for details.\n\n@item -E\n@itemx --tabstospaces\nConvert each typed tab to spaces --- to the number of spaces\nthat a tab at that position would take up.\n(Note: pasted tabs are not converted.)\n\n@item -F\n@itemx --multibuffer\nRead a file into a new buffer by default.\n\n@item -G\n@itemx --locking\nEnable vim-style file locking when editing files.\n\n@item -H\n@itemx --historylog\nSave the last hundred search strings and replacement strings and\nexecuted commands, so they can be easily reused in later sessions.\n\n@item -I\n@itemx --ignorercfiles\nDon't look at the system's nanorc file nor at the user's nanorc.\n\n@item -J\n@itemx --guidestripe\nDraw a vertical stripe at the given column, to help judge the width of the\ntext. (The color of the stripe can be changed with @code{set stripecolor}\nin your nanorc file.)\n\n@item -K\n@itemx --rawsequences\nInterpret escape sequences directly, instead of asking @code{ncurses}\nto translate them. (If you need this option to get some keys to work\nproperly, it means that the terminfo terminal description that is used\ndoes not fully match the actual behavior of your terminal. This can\nhappen when you ssh into a BSD machine, for example.)\nUsing this option disables @command{nano}'s mouse support.\n\n@item -L\n@itemx --nonewlines\nDon't automatically add a newline when a text does not end with one.\n(This can cause you to save non-POSIX text files.)\n\n@item -M\n@itemx --trimblanks\nSnip trailing whitespace from the wrapped line when automatic\nhard-wrapping occurs or when text is justified.\n\n@item -N\n@itemx --noconvert\nDisable automatic conversion of files from DOS format.\n\n@item -O\n@itemx --bookstyle\nWhen justifying, treat any line that starts with whitespace as the\nbeginning of a paragraph (unless auto-indenting is on).\n\n@item -P\n@itemx --positionlog\nFor the 200 most recent files, log the last position of the cursor,\nand place it at that position again upon reopening such a file.\nAlso save and restore the positions of any anchors.\n\n@item -Q \"@var{regex}\"\n@itemx --quotestr=\"@var{regex}\"\nSet the regular expression for matching the quoting part of a line.\nThe default value is \"@t{^([@w{ }\\t]*([!#%:;>|@}]|//))+}\".\n(Note that @code{\\t} stands for a literal Tab character.)\nThis makes it possible to rejustify blocks of quoted text when composing\nemail, and to rewrap blocks of line comments when writing source code.\n\n@item -R\n@itemx --restricted\nRead and write only the file (or files) specified on the command line.\nThis means: don't read or write the history files; don't allow suspending;\ndon't allow spell checking; don't allow executing any command in the shell;\ndon't allow the current buffer to be saved under a different name; don't\nallow appending or prepending to any file; and don't make backup files.\n\nAs an exception, before the specified file or files, the nanorc files are\nread, to allow customization. If customization should not be allowed,\nuse option @option{-I} (@option{--ignorercfiles}) as well.\n\nWhen no file is specified on the command line, restricted mode\nallows you to save the contents that you type into the new buffer\nunder any name, except that existing files may not be overwritten.\nIf the places where this new file may be created should be limited,\nthen use option @option{-o} (@option{--operatingdir}) as well.\n\nRestricted mode can also be activated by invoking @command{nano} with\na name beginning with @code{r} (for example: @command{rnano}).\n\n@item -S\n@itemx --softwrap\nDisplay over multiple screen rows lines that exceed the screen's width.\n(You can make this soft-wrapping occur at whitespace instead of rudely at\nthe screen's edge, by using also @code{--atblanks}.)\n\n@item -T @var{number}\n@itemx --tabsize=@var{number}\nSet the displayed tab length to @var{number} columns. The value of\n@var{number} must be greater than 0. The default value is @t{8}.\n\n@item -U\n@itemx --quickblank\nMake status-bar messages disappear after 1 keystroke instead of after 20.\nNote that option @option{-c} (@option{--constantshow}) overrides this.\nWhen option @option{--minibar} or @option{--zero} is in effect,\n@option{--quickblank} makes a message disappear after\n0.8 seconds instead of after the default 1.5 seconds.\n\n@item -V\n@itemx --version\nShow the current version number and exit.\n\n@item -W\n@itemx --wordbounds\nDetect word boundaries differently by treating punctuation\ncharacters as parts of words.\n\n@item -X \"@var{characters}\"\n@itemx --wordchars=\"@var{characters}\"\nSpecify which other characters (besides the normal alphanumeric ones)\nshould be considered as parts of words. When using this option, you\nprobably want to omit @option{-W} (@option{--wordbounds}).\n\n@item -Y @var{name}\n@itemx --syntax=@var{name}\nSpecify the syntax to be used for highlighting.\n@xref{Syntax highlighting} for more info.\n\n@item -Z\n@itemx --zap\nLet an unmodified @kbd{Backspace} or @kbd{Delete} erase the marked region\n(instead of a single character, and without affecting the cutbuffer).\n\n@item -a\n@itemx --atblanks\nWhen doing soft line wrapping, wrap lines at whitespace\ninstead of always at the edge of the screen.\n\n@item -b\n@itemx --breaklonglines\nAutomatically hard-wrap the current line when it becomes overlong,\nthat is: when the line becomes wider than the value given with @option{-r}\n(@option{--fill}). The default value for @option{-r} is the terminal's\nwidth minus eight.\n(This option is the opposite of @option{-w} (@option{--nowrap}) ---\nthe last one given takes effect.)\n\n@item -c\n@itemx --constantshow\nConstantly report the cursor position (line number, column number,\nand character number) on the status bar.\nNote that this overrides option @option{-U} (@option{--quickblank}).\n\n@item -d\n@itemx --rebinddelete\nInterpret the @kbd{Delete} and @kbd{Backspace} keys differently so that\nboth work properly. You should only use this option when on your system\neither @kbd{Backspace} acts like Delete or @kbd{Delete} acts like Backspace.\n\n@item -e\n@itemx --emptyline\nDo not use the line below the title bar, leaving it entirely blank.\n\n@item -f @var{file}\n@itemx --rcfile=@var{file}\nRead only this @var{file} for setting nano's options, instead of reading\nboth the system-wide and the user's nanorc files.\n\n@item -g\n@itemx --showcursor\nMake the cursor visible in the file browser (putting it on the\nhighlighted item) and in the help viewer. Useful for braille users\nand people with poor vision.\n\n@item -h\n@itemx --help\nShow a summary of command-line options and exit.\n\n@item -i\n@itemx --autoindent\nAutomatically indent a newly created line to the same number of tabs\nand/or spaces as the previous line (or as the next line if the previous\nline is the beginning of a paragraph).\n\n@item -j\n@itemx --jumpyscrolling\nScroll the buffer contents per half-screen instead of per line.\n\n@item -k\n@itemx --cutfromcursor\nMake the 'Cut Text' command (normally @kbd{^K}) cut from the current cursor\nposition to the end of the line, instead of cutting the entire line.\n\n@item -l\n@itemx --linenumbers\nDisplay line numbers to the left of the text area.\n(Any line with an anchor additionally gets a mark in the margin.)\n\n@item -m\n@itemx --mouse\nEnable mouse support, if available for your system. When enabled, mouse\nclicks can be used to place the cursor, set the mark (with two clicks),\nand execute shortcuts. The mouse works in the X Window System, and on\nthe console when gpm is running. Text can still be selected through\ndragging by holding down the Shift key.\n\n@item -n\n@itemx --noread\nTreat any name given on the command line as a new file. This allows\n@command{nano} to write to named pipes: it starts with a blank buffer,\nand writes to the pipe when the user saves the “file”. This way\n@command{nano} can be used as an editor in combination with for instance\n@command{gpg} without having to write sensitive data to disk first.\n\n@item -o @var{directory}\n@itemx --operatingdir=@var{directory}\nChange to the given @var{directory}, and allow reading and writing\nfiles only in this directory and its subdirectories.\n\n@item -p\n@itemx --preserve\nPreserve the @kbd{^S} (XOFF) and @kbd{^Q} (XON) sequences so that\ndata being sent to the terminal can be stopped and resumed.\nNote that option @option{-/} (@option{--modernbindings}) overrides this.\n\n@item -q\n@itemx --indicator\nDisplay a “scrollbar” on the righthand side of the edit window.\nIt shows the position of the viewport in the buffer\nand how much of the buffer is covered by the viewport.\n\n@item -r @var{number}\n@itemx --fill=@var{number}\nSet the target width for justifying and automatic hard-wrapping at this\n@var{number} of columns. If the value is 0 or less, wrapping occurs\nat the width of the screen minus @var{number} columns, allowing the wrap\npoint to vary along with the width of the screen if the screen is resized.\nThe default value is @t{-8}.\n\n@anchor{@option{--speller}}\n@item -s \"@var{program} [@var{argument} @dots{}]\"\n@itemx --speller=\"@var{program} [@var{argument} @dots{}]\"\nUse the given program to do spell checking and correcting. By default,\n@command{nano} uses the command specified in the @env{SPELL} environment\nvariable. If @env{SPELL} is not set, and @option{--speller} is\nnot specified either, then @command{nano} uses its own interactive spell\ncorrector, which requires either @command{hunspell} or GNU @command{spell}\nto be installed.\n\n@item -t\n@itemx --saveonexit\nSave a changed buffer without prompting (when exiting with @kbd{^X}).\nThis can be handy when @command{nano} is used as the composer of an\nemail program.\n\n@item -u\n@item --unix\nSave a file by default in Unix format. This overrides nano's\ndefault behavior of saving a file in the format that it had.\n(This option has no effect when you also use @option{--noconvert}.)\n\n@item -v\n@itemx --view\nDon't allow the contents of the file to be altered: read-only mode.\nThis mode allows the user to open also other files for viewing,\nunless @option{--restricted} is given too.\n(Note that this option should NOT be used in place of correct\nfile permissions to implement a read-only file.)\n\n@item -w\n@itemx --nowrap\nDo not automatically hard-wrap the current line when it becomes overlong.\nThis is the default. (This option is the opposite of @option{-b}\n(@option{--breaklonglines}) --- the last one given takes effect.)\n\n\n@item -x\n@itemx --nohelp\nExpert mode: don't show the two help lines at the bottom of the screen.\nThis affects the location of the status bar as well, as in Expert mode it\nis located at the very bottom of the editor.\n\nNote: When accessing the help system, Expert mode is temporarily\ndisabled to display the help-system navigation keys.\n\n@item -y\n@itemx --afterends\nMake @kbd{Ctrl+Right} and @kbd{Ctrl+Delete} stop at word ends\ninstead of beginnings.\n\n@item -z\n@itemx --listsyntaxes\nList the names of the available syntaxes and exit.\n\n@item -!\n@itemx --magic\nWhen neither the file's name nor its first line give a clue,\ntry using libmagic to determine the applicable syntax.\n\n@item -@@\n@itemx --colonparsing\nWhen a filename given on the command line ends in a colon plus digits\nand this filename does not exist, then snip the colon plus digits and\nunderstand the digits as a line number. If the trimmed filename does\nnot exist either, then repeat the process and understand the obtained\ntwo numbers as line and column number. But if the doubly trimmed\nfilename does not exist either, then forget the trimming and accept\nthe original filename as is. To disable this colon parsing for some\nfile, use @code{+1} or similar before the relevant filename.\n\n@item -%\n@itemx --stateflags\nUse the top-right corner of the screen for showing some state flags:\n@code{I} when auto-indenting, @code{M} when the mark is on, @code{L} when\nhard-wrapping (breaking long lines), @code{R} when recording a macro,\nand @code{S} when soft-wrapping.\nWhen the buffer is modified, a star (@code{*}) is shown after the\nfilename in the center of the title bar.\n\n@item -_\n@itemx --minibar\nSuppress the title bar and instead show information about\nthe current buffer at the bottom of the screen, in the space\nfor the status bar. In this “mini bar” the filename is shown\non the left, followed by an asterisk if the buffer has been modified.\nOn the right are displayed the current line and column number, the\ncode of the character under the cursor (in Unicode format: U+xxxx),\nthe same flags as are shown by @code{--stateflags}, and a percentage\nthat expresses how far the cursor is into the file (linewise).\nWhen a file is loaded or saved, and also when switching between buffers,\nthe number of lines in the buffer is displayed after the filename.\nThis number is cleared upon the next keystroke, or replaced with an\n[i/n] counter when multiple buffers are open.\nThe line plus column numbers and the character code are displayed only when\n@code{--constantshow} is used, and can be toggled on and off with @kbd{M-C}.\nThe state flags are displayed only when @code{--stateflags} is used.\n\n@item -0\n@itemx --zero\nHide all elements of the interface (title bar, status bar, and help lines)\nand use all rows of the terminal for showing the contents of the buffer.\nThe status bar appears only when there is a significant message,\nand disappears after 1.5 seconds or upon the next keystroke.\nWith @kbd{M-Z} the title bar plus status bar can be toggled.\nWith @kbd{M-X} the help lines.\n\n@item -1\n@itemx --solosidescroll\nWhen the cursor approaches the right edge of the edit window, scroll only the\ncurrent line sideways by a large amount, instead of scrolling all visible lines\nsideways by just the amount needed to keep the cursor in view.\nThis latter whole-window smooth sideways scrolling is the new default behavior.\nThe single-line jerky sideways scrolling enabled by this option was the old\nbehavior --- the only behavior that @command{nano} knew.\n\n@item -/\n@itemx --modernbindings\nUse key bindings similar to the ones that most modern programs use:\n@kbd{^X} cuts, @kbd{^C} copies, @kbd{^V} pastes,\n@kbd{^Z} undoes, @kbd{^Y} redoes,\n@kbd{^F} searches forward, @kbd{^G} searches next,\n@kbd{^S} saves, @kbd{^O} opens a file, @kbd{^Q} quits,\nand (when the terminal permits) @kbd{^H} shows help.\nFurthermore, @kbd{^A} sets the mark, @kbd{^B} searches backward,\n@kbd{^D} searches previous, @kbd{^R} makes replacements,\n@kbd{^P} shows the position, @kbd{^T} goes to a line,\n@kbd{^W} writes out a file, and @kbd{^E} executes a command.\nNote that this option overrides option @option{-p} (@option{--preserve}).\n\n@end table\n\n@sp 1\nSuspension is enabled by default, reachable via @kbd{^T^Z}.\n(If you want a plain @kbd{^Z} to suspend nano, add\n@code{bind ^Z suspend main} to your nanorc.)\n\n\n@node Feature toggles\n@chapter Feature toggles\n\nToggles allow you to change certain aspects of the editor while you are\nediting, aspects that you would normally specify via command-line options\nor nanorc options. Each toggle can be flicked via a Meta-key combination\n--- the @kbd{Meta} key is normally the @kbd{Alt} key (@pxref{Commands}\nfor more details). The following global toggles are available:\n\n@sp 1\n@table @code\n\n@item Constant Cursor Position Display\n@kbd{M-C} toggles the @option{-c} (@option{--constantshow}) command-line option.\n\n@item Smart Home Key\n@kbd{M-H} toggles the @option{-A} (@option{--smarthome}) command-line option.\n\n@item Auto Indent\n@kbd{M-I} toggles the @option{-i} (@option{--autoindent}) command-line option.\n\n@item Cut From Cursor To End-of-Line\n@kbd{M-K} toggles the @option{-k} (@option{--cutfromcursor}) command-line option.\n\n@item Long-Line Wrapping\n@kbd{M-L} toggles the @option{-b} (@option{--breaklonglines}) command-line option.\n\n@item Mouse Support\n@kbd{M-M} toggles the @option{-m} (@option{--mouse}) command-line option.\n\n@item Line Numbers\n@kbd{M-N} toggles the @option{-l} (@option{--linenumbers}) command-line option.\n\n@item Tabs To Spaces\n@kbd{M-O} toggles the @option{-E} (@option{--tabstospaces}) command-line option.\n\n@item Whitespace Display\n@kbd{M-P} toggles the displaying of whitespace (@pxref{Whitespace}).\n\n@item Soft Wrapping\n@kbd{M-S} toggles the @option{-S} (@option{--softwrap}) command-line option.\n\n@item Expert\n@kbd{M-X} toggles the @option{-x} (@option{--nohelp}) command-line option.\n\n@item Syntax Coloring\n@kbd{M-Y} toggles syntax coloring, when your nanorc defines syntaxes\n(@pxref{Syntax highlighting}).\n\n@item Hidden Interface\n@kbd{M-Z} toggles the @option{-0} (@option{--zero}) command-line option,\nbut without the @option{-x} (@option{--nohelp}) part. That is: it toggles\njust the title bar plus status bar (or the combined mini bar plus status bar),\nnot the help lines. The latter are toggled with @kbd{M-X}.\n\n@end table\n\n\n@node Nanorc files\n@chapter Nanorc files\n\nNanorc files can be used to configure @command{nano} to your liking\nwithout using command-line options. During startup @command{nano}\nnormally reads two files: first the system-wide file, @file{/etc/nanorc}\n(the exact path may be different on your system), and then the user-specific\nfile, either @file{~/.nanorc} or @file{$XDG_CONFIG_HOME/nano/nanorc} or\n@file{.config/nano/nanorc}, whichever exists first.\nHowever, if @option{--rcfile} is given, @command{nano} skips the\nabove files and reads just the specified settings file.\n\nA nanorc file can contain @command{set} and @command{unset} commands for\nvarious options (@pxref{Settings}). It can also contain commands that\ndefine syntax highlighting (@pxref{Syntax highlighting}) and commands\nthat rebind keys (@ref{Rebinding keys}). Each command should be on a\nseparate line, and all commands should be written in lowercase.\n\nOptions that do not take an argument are unset by default. So using\nthe @code{unset} command is only needed when wanting to override a\nsetting from the system's nanorc file in your own nanorc. Options that\ntake an argument cannot be unset, but can be assigned the empty string.\n\nAny command-line option overrides its nanorc setting, of course.\n\nQuotes inside the @var{characters} parameters below should not be escaped.\nThe last double quote on the line will be seen as the closing quote.\n\n@menu\n* Settings::\n* Syntax highlighting::\n* Rebinding keys::\n@end menu\n\n@node Settings\n@section Settings\n\nThe supported settings in a nanorc file are:\n\n@table @code\n\n@item set afterends\nMake @kbd{Ctrl+Right} and @kbd{Ctrl+Delete} stop at word ends\ninstead of beginnings.\n\n@item set allow_insecure_backup\nWhen backing up files, allow the backup to succeed even if its\npermissions can't be (re)set due to special OS considerations.\nYou should NOT enable this option unless you are sure you need it.\n\n@item set atblanks\nWhen soft line wrapping is enabled, make it wrap lines at blank characters\n(tabs and spaces) instead of always at the edge of the screen.\n\n@item set autoindent\nAutomatically indent a newly created line to the same number of tabs\nand/or spaces as the previous line (or as the next line if the previous\nline is the beginning of a paragraph).\n\n@item set backup\nWhen saving a file, back up the previous version of it, using the current\nfilename suffixed with a tilde (@code{~}).\n\n@item set backupdir \"@var{directory}\"\nMake and keep not just one backup file, but make and keep a uniquely\nnumbered one every time a file is saved --- when backups are enabled\nwith @code{set backup} or @option{--backup} or @option{-B}.\nThe uniquely numbered files are stored in the specified directory.\n\n@item set boldtext\nUse bold instead of reverse video for the title bar, status bar,\nprompt bar, mini bar, key combos, line numbers, and selected text.\nThis can be overridden by setting the options @code{titlecolor},\n@code{statuscolor}, @code{promptcolor}, @code{minicolor},\n@code{keycolor}, @code{numbercolor}, and/or @code{selectedcolor}.\n\n@item set bookstyle\nWhen justifying, treat any line that starts with whitespace as the\nbeginning of a paragraph (unless auto-indenting is on).\n\n@item set brackets \"@var{characters}\"\nSet the characters treated as closing brackets when justifying\nparagraphs. This may not include blank characters. Only closing\npunctuation (see @code{set punct}), optionally followed by the specified\nclosing brackets, can end sentences. The default value is\n\"@t{\"')>]@}}\".\n\n@item set breaklonglines\nAutomatically hard-wrap the current line when it becomes overlong --- that\nis: when the line becomes wider than the value given with @code{set fill}\n(which defaults to the width of the terminal minus eight).\n\n@item set casesensitive\nDo case-sensitive searches by default.\n\n@item set colonparsing\nWhen a filename given on the command line ends in a colon plus digits\nand this filename does not exist, then snip the colon plus digits and\nunderstand the digits as a line number. If the trimmed filename does\nnot exist either, then repeat the process and understand the obtained\ntwo numbers as line and column number. But if the doubly trimmed\nfilename does not exist either, then forget the trimming and accept\nthe original filename as is. To disable this colon parsing for some\nfile, use @code{+1} or similar before the relevant filename.\n\n@item set constantshow\nConstantly report the cursor position on the status bar.\nNote that this overrides @option{quickblank}.\n\n@item set cutfromcursor\nUse cut-from-cursor-to-end-of-line by default, instead of cutting the whole line.\n\n@item set emptyline\nDo not use the line below the title bar, leaving it entirely blank.\n\n@item set errorcolor [bold,][italic,]@var{fgcolor},@var{bgcolor}\nUse this color combination for the status bar when an error message is displayed.\nThe default value is @t{bold,white,red}.\n@xref{@code{set keycolor}} for valid color names.\n\n@item set fill @var{number}\nSet the target width for justifying and automatic hard-wrapping at this\n@var{number} of columns. If the value is 0 or less, wrapping occurs\nat the width of the screen minus @var{number} columns, allowing the wrap\npoint to vary along with the width of the screen if the screen is resized.\nThe default value is @t{-8}.\n\n@item set functioncolor [bold,][italic,]@var{fgcolor},@var{bgcolor}\nUse this color combination for the concise function descriptions\nin the two help lines at the bottom of the screen.\n@xref{@code{set keycolor}} for valid color names.\n\n@item set guidestripe @var{number}\nDraw a vertical stripe at the given column, to help judge the width of the\ntext. (The color of the stripe can be changed with @code{set stripecolor}.)\n\n@item set historylog\nSave the last hundred search strings and replacement strings and\nexecuted commands, so they can be easily reused in later sessions.\n\n@item set indicator\nDisplay a “scrollbar” on the righthand side of the edit window.\nIt shows the position of the viewport in the buffer\nand how much of the buffer is covered by the viewport.\n\n@item set jumpyscrolling\nScroll the buffer contents per half-screen instead of per line.\n\n@anchor{@code{set keycolor}}\n@item set keycolor [bold,][italic,]@var{fgcolor},@var{bgcolor}\nUse this color combination for the shortcut key combos\nin the two help lines at the bottom of the screen.\nValid names for the foreground and background colors are:\n@code{red}, @code{green}, @code{blue},\n@code{magenta}, @code{yellow}, @code{cyan},\n@code{white}, and @code{black}.\nEach of these eight names may be prefixed with the word\n@code{light} to get a brighter version of that color.\nThe word @code{grey} or @code{gray} may be used\nas a synonym for @code{lightblack}.\nOn a Linux console, @code{light} does not have\nany effect for a background color.\n\nOn terminal emulators that can do at least 256 colors,\nother valid (but unprefixable) color names are:\n@code{pink}, @code{purple}, @code{mauve},\n@code{lagoon}, @code{mint}, @code{lime},\n@code{peach}, @code{orange}, @code{latte},\n@code{rosy}, @code{beet}, @code{plum}, @code{sea},\n@code{sky}, @code{slate}, @code{teal}, @code{sage},\n@code{brown}, @code{ocher}, @code{sand}, @code{tawny},\n@code{brick}, @code{crimson}, and @code{normal}\n--- where @code{normal} means the default foreground or background color.\nOn such emulators, the color may also be specified as a three-digit hexadecimal\nnumber prefixed with @code{#}, with the digits representing the amounts of red,\ngreen, and blue, respectively. This tells @command{nano} to select from the\navailable palette the color that approximates the given values.\n\nEither @var{fgcolor} or ,@var{bgcolor} may be left out,\nand the pair may be preceded by @code{bold} and/or @code{italic}\n(separated by commas) to get a bold and/or slanting typeface,\nif your terminal can do those.\n\n@item set linenumbers\nDisplay line numbers to the left of the text area.\n(Any line with an anchor additionally gets a mark in the margin.)\n\n@item set locking\nUse vim-style lock-files when editing files.\n\n@item set magic\nWhen neither the file's name nor its first line give a clue,\ntry using libmagic to determine the applicable syntax.\n(Calling libmagic can be relatively time consuming.\nIt is therefore not done by default.)\n\n@anchor{@code{set matchbrackets}}\n@item set matchbrackets \"@var{characters}\"\nSpecify the opening and closing brackets that can be found by bracket\nsearches. This may not include blank characters. The opening set must\ncome before the closing set, and the two sets must be in the same order.\nThe default value is \"@t{(<[@{)>]@}}\".\n\n@item set minibar\nSuppress the title bar and instead show information about\nthe current buffer at the bottom of the screen, in the space\nfor the status bar. In this “mini bar” the filename is shown\non the left, followed by an asterisk if the buffer has been modified.\nOn the right are displayed the current line and column number, the\ncode of the character under the cursor (in Unicode format: U+xxxx),\nthe same flags as are shown by @code{set stateflags}, and a percentage\nthat expresses how far the cursor is into the file (linewise).\nWhen a file is loaded or saved, and also when switching between buffers,\nthe number of lines in the buffer is displayed after the filename.\nThis number is cleared upon the next keystroke, or replaced with an\n[i/n] counter when multiple buffers are open.\nThe line plus column numbers and the character code are displayed only when\n@code{set constantshow} is used, and can be toggled on and off with @kbd{M-C}.\nThe state flags are displayed only when @code{set stateflags} is used.\n\n@item set minicolor [bold,][italic,]@var{fgcolor},@var{bgcolor}\nUse this color combination for the mini bar.\n(When this option is not specified, the colors of the title bar are used.)\n@xref{@code{set keycolor}} for valid color names.\n\n@item set mouse\nEnable mouse support, so that mouse clicks can be used to place the\ncursor, set the mark (with two clicks), or execute shortcuts.\n\n@item set multibuffer\nWhen reading in a file with @kbd{^R}, insert it into a new buffer by default.\n\n@item set noconvert\nDon't convert files from DOS format.\n\n@item set nohelp\nDon't display the help lists at the bottom of the screen.\n\n@item set nonewlines\nDon't automatically add a newline when a text does not end with one.\n(This can cause you to save non-POSIX text files.)\n\n@item set nowrap\nDeprecated option since it has become the default setting.\nWhen needed, use @code{unset breaklonglines} instead.\n\n@item set numbercolor [bold,][italic,]@var{fgcolor},@var{bgcolor}\nUse this color combination for line numbers.\n@xref{@code{set keycolor}} for valid color names.\n\n@item set operatingdir \"@var{directory}\"\nAt startup, make @command{nano} change to the given @var{directory}, and\nallow reading and writing files only in this directory and its subdirectories.\n\n@item set positionlog\nSave the positions of cursor and anchors between editing sessions.\nThese positions are remembered for the 200 most-recently edited files.\n\n@item set preserve\nPreserve the XOFF and XON sequences (@kbd{^S} and @kbd{^Q}) so that\nthey are caught by the terminal (stopping and resuming the output).\n\n@item set promptcolor [bold,][italic,]@var{fgcolor},@var{bgcolor}\nUse this color combination for the prompt bar.\n(When this option is not specified, the colors of the title bar are used.)\n@xref{@code{set keycolor}} for valid color names.\n\n@item set punct \"@var{characters}\"\nSet the characters treated as closing punctuation when justifying\nparagraphs. This may not include blank characters. Only the\nspecified closing punctuation, optionally followed by closing brackets\n(see @code{set brackets}), can end sentences.\nThe default value is \"@t{!.?}\".\n\n@item set quickblank\nMake status-bar messages disappear after 1 keystroke instead of after 20.\nNote that option @option{constantshow} overrides this.\nWhen option @option{minibar} or @option{zero} is in effect,\n@option{quickblank} makes a message disappear after\n0.8 seconds instead of after the default 1.5 seconds.\n\n@item set quotestr \"@var{regex}\"\nSet the regular expression for matching the quoting part of a line.\nThe default value is \"@t{^([@w{ }\\t]*([!#%:;>|@}]|//))+}\".\n(Note that @code{\\t} stands for a literal Tab character.)\nThis makes it possible to rejustify blocks of quoted text when composing\nemail, and to rewrap blocks of line comments when writing source code.\n\n@item set rawsequences\nInterpret escape sequences directly, instead of asking @code{ncurses}\nto translate them. (If you need this option to get some keys to work\nproperly, it means that the terminfo terminal description that is used\ndoes not fully match the actual behavior of your terminal. This can\nhappen when you ssh into a BSD machine, for example.)\nUsing this option disables @command{nano}'s mouse support.\n\n@item set rebinddelete\nInterpret the @kbd{Delete} and @kbd{Backspace} keys differently so that\nboth work properly. You should only use this option when on your system\neither @kbd{Backspace} acts like Delete or @kbd{Delete} acts like Backspace.\n\n@item set regexp\nDo regular-expression searches by default.\nRegular expressions in @command{nano} are of the extended type (ERE).\n\n@item set saveonexit\nSave a changed buffer automatically on exit (@kbd{^X}); don't prompt.\n\n@item set scrollercolor @var{fgcolor},@var{bgcolor}\nUse this color combination for the indicator alias “scrollbar”.\n@xref{@code{set keycolor}} for valid color names.\n\n@item set selectedcolor [bold,][italic,]@var{fgcolor},@var{bgcolor}\nUse this color combination for selected text.\n@xref{@code{set keycolor}} for valid color names.\n\n@item set showcursor\nPut the cursor on the highlighted item in the file browser, and show\nthe cursor in the help viewer, to aid braille users and people with\npoor vision.\n\n@item set smarthome\nMake the Home key smarter. When Home is pressed anywhere but at the\nvery beginning of non-whitespace characters on a line, the cursor jumps\nto that beginning (either forwards or backwards). If the cursor is\nalready at that position, it jumps to the true beginning of the line.\n\n@item set softwrap\nDisplay lines that exceed the screen's width over multiple screen lines.\n(You can make this soft-wrapping occur at whitespace instead of rudely at\nthe screen's edge, by using also @code{set atblanks}.)\n\n@item set solosidescroll\nWhen the cursor approaches the right edge of the edit window, scroll only the\ncurrent line sideways by a large amount, instead of scrolling all visible lines\nsideways by just the amount needed to keep the cursor in view.\nThis latter whole-window smooth sideways scrolling is the new default behavior.\nThe single-line jerky sideways scrolling enabled by this option was the old\nbehavior --- the only behavior that @command{nano} knew.\n\n@item set speller \"@var{program} [@var{argument} @dots{}]\"\nUse the given program to do spell checking and correcting.\n@xref{@option{--speller}} for details.\n\n@item set spotlightcolor [bold,][italic,]@var{fgcolor},@var{bgcolor}\nUse this color combination for highlighting a search match.\nThe default value is @t{black,lightyellow}.\n@xref{@code{set keycolor}} for valid color names.\n\n@item set stateflags\nUse the top-right corner of the screen for showing some state flags:\n@code{I} when auto-indenting, @code{M} when the mark is on, @code{L} when\nhard-wrapping (breaking long lines), @code{R} when recording a macro,\nand @code{S} when soft-wrapping.\nWhen the buffer is modified, a star (@code{*}) is shown after the\nfilename in the center of the title bar.\n\n@item set statuscolor [bold,][italic,]@var{fgcolor},@var{bgcolor}\nUse this color combination for the status bar.\n@xref{@code{set keycolor}} for valid color names.\n\n@item set stripecolor [bold,][italic,]@var{fgcolor},@var{bgcolor}\nUse this color combination for the vertical guiding stripe.\n@xref{@code{set keycolor}} for valid color names.\n\n@item set tabsize @var{number}\nUse a tab size of @var{number} columns. The value of @var{number} must be\ngreater than 0. The default value is @t{8}.\n\n@item set tabstospaces\nConvert each typed tab to spaces --- to the number of spaces\nthat a tab at that position would take up.\n(Note: pasted tabs are not converted.)\n\n@item set titlecolor [bold,][italic,]@var{fgcolor},@var{bgcolor}\nUse this color combination for the title bar.\n@xref{@code{set keycolor}} for valid color names.\n\n@item set trimblanks\nRemove trailing whitespace from wrapped lines when automatic\nhard-wrapping occurs or when text is justified.\n\n@item set unix\nSave a file by default in Unix format. This overrides nano's\ndefault behavior of saving a file in the format that it had.\n(This option has no effect when you also use @code{set noconvert}.)\n\n@anchor{Whitespace}\n@item set whitespace \"@var{characters}\"\nSet the two characters used to indicate the presence of tabs and\nspaces. They must be single-column characters. The default pair\nfor a UTF-8 locale is @t{\"»·\"}, and for other locales @t{\">.\"}.\n\n@item set wordbounds\nDetect word boundaries differently by treating punctuation\ncharacters as part of a word.\n\n@item set wordchars \"@var{characters}\"\nSpecify which other characters (besides the normal alphanumeric ones)\nshould be considered as parts of words. When using this option, you\nprobably want to unset @code{wordbounds}.\n\n@item set zap\nLet an unmodified @kbd{Backspace} or @kbd{Delete} erase the marked region\n(instead of a single character, and without affecting the cutbuffer).\n\n@item set zero\nHide all elements of the interface (title bar, status bar, and help lines)\nand use all rows of the terminal for showing the contents of the buffer.\nThe status bar appears only when there is a significant message,\nand disappears after 1.5 seconds or upon the next keystroke.\nWith @kbd{M-Z} the title bar plus status bar can be toggled.\nWith @kbd{M-X} the help lines.\n\n@end table\n\n@node Syntax highlighting\n@section Syntax highlighting\n\nColoring the different syntactic elements of a file\nis done via regular expressions (see the @code{color} command below).\nThis is inherently imperfect, because regular expressions are not\npowerful enough to fully parse a file. Nevertheless, regular\nexpressions can do a lot and are easy to make, so they are a\ngood fit for a small editor like @command{nano}.\n\nSee @file{/usr/share/nano/} and @file{/usr/share/nano/extra/}\nfor the syntax-coloring definitions that are available out of the box.\n\nAll regular expressions in @command{nano} are POSIX extended regular expressions\n(ERE). This means that @code{.}, @code{?}, @code{*}, @code{+}, @code{^},\n@code{$}, and several other characters are special.\nThe period @code{.} matches any single character,\n@code{?} means the preceding item is optional,\n@code{*} means the preceding item may be matched zero or more times,\n@code{+} means the preceding item must be matched one or more times,\n@code{^} matches the beginning of a line, and @code{$} the end,\n@code{\\<} matches the start of a word, and @code{\\>} the end,\nand @code{\\s} matches a blank.\nIt also means that lookahead and lookbehind are not possible.\nA complete explanation can be found in the manual of GNU grep:\n@code{info grep regular}.\n\nEach regular expression in a @file{nanorc} file should be wrapped in\ndouble quotes (@code{\"\"}). Multiple regular expressions can follow\neach other on a line by separating them with blanks. This means that\na regular expression cannot contain a double quote followed by a blank.\nWhen you need this combination inside a regular expression,\nthen either the double quote or the blank should be put\nbetween square brackets (@code{[]}).\n\nA separate syntax can be defined for each kind of file\nvia the following commands in a nanorc file:\n\n@table @code\n\n@item syntax @var{name} [\"@var{fileregex}\" @dots{}]\nStart the definition of a syntax with this @var{name}.\nAll subsequent @code{color} and other such commands\nare added to this syntax, until a new @code{syntax}\ncommand is encountered.\n\nWhen @command{nano} is run, this syntax is automatically\nactivated (for the relevant buffer) if the absolute filename\nmatches the extended regular expression @var{fileregex}.\nOr the syntax can be explicitly activated (for all buffers)\nby using the @option{-Y} or @option{--syntax}\ncommand-line option followed by the @var{name}.\n\nThe @code{default} syntax is special: it takes no @var{fileregex},\nand applies to files that don't match any syntax's regexes.\nThe @code{none} syntax is reserved; specifying it on the\ncommand line is the same as not having a syntax at all.\n\n@item header \"@var{regex}\" @dots{}\nIf from all defined syntaxes no @var{fileregex} matched, then compare\nthis @var{regex} (or regexes) against the first line of the current file,\nto determine whether this syntax should be used for it.\n\n@item magic \"@var{regex}\" @dots{}\nIf no @var{fileregex} matched and no @code{header} regex matched\neither, then compare this @var{regex} (or regexes) against the\nresult of querying the @code{magic} database about the current\nfile, to determine whether this syntax should be used for it.\n(This querying is done only when @code{libmagic} is actually installed\non the system and @option{--magic} or @code{set magic} was given.)\n\n@item formatter @var{program} [@var{argument} @dots{}]\nRun the given @var{program} on the full contents of the current buffer.\n\n@item linter @var{program} [@var{argument} @dots{}]\nUse the given @var{program} to do a syntax check on the current buffer.\n\n@item comment \"@var{string}\"\nUse the given string for commenting and uncommenting lines.\nIf the string contains a vertical bar or pipe character (@t{|}),\nthis designates bracket-style comments; for example, \"@t{/*|*/}\" for\nCSS files. The characters before the pipe are prepended to the line and the\ncharacters after the pipe are appended at the end of the line. If no pipe\ncharacter is present, the full string is prepended; for example, \"@t{#}\"\nfor Python files. If nothing is specified between the double quotes, then\nthe comment/uncomment function is disabled; for example, \"\" for JSON.\nThe default value is \"@t{#}\".\n\n@item tabgives \"@var{string}\"\nMake the key produce the given @var{string}. Useful for languages like\nPython that want to see only spaces for indentation.\nThis overrides the setting of the @code{tabstospaces} option.\n\n@item color [bold,][italic,]@var{fgcolor},@var{bgcolor} \"@var{regex}\" @dots{}\nPaint all pieces of text that match the extended regular expression \"regex\"\nwith the given foreground and background colors, at least one of which must\nbe specified. Valid color names are:\n@code{red}, @code{green}, @code{blue},\n@code{magenta}, @code{yellow}, @code{cyan},\n@code{white}, and @code{black}.\nEach of these eight names may be prefixed with the word\n@code{light} to get a brighter version of that color.\nThe word @code{grey} or @code{gray} may be used\nas a synonym for @code{lightblack}.\nOn a Linux console, @code{light} does not have\nany effect for a background color.\n\nOn terminal emulators that can do at least 256 colors,\nother valid (but unprefixable) color names are:\n@code{pink}, @code{purple}, @code{mauve},\n@code{lagoon}, @code{mint}, @code{lime},\n@code{peach}, @code{orange}, @code{latte},\n@code{rosy}, @code{beet}, @code{plum}, @code{sea},\n@code{sky}, @code{slate}, @code{teal}, @code{sage},\n@code{brown}, @code{ocher}, @code{sand}, @code{tawny},\n@code{brick}, @code{crimson}, and @code{normal}\n--- where @code{normal} means the default foreground or background color.\nOn such emulators, the color may also be specified as a three-digit hexadecimal\nnumber prefixed with @code{#}, with the digits representing the amounts of red,\ngreen, and blue, respectively. This tells @command{nano} to select from the\navailable palette the color that approximates the given values.\n\nThe color pair may be preceded by @code{bold} and/or @code{italic}\n(separated by commas) to get a bold and/or slanting typeface,\nif your terminal can do those.\n\nAll coloring commands are applied in the order in which they are specified,\nwhich means that later commands can recolor stuff that was colored earlier.\n\n@item icolor [bold,][italic,]@var{fgcolor},@var{bgcolor} \"@var{regex}\" @dots{}\nSame as above, except that the matching is case insensitive.\n\n@item color [bold,][italic,]@var{fgcolor},@var{bgcolor} start=\"@var{fromrx}\" end=\"@var{torx}\"\nPaint all pieces of text whose start matches extended regular expression\n@var{fromrx} and whose end matches extended regular expression @var{torx}\nwith the given foreground and background colors, at least one of\nwhich must be specified. This means that, after an initial instance of\n@var{fromrx}, all text until the first instance of @var{torx} is colored.\nThis allows syntax highlighting to span multiple lines.\n\n@item icolor [bold,][italic,]@var{fgcolor},@var{bgcolor} start=\"@var{fromrx}\" end=\"@var{torx}\"\nSame as above, except that the matching is case insensitive.\n\n@item include \"@var{syntaxfile}\"\nRead in self-contained color syntaxes from @var{syntaxfile}. Note that\nsuch a syntax file may contain only the above commands, from @code{syntax}\nto @code{icolor}.\n\n@item extendsyntax @var{name} @var{command} @var{argument} @dots{}\nExtend the syntax previously defined as \"@var{name}\" with another @var{command}.\nThis allows you to add a new @code{color}, @code{icolor}, @code{header},\n@code{magic}, @code{formatter}, @code{linter}, @code{comment},\nor @code{tabgives} command to an already\ndefined syntax --- useful when you want to slightly improve a syntax defined\nin one of the system-installed files (which normally are not writable).\n\n@end table\n\n@node Rebinding keys\n@section Rebinding keys\n\nKey bindings can be changed via the following three commands in a\nnanorc file:\n\n@table @code\n\n@item bind key function menu\nRebinds @code{key} to @code{function} in the context of @code{menu}\n(or in all menus where the function exists when @code{all} is used).\n\n@item bind key \"string\" menu\nMakes @code{key} produce @code{string} in the context of @code{menu}\n(or in all menus where the key exists when @code{all} is used).\nBesides literal text and/or control codes, the @code{string} may contain\nfunction names between braces. These functions are invoked when the\nkey is typed. To include a literal opening brace, use @code{@{@{@}}.\n\n@item unbind key menu\nUnbinds @code{key} from @code{menu}\n(or from all menus where the key exists when @code{all} is used).\n\n@end table\n\nNote that @code{bind key \"@{function@}\" menu} is equivalent to\n@code{bind key function menu}, except that for the latter form\n@command{nano} checks the availability of the @code{function}\nin the given @code{menu} at startup time (and reports an error if\nit does not exist there), whereas for the first form @command{nano}\nchecks at execution time that the @code{function} exists but not\nwhether it makes any sense in the current menu. The user has to take\ncare that a function name between braces (or any sequence of them)\nis appropriate. Strange behavior or even a crash can result when\nthe braced name is unfitting.\n\n@sp 1\nThe format of @code{key} should be one of:\n\n@indentedblock\n@table @asis\n\n@item @code{^@var{X}}\nwhere @var{X} is a Latin letter, or one of several\nASCII characters (@@, ], \\, ^, _), or the word \"Space\".\nExample: @code{^C}.\n\n@item @code{M-@var{X}}\nwhere @var{X} is any ASCII character (except [),\nor the word \"Space\", \"Left\", \"Right\", \"Up\", or \"Down\".\nExample: @code{M-8}.\n\n@item @code{Sh-M-@var{X}}\nwhere @var{X} is a Latin letter.\nExample: @code{Sh-M-U}.\nBy default, each Meta+letter keystroke does the same as the corresponding\nShift+Meta+letter. But when any Shift+Meta bind is made, that will\nno longer be the case, for all letters.\n\n@item @code{F@var{n}}\nwhere @var{n} is a numeric value from 1 to 24.\nExample: @code{F10}.\n(Often, @code{F13} to @code{F24} can be typed as @code{F1} to @code{F12}\nwith Shift.)\n\n@item @code{Ins} or @code{Del}\n\n@end table\n@end indentedblock\n\n@sp 1\nRebinding @code{^M} (Enter) or @code{^I} (Tab) is probably not a good idea.\nRebinding @code{^[} (Esc) is not possible, because its keycode\nis the starter byte of Meta keystrokes and escape sequences.\nRebinding any of the dedicated cursor-moving keys (Home, End,\nPageUp, PageDown, and the arrows) is not possible.\nOn some terminals it's not possible to rebind @code{^H} (unless @code{--raw}\nis used) because its keycode is identical to that of the Backspace key.\n\n@sp 1\nValid names for the @code{function} to be bound are:\n\n@table @code\n\n@item help\nInvokes the help viewer.\n\n@item cancel\nCancels the current command.\n\n@item exit\nExits from the program (or from the help viewer or file browser).\n\n@item writeout\nWrites the current buffer to disk, asking for a name.\n\n@item savefile\nWrites the current file to disk without prompting.\n\n@item insert\nInserts a file into the current buffer (at the current cursor position),\nor into a new buffer when option @code{multibuffer} is set.\n\n@item whereis\nStarts a forward search for text in the current buffer --- or for filenames\nmatching a string in the current list in the file browser.\n\n@item wherewas\nStarts a backward search for text in the current buffer --- or for filenames\nmatching a string in the current list in the file browser.\n\n@item findprevious\nSearches the next occurrence in the backward direction.\n\n@item findnext\nSearches the next occurrence in the forward direction.\n\n@item replace\nInteractively replaces text within the current buffer.\n\n@item cut\nCuts and stores the current line (or the marked region).\n\n@item copy\nCopies the current line (or the marked region) without deleting it.\n\n@item paste\nPastes the currently stored text into the current buffer at the\ncurrent cursor position.\n\n@item zap\nThrows away the current line (or the marked region).\n(This function is bound by default to @kbd{Alt+Delete}.)\n\n@item chopwordleft\nDeletes from the cursor position to the beginning of the preceding word.\n(This function is bound by default to @kbd{Shift+Ctrl+Delete}. If your terminal\nproduces @code{^H} for @kbd{Ctrl+Backspace}, you can make @kbd{Ctrl+Backspace} delete\nthe word to the left of the cursor by rebinding @kbd{^H} to this function.)\n\n@item chopwordright\nDeletes from the cursor position to the beginning of the next word.\n(This function is bound by default to @kbd{Ctrl+Delete}.)\n\n@item cutrestoffile\nCuts all text from the cursor position till the end of the buffer.\n\n@item mark\nSets the mark at the current position, to start selecting text.\nOr, when it is set, unsets the mark.\n\n@item location\nReports the current position of the cursor in the buffer:\nthe line, column, and character positions.\n\n@item wordcount\nCounts and reports on the status bar the number of lines, words,\nand characters in the current buffer (or in the marked region).\n\n@item execute\nPrompts for a program to execute. The program's output will be inserted\ninto the current buffer --- or into a new buffer when @kbd{M-F} is toggled.\nWhen the program's name is preceded by a pipe symbol (@kbd{|}), then the\ncurrent buffer (or the marked region) is piped to the program, and the\noutput of the program replaces the buffer (or the marked region).\n\n@item speller\nInvokes a spell-checking program, either the default @command{hunspell}\nor GNU @command{spell}, or the one defined by @option{--speller} or\n@code{set speller}.\n\n@item formatter\nInvokes a full-buffer-processing program (if the active syntax defines one).\n(The current buffer is written out to a temporary file, the program\nis run on it, and then the temporary file is read back in, replacing\nthe contents of the buffer.)\n\n@item linter\nInvokes a syntax-checking program (if the active syntax defines one).\nIf this program produces lines of the form \"filename:linenum:charnum:\nsome message\", then the cursor is put at the indicated position\nin the mentioned file while showing \"some message\" on the status bar.\nYou can move from message to message with @kbd{PgUp} and @kbd{PgDn},\nand leave linting mode with @kbd{^C} or @kbd{Enter}.\n\n@item justify\nJustifies the current paragraph (or the marked region).\nA paragraph is a group of contiguous lines that, apart from possibly\nthe first line, all have the same indentation. The beginning of a\nparagraph is detected by either this lone line with a differing\nindentation or by a preceding blank line.\n\n@item fulljustify\nJustifies the entire current buffer (or the marked region).\n\n@item indent\nIndents (shifts to the right) the current line or the marked lines.\n\n@item unindent\nUnindents (shifts to the left) the current line or the marked lines.\n\n@item comment\nComments or uncomments the current line or the marked lines,\nusing the comment style specified in the active syntax.\n\n@item complete\nCompletes (when possible) the fragment before the cursor\nto a full word found elsewhere in the current buffer.\n\n@item left\nGoes left one position (in the editor or browser).\n\n@item right\nGoes right one position (in the editor or browser).\n\n@item up\nGoes one line up (in the editor or browser).\n\n@item down\nGoes one line down (in the editor or browser).\n\n@item scrollleft\nScrolls the viewport a tabsize to the left, when possible.\n(This function is bound by default to @kbd{M-<}.)\n\n@item scrollright\nScrolls the viewport a tabsize to the right. When needed to keep\nthe cursor visible, it is moved to a longer line in the viewport.\nIf there is no sufficiently longer line, no scroll is made.\n(This function is bound by default to @kbd{M->}.)\n\n@item scrollup\nScrolls the viewport up one row (meaning that the text slides down)\nwhile keeping the cursor in the same text position, if possible.\n(This function is bound by default to @kbd{M-Up}.\nIf @kbd{Alt+Up} does nothing on your Linux console, see the FAQ:\n@url{https://nano-editor.org/dist/latest/faq.html#4.1}.)\n\n@item scrolldown\nScrolls the viewport down one row (meaning that the text slides up)\nwhile keeping the cursor in the same text position, if possible.\n(This function is bound by default to @kbd{M-Down}.)\n\n@item center\nScrolls the line with the cursor to the middle of the viewport.\n\n@item cycle\nScrolls the line with the cursor first to the middle of the viewport,\nthen to the top, then to the bottom.\n\n@item prevword\nMoves the cursor to the beginning of the previous word.\n\n@item nextword\nMoves the cursor to the beginning of the next word.\n\n@item home\nMoves the cursor to the beginning of the current line.\n\n@item end\nMoves the cursor to the end of the current line.\n\n@item beginpara\nMoves the cursor to the beginning of the current paragraph.\n\n@item endpara\nMoves the cursor to the end of the current paragraph.\n\n@item prevblock\nMoves the cursor to the beginning of the current or preceding block of text.\n(Blocks are separated by one or more blank lines.)\n\n@item nextblock\nMoves the cursor to the beginning of the next block of text.\n\n@item toprow\nMoves the cursor to the first row in the viewport.\n\n@item bottomrow\nMoves the cursor to the last row in the viewport.\n\n@item pageup\nGoes up one screenful.\n\n@item pagedown\nGoes down one screenful.\n\n@item firstline\nGoes to the first line of the file.\n\n@item lastline\nGoes to the last line of the file.\n\n@item gotoline\nGoes to a specific line (and column if given).\nA negative number counts from the end of the buffer (and end of the line).\nPutting @code{++} or @code{--} before the first number will jump the given\nnumber of lines forward or backward.\n\n@item findbracket\nMoves the cursor to the bracket (or brace or parenthesis, etc.) that matches\n(pairs) with the one under the cursor. @xref{@code{set matchbrackets}}.\n\n@item anchor\nPlaces an anchor at the current line, or removes it when already present.\n(An anchor is visible when line numbers are activated.)\n\n@item prevanchor\nGoes to the first anchor before the current line.\n\n@item nextanchor\nGoes to the first anchor after the current line.\n\n@item prevbuf\nSwitches to editing/viewing the previous buffer when multiple buffers are open.\n\n@item nextbuf\nSwitches to editing/viewing the next buffer when multiple buffers are open.\n\n@item verbatim\nInserts the next keystroke verbatim into the file, or begins Unicode input\nwhen a hexadecimal digit is typed (@pxref{Entering text} for details).\n\n@item tab\nInserts a tab at the current cursor location.\n\n@item enter\nInserts a new line below the current one.\n\n@item delete\nDeletes the character under the cursor.\n\n@item backspace\nDeletes the character before the cursor.\n\n@item recordmacro\nStarts the recording of keystrokes --- the keystrokes are stored\nas a macro. When already recording, the recording is stopped.\n\n@item runmacro\nReplays the keystrokes of the last recorded macro.\n\n@item undo\nUndoes the last performed text action (add text, delete text, etc).\n\n@item redo\nRedoes the last undone action (that is: it undoes an undo).\n\n@item refresh\nRefreshes the screen.\n\n@item suspend\nSuspends the editor and returns control to the shell\n(until you tell the process to resume execution with @kbd{fg}).\n\n@item casesens\nToggles whether searching/replacing ignores or respects the case of\nthe given characters.\n\n@item regexp\nToggles whether searching/replacing uses literal strings or regular expressions.\n\n@item backwards\nToggles whether searching/replacing goes forward or backward.\n\n@item older\nRetrieves the previous (earlier) entry at a prompt.\n\n@item newer\nRetrieves the next (later) entry at a prompt.\n\n@item flipreplace\nToggles between searching for something and replacing something.\n\n@item flipgoto\nToggles between searching for text and targeting a line number.\n\n@item flipexecute\nSwitches from inserting a file to executing a command.\n\n@item flippipe\nWhen executing a command, toggles whether the current buffer (or marked\nregion) is piped to the command.\n\n@item flipnewbuffer\nToggles between inserting into the current buffer and into a new\nempty buffer.\n\n@item flipconvert\nWhen reading in a file, toggles between converting and not converting\nit from DOS format. Converting is the default.\n\n@item dosformat\nWhen writing a file, switches to writing DOS format (CR+LF line endings).\n\n@item append\nWhen writing a file, appends to the end instead of overwriting.\n\n@item prepend\nWhen writing a file, “prepends” (writes at the beginning) instead of overwriting.\n\n@item backup\nWhen writing a file, creates a backup of the current file.\n\n@item discardbuffer\nDiscards the current buffer without saving (when in the Write Out menu).\nWhen it was the last buffer, then @command{nano} exits with error status 2.\n\n@item browser\nStarts the file browser (in the Read File and Write Out menus),\nallowing to select a file from a list.\n\n@item gotodir\nGoes to a directory to be specified, allowing to browse anywhere\nin the filesystem.\n\n@item firstfile\nGoes to the first file in the list when using the file browser.\n\n@item lastfile\nGoes to the last file in the list when using the file browser.\n\n@item nohelp\nToggles the presence of the two-line list of key bindings at the bottom of the screen.\n(This toggle is special: it is available in all menus except the help viewer\nand the linter. All further toggles are available in the main menu only.)\n\n@item zero\nToggles the presence of title bar and status bar.\n\n@item constantshow\nToggles the constant reporting (on the status bar)\nof the current line, column, and character positions.\n\n@item softwrap\nToggles the displaying of overlong lines on multiple screen lines.\n\n@item linenumbers\nToggles the display of line numbers in front of the text.\n\n@item whitespacedisplay\nToggles the showing of whitespace.\n\n@item nosyntax\nToggles syntax highlighting.\n\n@item smarthome\nToggles the smartness of the Home key.\n\n@item autoindent\nToggles whether a newly created line will contain the same amount of leading\nwhitespace as the preceding line --- or as the next line if the preceding line\nis the beginning of a paragraph.\n\n@item cutfromcursor\nToggles whether cutting text cuts the whole line or just from the current cursor\nposition to the end of the line.\n\n@item breaklonglines\nToggles whether the overlong part of a line is hard-wrapped to the next line.\n\n@item tabstospaces\nToggles whether typed tabs are converted to spaces.\n\n@item mouse\nToggles mouse support.\n\n@end table\n\n@sp 1\nValid names for @code{menu} are:\n\n@table @code\n\n@item main\nThe main editor window where text is entered and edited.\n\n@item help\nThe help-viewer menu.\n\n@item search\nThe search menu (AKA whereis).\n\n@item replace\nThe 'search to replace' menu.\n\n@item replacewith\nThe 'replace with' menu, which comes up after 'search to replace'.\n\n@item yesno\nThe 'yesno' menu, where the Yes/No/All/Cancel question is asked.\n\n@item gotoline\nThe 'goto line (and column)' menu.\n\n@item writeout\nThe 'write file' menu.\n\n@item insert\nThe 'insert file' menu.\n\n@item browser\nThe 'file browser' menu, for selecting a file to be opened or\ninserted or written to.\n\n@item whereisfile\nThe 'search for a file' menu in the file browser.\n\n@item gotodir\nThe 'go to directory' menu in the file browser.\n\n@item execute\nThe menu for inserting the output from an external command,\nor for filtering the buffer (or the marked region) through\nan external command, or for executing one of several tools.\n\n@item spell\nThe menu of the integrated spell checker where the user can edit a misspelled word.\n\n@item linter\nThe linter menu, which allows jumping through the linting messages.\n\n@item all\nA special name that encompasses all menus. For @code{bind} it means\nall menus where the specified @code{function} exists; for @code{unbind}\nit means all menus where the specified @code{key} exists.\n\n@end table\n\n\n@node Pico compatibility\n@chapter Pico compatibility\n\n@command{nano} emulates Pico quite closely, but there\nare some differences between the two editors:\n\n@table @code\n\n@item Hard-Wrapping\nUnlike Pico, @command{nano} does not automatically hard-wrap the current\nline when it becomes overlong during typing. This hard-wrapping can be\nswitched on with the @option{--breaklonglines} option. With that option,\n@command{nano} by default breaks lines at screen width minus eight columns,\nwhereas Pico does it at screen width minus six columns. You can make\n@command{nano} do as Pico by using @option{--fill=-6}.\n\n@item Scrolling\nBy default, @command{nano} scrolls just one line (instead of half\na screen) when the cursor is moved to a line that is just out of view.\nAnd when paging up or down, @command{nano} keeps the cursor in the same\nscreen position as much as possible, instead of always placing it on the\nfirst line of the viewport. The Pico-like behavior can be obtained\nwith the @option{--jumpyscrolling} option.\n\n@item Edit Area\nPico never uses the line directly below the title bar, leaving it always\nblank. @command{nano} includes this line in the editing area, in order\nto not waste space, and because in this way it is slightly clearer where\nthe text starts. If you are accustomed to this line being empty, you can\nget it back with the @option{--emptyline} option.\n\n@item Interactive Replace\nInstead of allowing you to replace either just one occurrence of a search\nstring or all of them, @command{nano}'s replace function is interactive:\nit pauses at each found search string and asks whether to replace this\ninstance. You can then choose Yes, or No (skip this one), or All (don't\nask any more), or Cancel (stop with replacing).\n\n@item Search and Replace History\nWhen the option @option{-H} or @option{--historylog} is given (or set in\na nanorc file), text entered as search or replace strings is stored.\nThese strings can be accessed with the up/down arrow keys at their\nrespective prompts, or you can\ntype the first few characters and then use @kbd{Tab} to cycle through the\nmatching strings. A retrieved string can subsequently be edited.\n\n@item Position History\nWhen the option @option{-P} or @option{--positionlog} is given (or set in\na nanorc file), @command{nano} will store the position of the cursor\nwhen you close a file, and will place the cursor in that position\nagain when you later reopen the file.\n\n@item Current Cursor Position\nThe output of the \"Display Cursor Position\" command (@kbd{^C}) displays\nnot only the current line and character position of the cursor,\nbut also (between the two) the current column position.\n\n@item Spell Checking\nIn the internal spell checker misspelled words are sorted alphabetically\nand trimmed for uniqueness, such that the strings 'Aplpe' and 'aplpe'\nwill be offered for correction separately.\n\n@item Writing Selected Text to Files\nWhen using the Write-Out key (@kbd{^O}), text that has been selected using the\nmarking key (@kbd{^^}) can not just be written out to a new (or existing) file,\nit can also be appended or prepended to an existing file.\n\n@item Reading Text from a Command\nWhen using the Read-File key (@kbd{^R}), @command{nano} can not just read a file,\nit can also read the output of a command to be run (@kbd{^X}).\n\n@item Reading from Working Directory\nBy default, Pico reads files from the user's home directory (when\nusing @kbd{^R}), but it writes files to the current working directory\n(when using @kbd{^O}). @command{nano} makes this symmetrical: always reading\nfrom and writing to the current working directory --- the directory\nthat @command{nano} was started in.\n\n@item File Browser\nIn the file browser, @command{nano} does not implement the Add, Copy,\nRename, and Delete commands that Pico provides. In @command{nano} the\nbrowser is just a file browser, not a file manager.\n\n@item Toggles\nMany options which alter the functionality of the program can be\n\"toggled\" on or off using Meta key sequences, meaning the program does\nnot have to be restarted to turn a particular feature on or off.\n@xref{Feature toggles} for a list of options that can be toggled.\nOr see the list at the end of the main internal help text (@kbd{^G}) instead.\n\n@end table\n\n\n@node Building and its options\n@chapter Building and its options\n\nBuilding @command{nano} from source is straightforward if you are\nfamiliar with compiling programs with autoconf support:\n\n@blankline\n@example\n tar -xf nano-x.y.tar.gz\n cd nano-x.y\n ./configure\n make\n make install\n@end example\n@blankline\n\nThe possible options to @code{./configure} are:\n\n@table @code\n\n@item --disable-browser\nExclude the file browser that can be called with @kbd{^T} when\nwanting to read or write a file.\n\n@item --disable-color\nExclude support for syntax coloring. This also eliminates the @option{-Y}\ncommand-line option, which allows choosing a specific syntax.\n\n@item --disable-comment\nExclude the single-keystroke comment/uncomment function (@w{@kbd{M-3}}).\n\n@item --disable-extra\nExclude the Easter egg: a crawl of major contributors.\n\n@item --disable-formatter\nExclude the code for calling a formatting tool.\n\n@item --disable-help\nExclude the help texts (@kbd{^G}). This makes the binary much smaller,\nbut also makes it difficult for new users to learn more than very basic\nthings about using the editor.\n\n@item --disable-histories\nExclude the code for handling the history files: the search and\nreplace strings that were used, the commands that were executed,\nand the cursor position at which each file was closed.\nThis also eliminates the @option{-H} and @option{-P} command-line\noptions, which switch on the storing of search/replace strings,\nexecuted commands, and cursor positions.\n\n@item --disable-justify\nExclude the text-justification functions (@kbd{^J} and @kbd{M-J}).\n\n@item --disable-libmagic\nExclude the code for using the library of magic-number tests (for\ndetermining the file type and thus which syntax to use for coloring ---\nin most cases the regexes for filename and header line will be enough).\n\n@item --disable-linenumbers\nExclude the ability to show line numbers. This also eliminates\nthe @option{-l} command-line option, which turns line numbering on.\n\n@item --disable-linter\nExclude the code for calling a linting tool.\n\n@item --disable-mouse\nExclude all mouse functionality. This also eliminates the @option{-m}\ncommand-line option, which enables the mouse functionality.\n\n@item --disable-multibuffer\nExclude support for opening multiple files at a time and switching\nbetween them. This also eliminates the @option{-F} command-line option,\nwhich causes a file to be read into a separate buffer by default.\n\n@item --disable-nanorc\nExclude support for reading the nanorc files at startup. With such\nsupport, you can store custom settings in a system-wide and a per-user\nnanorc file rather than having to pass command-line options to get\nthe desired behavior. @xref{Nanorc files} for more info.\nDisabling this also eliminates the @option{-I} command-line option,\nwhich inhibits the reading of nanorc files.\n\n@item --disable-operatingdir\nExclude the code for setting an operating directory. This also eliminates\nthe @option{-o} command-line option, which sets the operating directory.\n\n@item --disable-speller\nExclude the code for spell checking. This also eliminates the @option{-s}\ncommand-line option, which allows specifying an alternate spell checker.\n\n@item --disable-tabcomp\nExclude tab completion (when nano asks for a filename or search string\nor replace string or command to execute).\n\n@item --disable-wordcomp\nExclude word completion (@kbd{^]}).\n\n@item --disable-wrapping\nExclude all hard-wrapping of overlong lines. This also eliminates the\n@option{-b} and @option{-w} command-line options, which switch automatic\nlong-line wrapping on and off, respectively.\n\n@item --enable-tiny\nThis option implies all of the above. It also disables some other\ninternals of the editor, like the function toggles, the marking of text,\nthe undo/redo code, line anchors, the recording and playback of a macro,\nsoftwrapping, and the cut-to-end-of-line code. These things stay disabled\nalso when using the enabling counterpart of the above options together with\n@option{--enable-tiny} to switch specific features back on.\n\n@item --enable-debug\nInclude some code for runtime debugging output. This can get messy, so\nchances are you only want this feature when you're working on the nano source.\n\n@item --disable-nls\nExclude Native Language support. This disables the use of any\navailable GNU @command{nano} translations.\n\n@item --enable-utf8\nInclude support for handling and displaying Unicode files.\nThis requires a \"wide\" version of the curses library.\n\n@item --disable-utf8\nExclude support for handling and displaying Unicode files. Normally the\nconfigure script auto-detects whether to enable UTF-8 support or not.\nYou can use this or the previous option to override that detection.\n\n@item --enable-altrcname=@var{name}\nUse the file with the given @var{name} (in the user's home directory)\nas nano's settings file, instead of the default @code{.nanorc}.\n\n@end table\n\n@html\n
\n@end html\n\n@iftex\n@contents\n@end iftex\n\n@bye\n" }, { "path": "doc/nanorc.5", "content": ".\\\" Copyright (C) 2003-2011, 2013-2026 Free Software Foundation, Inc.\n.\\\"\n.\\\" This document is dual-licensed. You may distribute and/or modify it\n.\\\" under the terms of either of the following licenses:\n.\\\"\n.\\\" * The GNU General Public License, as published by the Free Software\n.\\\" Foundation, version 3 or (at your option) any later version. You\n.\\\" should have received a copy of the GNU General Public License\n.\\\" along with this program. If not, see\n.\\\" .\n.\\\"\n.\\\" * The GNU Free Documentation License, as published by the Free\n.\\\" Software Foundation, version 1.2 or (at your option) any later\n.\\\" version, with no Invariant Sections, no Front-Cover Texts, and no\n.\\\" Back-Cover Texts. You should have received a copy of the GNU Free\n.\\\" Documentation License along with this program. If not, see\n.\\\" .\n.\\\"\n.TH NANORC 5 \"April 2026\" \"GNU nano 9.0\"\n\n.SH NAME\nnanorc \\- GNU nano's configuration file\n\n.SH DESCRIPTION\nThe \\fInanorc\\fR files contain the default settings for \\fBnano\\fR,\na small and friendly text editor. During startup, if \\fB\\-\\-rcfile\\fR\nis not given, \\fBnano\\fR reads two files: first the system-wide settings,\nfrom \\fI/etc/\\:nanorc\\fR (the exact path might be different on your system),\nand then the user-specific settings, either from \\fI\\[ti]/.nanorc\\fR or from\n\\fI\\%$XDG_CONFIG_HOME/\\:nano/\\:nanorc\\fR or from \\fI\\[ti]\\%/.config/\\:nano/\\:nanorc\\fR,\nwhichever is encountered first. If \\fB\\-\\-rcfile\\fR is given,\n\\fBnano\\fR reads just the specified settings file.\n\n.SH NOTICES\nSince version 9.0, all lines are scrolled horizontally together\n(when the cursor approaches the edge), by just the amount needed,\ninstead of scrolling only the current line by a large step.\nIf you prefer the old behavior, you can use \\fB\\-\\-solo\\fR on the\ncommand line or \\fBset \\%solosidescroll\\fR in your \\fInanorc\\fR.\n.sp\nAlso since version 9.0, keystrokes \\fBM\\-<\\fR and \\fBM\\->\\fR have\nbeen reassigned to the \\fBscrollleft\\fR and \\fBscrollright\\fR functions.\nIf you want those keystrokes to do what they did before version 9.0,\nadd these two lines at the end of your \\fInanorc\\fR file:\n.sp\n.RS 4\n.B bind M\\-< prevbuf main\n.br\n.B bind M\\-> nextbuf main\n.RE\n.sp\nSince version 8.0, to be newcomer friendly, \\fB^F\\fR starts a forward search,\n\\fB^B\\fR starts a backward search, \\fBM\\-F\\fR searches the next occurrence\nforward, and \\fBM\\-B\\fR searches the next occurrence backward. If you want\nthose keystrokes to do what they did before version 8.0, add the following\nfour lines at the end of your \\fInanorc\\fR file:\n.sp\n.RS 4\n.B bind ^F forward main\n.br\n.B bind ^B back main\n.br\n.B bind M\\-F formatter main\n.br\n.B bind M\\-B linter main\n.RE\n.sp\n\n.SH OPTIONS\nThe configuration file accepts a series of \\fBset\\fR and \\fBunset\\fR\ncommands, which can be used to configure nano on startup without using\ncommand-line options. Additionally, there are some commands to define\nsyntax highlighting and to rebind keys \\[em] see the two separate sections\non those. \\fBnano\\fR reads one command per line.\nAll commands and keywords should be written in lowercase.\n.sp\nOptions in \\fInanorc\\fR files take precedence over nano's defaults, and\ncommand-line options override \\fInanorc\\fR settings. Also, options that\ndo not take an argument are unset by default. So using the \\fBunset\\fR\ncommand is only needed when wanting to override a setting of the system's\n\\fInanorc\\fR file in your own \\fInanorc\\fR. Options that take an\nargument cannot be unset.\n.sp\nQuotes inside the \\fIcharacters\\fR parameters below should not be escaped.\nThe last double quote on the line will be seen as the closing quote.\n.sp\nThe supported commands and arguments are:\n.TP 3\n.B set afterends\nMake Ctrl+Right and Ctrl+Delete stop at word ends instead of beginnings.\n.TP\n.B set allow_insecure_backup\nWhen backing up files, allow the backup to succeed even if its permissions\ncan't be (re)set due to special OS considerations. You should\nNOT enable this option unless you are sure you need it.\n.TP\n.B set atblanks\nWhen soft line wrapping is enabled, make it wrap lines at blank characters\n(tabs and spaces) instead of always at the edge of the screen.\n.TP\n.B set autoindent\nAutomatically indent a newly created line to the same number of tabs\nand/or spaces as the previous line (or as the next line if the previous\nline is the beginning of a paragraph).\n.TP\n.B set backup\nWhen saving a file, create a backup file by adding a tilde (\\fB\\[ti]\\fR) to\nthe file's name.\n.TP\n.B set backupdir \\fIdirectory\\fR\nMake and keep not just one backup file, but make and keep a uniquely\nnumbered one every time a file is saved \\[em] when backups are enabled\nwith \\fBset \\%backup\\fR or \\fB\\-\\-backup\\fR or \\fB\\-B\\fR.\nThe uniquely numbered files are stored in the specified \\fIdirectory\\fR.\n.TP\n.B set boldtext\nUse bold instead of reverse video for the title bar, status bar,\nprompt bar, mini bar, key combos, line numbers, and selected text.\nThis can be overridden by setting the options \\fB\\%titlecolor\\fR,\n\\fB\\%statuscolor\\fR, \\fB\\%promptcolor\\fR, \\fB\\%minicolor\\fR,\n\\fB\\%keycolor\\fR, \\fB\\%numbercolor\\fR, and/or \\fB\\%selectedcolor\\fR.\n.TP\n.B set bookstyle\nWhen justifying, treat any line that starts with whitespace as the\nbeginning of a paragraph (unless auto-indenting is on).\n.TP\n.BI \"set brackets \"\"\" characters \"\"\"\"\nSet the characters treated as closing brackets when justifying\nparagraphs. This may not include blank characters. Only closing\npunctuation (see \\fBset punct\\fR), optionally followed by the specified\nclosing brackets, can end sentences. The default value is \"\\fB\\[dq]')>]}\\fR\".\n.TP\n.B set breaklonglines\nAutomatically hard-wrap the current line when it becomes overlong \\[em]\nthat is: when it becomes wider than the value given with \\fBset fill\\fR\n(which defaults to the width of the terminal minus eight).\n.TP\n.B set casesensitive\nDo case-sensitive searches by default.\n.TP\n.B set colonparsing\nWhen a filename given on the command line ends in a colon plus digits\nand this filename does not exist, then snip the colon plus digits and\nunderstand the digits as a line number. If the trimmed filename does\nnot exist either, then repeat the process and understand the obtained\ntwo numbers as line and column number. But if the doubly trimmed\nfilename does not exist either, then forget the trimming and accept\nthe original filename as is. To disable this colon parsing for some\nfile, use \\fB+1\\fR or similar before the relevant filename.\n.TP\n.B set constantshow\nConstantly report the cursor position on the status bar.\nThis overrides the option \\fBquickblank\\fR.\n.TP\n.B set cutfromcursor\nUse cut-from-cursor-to-end-of-line by default, instead of cutting the whole line.\n.TP\n.B set emptyline\nDo not use the line below the title bar, leaving it entirely blank.\n.TP\n.B set errorcolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\\fIfgcolor\\fB,\\fIbgcolor\\fR\nUse this color combination for the status bar when an error message is displayed.\nThe default value is \\fBbold,white,red\\fR.\nSee \\fBset \\%titlecolor\\fR for valid color names.\n.TP\n.B set fill \\fInumber\\fR\nSet the target width for justifying and automatic hard-wrapping at this\n\\fInumber\\fR of columns. If the value is 0 or less, wrapping occurs\nat the width of the screen minus \\fInumber\\fR columns, allowing the wrap\npoint to vary along with the width of the screen if the screen is resized.\nThe default value is \\fB\\-8\\fR.\n.TP\n.B set functioncolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\\fIfgcolor\\fB,\\fIbgcolor\\fR\nUse this color combination for the concise function descriptions\nin the two help lines at the bottom of the screen.\nSee \\fBset \\%titlecolor\\fR for more details.\n.TP\n.B set guidestripe \\fInumber\nDraw a vertical stripe at the given column, to help judge the width of the\ntext. (The color of the stripe can be changed with \\fBset \\%stripecolor\\fR.)\n.TP\n.B set historylog\nSave the last hundred search strings and replacement strings and\nexecuted commands, so they can be easily reused in later sessions.\n.TP\n.B set indicator\nDisplay a \\[lq]scrollbar\\[rq] on the righthand side of the edit window.\nIt shows the position of the viewport in the buffer\nand how much of the buffer is covered by the viewport.\n.TP\n.B set jumpyscrolling\nScroll the buffer contents per half-screen instead of per line.\n.TP\n.B set keycolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\\fIfgcolor\\fB,\\fIbgcolor\\fR\nUse this color combination for the shortcut key combos\nin the two help lines at the bottom of the screen.\nSee \\fBset \\%titlecolor\\fR for more details.\n.TP\n.B set linenumbers\nDisplay line numbers to the left of the text area.\n(Any line with an anchor additionally gets a mark in the margin.)\n.TP\n.B set locking\nUse vim-style lock-files when editing files.\n.TP\n.B set magic\nWhen neither the file's name nor its first line give a clue,\ntry using \\fI\\%libmagic\\fR to determine the applicable syntax.\n(Calling \\fI\\%libmagic\\fR can be relatively time consuming.\nIt is therefore not done by default.)\n.TP\n.BI \"set matchbrackets \"\"\" characters \"\"\"\"\nSpecify the opening and closing brackets that can be found by bracket\nsearches. This may not include blank characters. The opening set must\ncome before the closing set, and the two sets must be in the same order.\nThe default value is \"\\fB(<[{)>]}\\fR\".\n.TP\n.B set minibar\nSuppress the title bar and instead show information about\nthe current buffer at the bottom of the screen, in the space\nfor the status bar. In this \\[lq]mini bar\\[rq] the filename is shown\non the left, followed by an asterisk if the buffer has been modified.\nOn the right are displayed the current line and column number, the\ncode of the character under the cursor (in Unicode format: U+xxxx),\nthe same flags as are shown by \\fBset \\%stateflags\\fR, and a percentage\nthat expresses how far the cursor is into the file (linewise).\nWhen a file is loaded or saved, and also when switching between buffers,\nthe number of lines in the buffer is displayed after the filename.\nThis number is cleared upon the next keystroke, or replaced with an\n[i/n] counter when multiple buffers are open.\nThe line plus column numbers and the character code are displayed only when\n\\fBset \\%constantshow\\fR is used, and can be toggled on and off with \\fBM\\-C\\fR.\nThe state flags are displayed only when \\fBset \\%stateflags\\fR is used.\n.TP\n.B set minicolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\\fIfgcolor\\fB,\\fIbgcolor\\fR\nUse this color combination for the mini bar.\n(When this option is not specified, the colors of the title bar are used.)\nSee \\fBset \\%titlecolor\\fR for more details.\n.TP\n.B set mouse\nEnable mouse support, if available for your system. When enabled,\nmouse clicks can be used to place the cursor, set the mark (with two\nclicks), and execute shortcuts. The mouse works in the X Window\nSystem, and on the console when gpm is running. Text can still be\nselected through dragging by holding down the Shift key.\n.TP\n.B set multibuffer\nWhen reading in a file with \\fB^R\\fR, insert it into a new buffer by default.\n.TP\n.B set noconvert\nDon't convert files from DOS format.\n.TP\n.B set nohelp\nDon't display the two help lines at the bottom of the screen.\n.TP\n.B set nonewlines\nDon't automatically add a newline when a text does not end with one.\n(This can cause you to save non-POSIX text files.)\n.TP\n.B set nowrap\nDeprecated option since it has become the default setting.\nWhen needed, use \\fBunset \\%breaklonglines\\fR instead.\n.TP\n.B set numbercolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\\fIfgcolor\\fB,\\fIbgcolor\\fR\nUse this color combination for line numbers.\nSee \\fBset \\%titlecolor\\fR for more details.\n.TP\n.B set operatingdir \\fIdirectory\\fR\nAt startup, make \\fBnano\\fR change to the given \\fIdirectory\\fR, and allow\nreading and writing files only in this directory and its subdirectories.\n.TP\n.B set positionlog\nSave the positions of cursor and anchors between editing sessions.\nThese positions are remembered for the 200 most-recently edited files.\n.TP\n.B set preserve\nPreserve the XOFF and XON sequences (\\fB^S\\fR and \\fB^Q\\fR) so that\nthey are caught by the terminal (stopping and resuming the output).\n.TP\n.B set promptcolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\\fIfgcolor\\fB,\\fIbgcolor\\fR\nUse this color combination for the prompt bar.\n(When this option is not specified, the colors of the title bar are used.)\nSee \\fBset \\%titlecolor\\fR for more details.\n.TP\n.BI \"set punct \"\"\" characters \"\"\"\"\nSet the characters treated as closing punctuation when justifying\nparagraphs. This may not include blank characters. Only the\nspecified closing punctuation, optionally followed by closing brackets\n(see \\fBset \\%brackets\\fR), can end sentences. The default value is \"\\fB!.?\\fR\".\n.TP\n.B set quickblank\nMake status-bar messages disappear after 1 keystroke instead of after 20.\nNote that option \\fBconstantshow\\fR overrides this.\nWhen option \\fBminibar\\fR or \\fBzero\\fR is in effect,\n\\fBquickblank\\fR makes a message disappear after\n0.8 seconds instead of after the default 1.5 seconds.\n.TP\n.BI \"set quotestr \"\"\" regex \"\"\"\"\nSet the regular expression for matching the quoting part of a line.\nThe default value is \"\\fB^([\\ \\et]*([!#%:;>|}]|//))+\\fR\".\n(Note that \\fB\\et\\fR stands for an actual Tab character.)\nThis makes it possible to rejustify blocks of quoted text when composing\nemail, and to rewrap blocks of line comments when writing source code.\n.TP\n.B set rawsequences\nInterpret escape sequences directly, instead of asking \\fIn\\%curses\\fR\nto translate them. (If you need this option to get some keys to work\nproperly, it means that the \\fI\\%terminfo\\fR terminal description that is used\ndoes not fully match the actual behavior of your terminal. This can\nhappen when you ssh into a BSD machine, for example.)\nUsing this option disables \\fBnano\\fR's mouse support.\n.TP\n.B set rebinddelete\nInterpret the Delete and Backspace keys differently so that both Backspace\nand Delete work properly. You should only use this option when on your\nsystem either Backspace acts like Delete or Delete acts like Backspace.\n.TP\n.B set regexp\nDo regular-expression searches by default.\nRegular expressions in \\fBnano\\fR are of the extended type (ERE).\n.TP\n.B set saveonexit\nSave a changed buffer automatically on exit (\\fB^X\\fR); don't prompt.\n.TP\n.B set scrollercolor \\fIfgcolor\\fB,\\fIbgcolor\\fR\nUse this color combination for the indicator alias \\[lq]scrollbar\\[rq].\nSee \\fBset \\%titlecolor\\fR for more details.\n.TP\n.B set selectedcolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\\fIfgcolor\\fB,\\fIbgcolor\\fR\nUse this color combination for selected text.\nSee \\fBset \\%titlecolor\\fR for more details.\n.TP\n.B set showcursor\nPut the cursor on the highlighted item in the file browser, and show\nthe cursor in the help viewer, to aid braille users and people with\npoor vision.\n.TP\n.B set smarthome\nMake the Home key smarter. When Home is pressed anywhere but at the\nvery beginning of non-whitespace characters on a line, the cursor jumps\nto that beginning (either forwards or backwards). If the cursor is\nalready at that position, it jumps to the true beginning of the line.\n.TP\n.B set softwrap\nDisplay lines that exceed the screen's width over multiple screen lines.\n(You can make this soft-wrapping occur at whitespace instead of rudely at\nthe screen's edge, by using also \\fBset \\%atblanks\\fR.)\n.TP\n.B set solosidescroll\nWhen the cursor approaches the right edge of the edit window, scroll only the\ncurrent line sideways by a large amount, instead of scrolling all visible lines\nsideways by just the amount needed to keep the cursor in view.\nThis latter whole-window smooth sideways scrolling is the new default behavior.\nThe single-line jerky sideways scrolling enabled by this option was the old\nbehavior \\[em] the only behavior that \\fBnano\\fR knew.\n.TP\n.B set speller \"\"\"\\fIprogram\\fR [\\fIargument \\fR...]\\fB\"\"\"\nUse the given \\fIprogram\\fR to do spell checking and correcting, instead of\nusing the built-in corrector that calls \\fBhunspell\\fR(1) or \\fBspell\\fR(1).\n.TP\n.B set spotlightcolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\\fIfgcolor\\fB,\\fIbgcolor\\fR\nUse this color combination for highlighting a search match.\nThe default value is \\fBblack,\\%lightyellow\\fR.\nSee \\fBset \\%titlecolor\\fR for valid color names.\n.TP\n.B set stateflags\nUse the top-right corner of the screen for showing some state flags:\n\\fBI\\fR when auto-indenting, \\fBM\\fR when the mark is on, \\fBL\\fR when\nhard-wrapping (breaking long lines), \\fBR\\fR when recording a macro,\nand \\fBS\\fR when soft-wrapping.\nWhen the buffer is modified, a star (\\fB*\\fR) is shown after the\nfilename in the center of the title bar.\n.TP\n.B set statuscolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\\fIfgcolor\\fB,\\fIbgcolor\\fR\nUse this color combination for the status bar.\nSee \\fBset \\%titlecolor\\fR for more details.\n.TP\n.B set stripecolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\\fIfgcolor\\fB,\\fIbgcolor\\fR\nUse this color combination for the vertical guiding stripe.\nSee \\fBset \\%titlecolor\\fR for more details.\n.TP\n.B set tabsize \\fInumber\\fR\nUse a tab size of \\fInumber\\fR columns. The value of \\fInumber\\fR must be\ngreater than 0. The default value is \\fB8\\fR.\n.TP\n.B set tabstospaces\nConvert each typed tab to spaces \\[em] to the number of spaces\nthat a tab at that position would take up.\n(Note: pasted tabs are not converted.)\n.TP\n.B set titlecolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\\fIfgcolor\\fB,\\fIbgcolor\\fR\nUse this color combination for the title bar.\nValid names for the foreground and background colors are:\n.BR red \", \" green \", \" blue \", \" \\%magenta \", \" \\%yellow \", \" \\%cyan ,\n.BR white \", and \" black .\nEach of these eight names may be prefixed with the word \\fBlight\\fR\nto get a brighter version of that color.\nThe word \\fBgrey\\fR or \\fBgray\\fR may be used\nas a synonym for \\fB\\%lightblack\\fR.\nOn a Linux console, \\fBlight\\fR does not have\nany effect for a background color.\nOn terminal emulators that can do at least 256 colors,\nother valid (but unprefixable) color names are:\n.BR pink \", \" \\%purple \", \" mauve \", \" \\%lagoon \", \" mint \", \" lime \", \" peach ,\n.BR \\%orange \", \" \\%latte \", \" \\%rosy \", \" beet \", \" plum \", \" sea \", \" sky ,\n.BR slate \", \" teal \", \" sage \", \" brown \", \" \\%ocher \", \" sand \", \" \\%tawny ,\n.BR brick \", \" \\%crimson \", and \" \\%normal\n\\[em] where \\fB\\%normal\\fR means the default foreground or background color.\nOn such emulators, the color may also be specified as a three-digit hexadecimal\nnumber prefixed with \\fB#\\fR, with the digits representing the amounts of red,\ngreen, and blue, respectively. This tells \\fBnano\\fR to select from the\navailable palette the color that approximates the given values.\n\nEither \"\\fIfgcolor\\fR\" or \"\\fB,\\fIbgcolor\\fR\" may be left out,\nand the pair may be preceded by \\fBbold\\fR and/or \\fB\\%italic\\fR\n(separated by commas) to get a bold and/or slanting typeface,\nif your terminal can do those.\n.TP\n.B set trimblanks\nRemove trailing whitespace from wrapped lines when automatic\nhard-wrapping occurs or when text is justified.\n.TP\n.B set unix\nSave a file by default in Unix format. This overrides nano's\ndefault behavior of saving a file in the format that it had.\n(This option has no effect when you also use \\fBset \\%noconvert\\fR.)\n.TP\n.BI \"set whitespace \"\"\" characters \"\"\"\"\nSet the two characters used to indicate the presence of tabs and\nspaces. They must be single-column characters. The default pair\nfor a UTF-8 locale is \"\\fB\\[Fc]\\[md]\\fR\", and for other locales \"\\fB>.\\fR\".\n.TP\n.B set wordbounds\nDetect word boundaries differently by treating punctuation\ncharacters as parts of words.\n.TP\n.BI \"set wordchars \"\"\" characters \"\"\"\"\nSpecify which other characters (besides the normal alphanumeric ones)\nshould be considered as parts of words. When using this option, you\nprobably want to unset \\fBwordbounds\\fR.\n.TP\n.B set zap\nLet an unmodified Backspace or Delete erase the marked region\n(instead of a single character, and without affecting the cutbuffer).\n.TP\n.B set zero\nHide all elements of the interface (title bar, status bar, and help lines)\nand use all rows of the terminal for showing the contents of the buffer.\nThe status bar appears only when there is a significant message,\nand disappears after 1.5 seconds or upon the next keystroke.\nWith \\fBM\\-Z\\fR the title bar plus status bar can be toggled.\nWith \\fBM\\-X\\fR the help lines.\n\n.SH SYNTAX HIGHLIGHTING\nColoring the different syntactic elements of a file\nis done via regular expressions (see the \\fBcolor\\fR command below).\nThis is inherently imperfect, because regular expressions are not\npowerful enough to fully parse a file. Nevertheless, regular\nexpressions can do a lot and are easy to make, so they are a\ngood fit for a small editor like \\fBnano\\fR.\n.sp\nAll regular expressions in \\fBnano\\fR are POSIX extended regular expressions.\nThis means that \\fB.\\fR, \\fB?\\fR, \\fB*\\fR, \\fB+\\fR, \\fB^\\fR, \\fB$\\fR, and\nseveral other characters are special.\nThe period \\fB.\\fR matches any single character,\n\\fB?\\fR means the preceding item is optional,\n\\fB*\\fR means the preceding item may be matched zero or more times,\n\\fB+\\fR means the preceding item must be matched one or more times,\n\\fB^\\fR matches the beginning of a line, and \\fB$\\fR the end,\n\\fB\\e<\\fR matches the start of a word, and \\fB\\e>\\fR the end,\nand \\fB\\es\\fR matches a blank.\nIt also means that lookahead and lookbehind are not possible.\nA complete explanation can be found in the manual page of GNU grep:\n\\fBman grep\\fR.\n.sp\nEach regular expression in a \\fInanorc\\fR file should be wrapped in\ndouble quotes (\\fB\"\"\\fR). Multiple regular expressions can follow\neach other on a line by separating them with blanks. This means that\na regular expression cannot contain a double quote followed by a blank.\nWhen you need this combination inside a regular expression,\nthen either the double quote or the blank should be put\nbetween square brackets (\\fB[]\\fR).\n.sp\nFor each kind of file a separate syntax can be defined\nvia the following commands:\n.TP\n.BI syntax \" name \\fR[\" \"\"\"\" fileregex \"\"\" \" \\fR...]\nStart the definition of a syntax with this \\fIname\\fR.\nAll subsequent \\fBcolor\\fR and other such commands\nare added to this syntax, until a new \\fBsyntax\\fR\ncommand is encountered.\n.sp\nWhen \\fBnano\\fR is run, this syntax is automatically\nactivated (for the relevant buffer) if the absolute filename\nmatches the extended regular expression \\fIfileregex\\fR.\nOr the syntax can be explicitly activated (for all buffers)\nby using the \\fB\\-Y\\fR or \\fB\\-\\-syntax\\fR\ncommand-line option followed by the \\fIname\\fR.\n.sp\nThe syntax \\fBdefault\\fR is special: it takes no \\fIfileregex\\fR,\nand applies to files that don't match any syntax's regexes.\nThe syntax \\fBnone\\fR is reserved; specifying it on the command line\nis the same as not having a syntax at all.\n.TP\n.BI \"header \"\"\" regex \"\"\" \" \\fR...\nIf from all defined syntaxes no \\fIfileregex\\fR matched, then compare\nthis \\fIregex\\fR (or regexes) against the first line of the current file,\nto determine whether this syntax should be used for it.\n.TP\n.BI \"magic \"\"\" regex \"\"\" \" \\fR...\nIf no \\fIfileregex\\fR matched and no \\fBheader\\fR regex matched\neither, then compare this \\fIregex\\fR (or regexes) against the\nresult of querying the \\fImagic\\fR database about the current\nfile, to determine whether this syntax should be used for it.\n(This querying is done only when \\fI\\%libmagic\\fR is actually installed\non the system and \\fB\\-\\-magic\\fR or \\fBset \\%magic\\fR was given.)\n.TP\n.BI formatter \" program \" \\fR[ \"argument \" \\fR...]\nRun the given \\fIprogram\\fR on the full contents of the current buffer.\n.TP\n.BI linter \" program \" \\fR[ \"argument \" \\fR...]\nUse the given \\fIprogram\\fR to run a syntax check on the current buffer.\n.TP\n.BI \"comment \"\"\" string \"\"\"\"\nUse the given \\fIstring\\fR for commenting and uncommenting lines.\nIf the string contains a vertical bar or pipe character (\\fB|\\fR),\nthis designates bracket-style comments; for example, \"\\fB/*|*/\\fR\" for\nCSS files. The characters before the pipe are prepended to the line and the\ncharacters after the pipe are appended at the end of the line. If no pipe\ncharacter is present, the full string is prepended; for example, \"\\fB#\\fR\"\nfor Python files. If nothing is specified between the double quotes, then\nthe comment/uncomment function is disabled; for example, \"\" for JSON.\nThe default value is \"\\fB#\\fR\".\n.TP\n.BI \"tabgives \"\"\" string \"\"\"\"\nMake the key produce the given \\fIstring\\fR. Useful for languages like\nPython that want to see only spaces for indentation.\nThis overrides the setting of the \\fBtabstospaces\\fR option.\n.TP\n.BI \"color \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\" fgcolor , bgcolor \" \"\"\" regex \"\"\" \" \\fR...\nPaint all pieces of text that match the extended regular expression\n\\fIregex\\fR with the given foreground and background colors, at least\none of which must be specified. Valid color names are:\n.BR red \", \" green \", \" blue \", \" \\%magenta \", \" \\%yellow \", \" \\%cyan ,\n.BR white \", and \" black .\nEach of these eight names may be prefixed with the word \\fBlight\\fR\nto get a brighter version of that color.\nThe word \\fBgrey\\fR or \\fBgray\\fR may be used\nas a synonym for \\fB\\%lightblack\\fR.\nOn a Linux console, \\fBlight\\fR does not have\nany effect for a background color.\nOn terminal emulators that can do at least 256 colors,\nother valid (but unprefixable) color names are:\n.BR pink \", \" \\%purple \", \" mauve \", \" \\%lagoon \", \" mint \", \" lime \", \" peach ,\n.BR \\%orange \", \" \\%latte \", \" \\%rosy \", \" beet \", \" plum \", \" sea \", \" sky ,\n.BR slate \", \" teal \", \" sage \", \" brown \", \" \\%ocher \", \" sand \", \" \\%tawny ,\n.BR brick \", \" \\%crimson \", and \" \\%normal\n\\[em] where \\fB\\%normal\\fR means the default foreground or background color.\nOn such emulators, the color may also be specified as a three-digit hexadecimal\nnumber prefixed with \\fB#\\fR, with the digits representing the amounts of red,\ngreen, and blue, respectively. This tells \\fBnano\\fR to select from the\navailable palette the color that approximates the given values.\n\nThe color pair may be preceded by \\fBbold\\fR and/or \\fB\\%italic\\fR\n(separated by commas) to get a bold and/or slanting typeface,\nif your terminal can do those.\n.sp\nAll coloring commands are applied in the order in which they are specified,\nwhich means that later commands can recolor stuff that was colored earlier.\n.TP\n.BI \"icolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\" fgcolor , bgcolor \" \"\"\" regex \"\"\" \" \\fR...\nSame as above, except that the matching is case insensitive.\n.TP\n.BI \"color \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\" fgcolor , bgcolor \" start=\"\"\" fromrx \"\"\" end=\"\"\" torx \"\"\"\"\nPaint all pieces of text whose start matches extended regular expression\n\\fIfromrx\\fR and whose end matches extended regular expression \\fItorx\\fR\nwith the given foreground and background colors,\nat least one of which must be specified. This means that, after an\ninitial instance of \\fIfromrx\\fR, all text until the first instance of\n\\fItorx\\fR is colored. This allows syntax highlighting to span\nmultiple lines.\n.TP\n.BI \"icolor \\fR[\\fBbold,\\fR][\\fBitalic,\\fR]\" fgcolor , bgcolor \" start=\"\"\" fromrx \"\"\" end=\"\"\" torx \"\"\"\"\nSame as above, except that the matching is case insensitive.\n.TP\n.BI \"include \"\"\" syntaxfile \"\"\"\"\nRead in self-contained color syntaxes from \\fIsyntaxfile\\fR. Note that\n\\fIsyntaxfile\\fR may contain only the above commands, from \\fBsyntax\\fR\nto \\fBicolor\\fR.\n.TP\n.BI extendsyntax \" name command argument \" \\fR...\nExtend the syntax previously defined as \\fIname\\fR with another\n\\fI\\%command\\fR. This allows adding a new \\fB\\%color\\fR, \\fB\\%icolor\\fR,\n\\fB\\%header\\fR, \\fB\\%magic\\fR, \\fB\\%formatter\\fR, \\fB\\%linter\\fR,\n\\fB\\%comment\\fR, or \\fB\\%tabgives\\fR\ncommand to an already defined syntax \\[em] useful when you want to\nslightly improve a syntax defined in one of the system-installed\nfiles (which normally are not writable).\n\n.SH REBINDING KEYS\nKey bindings can be changed via the following three commands:\n.RS 3\n.TP\n.BI bind \" key function menu\"\nRebinds the given \\fIkey\\fR to the given \\fIfunction\\fR in the given \\fImenu\\fR\n(or in all menus where the function exists when \\fBall\\fR is used).\n.TP\n.BI bind \" key \" \"\"\"\" string \"\"\"\" \" menu\"\nMakes the given \\fIkey\\fR produce the given \\fIstring\\fR in the given\n\\fImenu\\fR (or in all menus where the key exists when \\fBall\\fR is used).\nBesides literal text and/or control codes, the \\fIstring\\fR may contain\nfunction names between braces. These functions are invoked when\nthe key is typed. To include a literal opening brace, use \\fB{{}\\fR.\n.TP\n.BI unbind \" key menu\"\nUnbinds the given \\fIkey\\fR from the given \\fImenu\\fR (or from all\nmenus where the key exists when \\fBall\\fR is used).\n.RE\n.sp\nNote that \\fBbind \\fIkey\\fR \\fB\"{\\fIfunction\\fB}\"\\fR \\fImenu\\fR is equivalent\nto \\fBbind \\fIkey\\fR \\fIfunction\\fR \\fImenu\\fR, except that for the latter form\n\\fBnano\\fR checks the availability of the \\fIfunction\\fR in the given \\fImenu\\fR\nat startup time (and reports an error if it does not exist there), whereas for the\nfirst form \\fBnano\\fR checks at execution time that the \\fIfunction\\fR exists\nbut not whether it makes any sense in the current menu. The user has to take care\nthat a function name between braces (or any sequence of them) is appropriate.\nStrange behavior or even a crash can result when the braced name is unfitting.\n\n.TP\nThe format of \\fIkey\\fR should be one of:\n.RS 3\n.TP 7\n.BI ^ X\nwhere \\fIX\\fR is a Latin letter, or one of several ASCII characters\n(@, ], \\e, ^, _), or the word \"Space\".\nExample: ^C.\n.TP\n.BI M\\- X\nwhere \\fIX\\fR is any ASCII character (except [),\nor the word \"Space\", \"Left\", \"Right\", \"Up\", or \"Down\".\nExample: M\\-8.\n.TP\n.BI Sh\\-M\\- X\nwhere \\fIX\\fR is a Latin letter.\nExample: Sh\\-M\\-U.\nBy default, each Meta+letter keystroke does the same as the corresponding\nShift+Meta+letter. But when any Shift+Meta bind is made, that will\nno longer be the case, for all letters.\n.TP\n.BI F N\nwhere \\fIN\\fR is a numeric value from 1 to 24.\nExample: F10.\n(Often, \\fBF13\\fR to \\fBF24\\fR can be typed as \\fBF1\\fR to \\fBF12\\fR with Shift.)\n.TP\n.BR Ins \" or \" Del .\n.RE\n.sp\nRebinding \\fB^M\\fR (Enter) or \\fB^I\\fR (Tab) is probably not a good idea.\nRebinding \\fB^[\\fR (Esc) is not possible, because its keycode\nis the starter byte of Meta keystrokes and escape sequences.\nRebinding any of the dedicated cursor-moving keys (the arrows,\nHome, End, PageUp and PageDown) is not possible.\nOn some terminals it's not possible to rebind \\fB^H\\fR (unless \\fB\\-\\-raw\\fR\nis used) because its keycode is identical to that of the Backspace key.\n\n.TP\nValid \\fIfunction\\fR names to be bound are:\n.RS 3\n.TP 2\n.B help\nInvokes the help viewer.\n.TP\n.B cancel\nCancels the current command.\n.TP\n.B exit\nExits from the program (or from the help viewer or file browser).\n.TP\n.B writeout\nWrites the current buffer to disk, asking for a name.\n.TP\n.B savefile\nWrites the current file to disk without prompting.\n.TP\n.B insert\nInserts a file into the current buffer (at the current cursor position),\nor into a new buffer when option \\fBmultibuffer\\fR is set.\n.TP\n.B whereis\nStarts a forward search for text in the current buffer \\[em] or for filenames\nmatching a string in the current list in the file browser.\n.TP\n.B wherewas\nStarts a backward search for text in the current buffer \\[em] or for filenames\nmatching a string in the current list in the file browser.\n.TP\n.B findprevious\nSearches the next occurrence in the backward direction.\n.TP\n.B findnext\nSearches the next occurrence in the forward direction.\n.TP\n.B replace\nInteractively replaces text within the current buffer.\n.TP\n.B cut\nCuts and stores the current line (or the marked region).\n.TP\n.B copy\nCopies the current line (or the marked region) without deleting it.\n.TP\n.B paste\nPastes the currently stored text into the current buffer at the\ncurrent cursor position.\n.TP\n.B zap\nThrows away the current line (or the marked region).\n(This function is bound by default to .)\n.TP\n.B chopwordleft\nDeletes from the cursor position to the beginning of the preceding word.\n(This function is bound by default to . If your terminal\nproduces \\fB^H\\fR for , you can make delete\nthe word to the left of the cursor by rebinding \\fB^H\\fR to this function.)\n.TP\n.B chopwordright\nDeletes from the cursor position to the beginning of the next word.\n(This function is bound by default to .)\n.TP\n.B cutrestoffile\nCuts all text from the cursor position till the end of the buffer.\n.TP\n.B mark\nSets the mark at the current position, to start selecting text.\nOr, when it is set, unsets the mark.\n.TP\n.B location\nReports the current position of the cursor in the buffer:\nthe line, column, and character positions.\n.TP\n.B wordcount\nCounts and reports on the status bar the number of lines, words,\nand characters in the current buffer (or in the marked region).\n.TP\n.B execute\nPrompts for a program to execute. The program's output is inserted\ninto the current buffer \\[em] or into a new buffer when \\fBM\\-F\\fR is toggled.\nWhen the program's name is preceded by a pipe symbol (\\fB|\\fR), then the\ncurrent buffer (or the marked region) is piped to the program, and the\noutput of the program replaces the buffer (or the marked region).\n.TP\n.B speller\nInvokes a spell-checking program, either the default \\fBhunspell\\fR(1) or GNU\n\\fBspell\\fR(1), or the one defined by \\fB\\-\\-speller\\fR or \\fBset \\%speller\\fR.\n.TP\n.B formatter\nInvokes a full-buffer-processing program (if the active syntax defines one).\n(The current buffer is written out to a temporary file, the program\nis run on it, and then the temporary file is read back in, replacing\nthe contents of the buffer.)\n.TP\n.B linter\nInvokes a syntax-checking program (if the active syntax defines one).\nIf this program produces lines of the form \"filename:linenum:charnum:\nsome message\", then the cursor is put at the indicated position\nin the mentioned file while showing \"some message\" on the status bar.\nYou can move from message to message with and ,\nand leave linting mode with \\fB^C\\fR or .\n.TP\n.B justify\nJustifies the current paragraph (or the marked region).\nA paragraph is a group of contiguous lines that, apart from possibly\nthe first line, all have the same indentation. The beginning of a\nparagraph is detected by either this lone line with a differing\nindentation or by a preceding blank line.\n.TP\n.B fulljustify\nJustifies the entire current buffer (or the marked region).\n.TP\n.B indent\nIndents (shifts to the right) the current line or the marked lines.\n.TP\n.B unindent\nUnindents (shifts to the left) the current line or the marked lines.\n.TP\n.B comment\nComments or uncomments the current line or the marked lines,\nusing the comment style specified in the active syntax.\n.TP\n.B complete\nCompletes (when possible) the fragment before the cursor\nto a full word found elsewhere in the current buffer.\n.TP\n.B left\nGoes left one position (in the editor or browser).\n.TP\n.B right\nGoes right one position (in the editor or browser).\n.TP\n.B up\nGoes one line up (in the editor or browser).\n.TP\n.B down\nGoes one line down (in the editor or browser).\n.TP\n.B scrollleft\nScrolls the viewport a tabsize to the left, when possible.\n(This function is bound by default to \\fBM\\-<\\fR.)\n.TP\n.B scrollright\nScrolls the viewport a tabsize to the right. When needed to keep\nthe cursor visible, it is moved to a longer line in the viewport.\nIf there is no sufficiently longer line, no scroll is made.\n(This function is bound by default to \\fBM\\->\\fR.)\n.TP\n.B scrollup\nScrolls the viewport up one row (meaning that the text slides down)\nwhile keeping the cursor in the same text position, if possible.\n(This function is bound by default to \\fBM\\-Up\\fR.\nIf \\fBM\\-Up\\fR does nothing on your Linux console, see the FAQ:\n.UR https://nano\\-editor.org/dist/latest/faq.html#4.1\n.UE .)\n.TP\n.B scrolldown\nScrolls the viewport down one row (meaning that the text slides up)\nwhile keeping the cursor in the same text position, if possible.\n(This function is bound by default to \\fBM\\-Down\\fR.)\n.TP\n.B center\nScrolls the line with the cursor to the middle of the viewport.\n.TP\n.B cycle\nScrolls the line with the cursor first to the middle of the viewport,\nthen to the top, then to the bottom.\n.TP\n.B prevword\nMoves the cursor to the beginning of the previous word.\n.TP\n.B nextword\nMoves the cursor to the beginning of the next word.\n.TP\n.B home\nMoves the cursor to the beginning of the current line.\n.TP\n.B end\nMoves the cursor to the end of the current line.\n.TP\n.B beginpara\nMoves the cursor to the beginning of the current paragraph.\n.TP\n.B endpara\nMoves the cursor to the end of the current paragraph.\n.TP\n.B prevblock\nMoves the cursor to the beginning of the current or preceding block of text.\n(Blocks are separated by one or more blank lines.)\n.TP\n.B nextblock\nMoves the cursor to the beginning of the next block of text.\n.TP\n.B toprow\nMoves the cursor to the first row in the viewport.\n.TP\n.B bottomrow\nMoves the cursor to the last row in the viewport.\n.TP\n.B pageup\nGoes up one screenful.\n.TP\n.B pagedown\nGoes down one screenful.\n.TP\n.B firstline\nGoes to the first line of the file.\n.TP\n.B lastline\nGoes to the last line of the file.\n.TP\n.B gotoline\nGoes to a specific line (and column if given).\nA negative number counts from the end of the buffer (and end of the line).\nPutting \\fB++\\fR or \\fB\\-\\-\\fR before the first number will jump the given\nnumber of lines forward or backward.\n.TP\n.B findbracket\nMoves the cursor to the bracket (or brace or parenthesis, etc.\\&) that matches\n(pairs) with the one under the cursor. See \\fBset \\%matchbrackets\\fR.\n.TP\n.B anchor\nPlaces an anchor at the current line, or removes it when already present.\n(An anchor is visible when line numbers are activated.)\n.TP\n.B prevanchor\nGoes to the first anchor before the current line.\n.TP\n.B nextanchor\nGoes to the first anchor after the current line.\n.TP\n.B prevbuf\nSwitches to editing/viewing the previous buffer when multiple buffers are open.\n.TP\n.B nextbuf\nSwitches to editing/viewing the next buffer when multiple buffers are open.\n.TP\n.B verbatim\nInserts the next keystroke verbatim into the file, or begins Unicode input\nwhen a hexadecimal digit is typed.\n.TP\n.B tab\nInserts a tab at the current cursor location.\n.TP\n.B enter\nInserts a new line below the current one.\n.TP\n.B delete\nDeletes the character under the cursor.\n.TP\n.B backspace\nDeletes the character before the cursor.\n.TP\n.B recordmacro\nStarts the recording of keystrokes \\[em] the keystrokes are stored\nas a macro. When already recording, the recording is stopped.\n.TP\n.B runmacro\nReplays the keystrokes of the last recorded macro.\n.TP\n.B undo\nUndoes the last performed text action (add text, delete text, etc).\n.TP\n.B redo\nRedoes the last undone action (that is: it undoes an undo).\n.TP\n.B refresh\nRefreshes the screen.\n.TP\n.B suspend\nSuspends the editor and returns control to the shell\n(until you tell the process to resume execution with \\fBfg\\fR).\n.TP\n.B casesens\nToggles whether searching/replacing ignores or respects the case of\nthe given characters.\n.TP\n.B regexp\nToggles whether searching/replacing uses literal strings or regular expressions.\n.TP\n.B backwards\nToggles whether searching/replacing goes forward or backward.\n.TP\n.B older\nRetrieves the previous (earlier) entry at a prompt.\n.TP\n.B newer\nRetrieves the next (later) entry at a prompt.\n.TP\n.B flipreplace\nToggles between searching for something and replacing something.\n.TP\n.B flipgoto\nToggles between searching for text and targeting a line number.\n.TP\n.B flipexecute\nSwitches from inserting a file to executing a command.\n.TP\n.B flippipe\nWhen executing a command, toggles whether the current buffer (or marked\nregion) is piped to the command.\n.TP\n.B flipnewbuffer\nToggles between inserting into the current buffer and into a new\nempty buffer.\n.TP\n.B flipconvert\nWhen reading in a file, toggles between converting and not converting\nit from DOS format. Converting is the default.\n.TP\n.B dosformat\nWhen writing a file, switches to writing DOS format (CR+LF line endings).\n.TP\n.B append\nWhen writing a file, appends to the end instead of overwriting.\n.TP\n.B prepend\nWhen writing a file, \\[lq]prepends\\[rq] (writes at the beginning) instead of overwriting.\n.TP\n.B backup\nWhen writing a file, creates a backup of the current file.\n.TP\n.B discardbuffer\nDiscards the current buffer without saving (when in the Write Out menu).\nWhen it was the last buffer, then \\fBnano\\fR exits with error status 2.\n.TP\n.B browser\nStarts the file browser (in the Read File and Write Out menus),\nallowing to select a file from a list.\n.TP\n.B gotodir\nGoes to a directory to be specified, allowing to browse anywhere\nin the filesystem.\n.TP\n.B firstfile\nGoes to the first file in the list when using the file browser.\n.TP\n.B lastfile\nGoes to the last file in the list when using the file browser.\n.TP\n.B nohelp\nToggles the presence of the two-line list of key bindings at the bottom of the screen.\n(This toggle is special: it is available in all menus except the help viewer\nand the linter. All further toggles are available in the main menu only.)\n.TP\n.B zero\nToggles the presence of title bar and status bar.\n.TP\n.B constantshow\nToggles the constant reporting (on the status bar)\nof the current line, column, and character positions.\n.TP\n.B softwrap\nToggles the displaying of overlong lines on multiple screen lines.\n.TP\n.B linenumbers\nToggles the display of line numbers in front of the text.\n.TP\n.B whitespacedisplay\nToggles the showing of whitespace.\n.TP\n.B nosyntax\nToggles syntax highlighting.\n.TP\n.B smarthome\nToggles the smartness of the Home key.\n.TP\n.B autoindent\nToggles whether a newly created line will contain the same amount of leading\nwhitespace as the preceding line \\[em] or as the next line if the preceding line\nis the beginning of a paragraph.\n.TP\n.B cutfromcursor\nToggles whether cutting text cuts the whole line or just from the current cursor\nposition to the end of the line.\n.TP\n.B breaklonglines\nToggles whether the overlong part of a line is hard-wrapped to the next line.\n.TP\n.B tabstospaces\nToggles whether typed tabs are converted to spaces.\n.TP\n.B mouse\nToggles mouse support.\n.RE\n\n.TP\nValid \\fImenu\\fR sections are:\n.RS 3\n.TP 2\n.B main\nThe main editor window where text is entered and edited.\n.TP\n.B help\nThe help-viewer menu.\n.TP\n.B search\nThe search menu (AKA whereis).\n.TP\n.B replace\nThe \\&'search to replace' menu.\n.TP\n.B replacewith\nThe \\&'replace with' menu, which comes up after \\&'search to replace'.\n.TP\n.B yesno\nThe \\&'yesno' menu, where the Yes/No/All/Cancel question is asked.\n.TP\n.B gotoline\nThe \\&'goto line (and column)' menu.\n.TP\n.B writeout\nThe \\&'write file' menu.\n.TP\n.B insert\nThe \\&'insert file' menu.\n.TP\n.B browser\nThe \\&'file browser' menu, for selecting a file to be opened or\ninserted or written to.\n.TP\n.B whereisfile\nThe \\&'search for a file' menu in the file browser.\n.TP\n.B gotodir\nThe \\&'go to directory' menu in the file browser.\n.TP\n.B execute\nThe menu for inserting the output from an external command,\nor for filtering the buffer (or the marked region) through\nan external command, or for executing one of several tools.\n.TP\n.B spell\nThe menu of the integrated spell checker where the user can edit a misspelled word.\n.TP\n.B linter\nThe linter menu, which allows jumping through the linting messages.\n.TP\n.B all\nA special name that encompasses all menus.\nFor \\fBbind\\fR it means all menus where the specified \\fIfunction\\fR exists;\nfor \\fBunbind\\fR it means all menus where the specified \\fIkey\\fR exists.\n.RE\n\n.SH EXAMPLES\nTo make \\fBCtrl+Z\\fR suspend nano:\n.sp\n.RS\n.B bind ^Z suspend main\n.RE\n.sp\nTo make \\fBShift+Alt+C\\fR copy the marked region to the system's clipboard:\n.sp\n.RS\n.B bind Sh\\-M\\-C \"\"\"{execute}| xsel \\-ib {enter}{undo}\"\"\" main\n.RE\n.sp\n\n.SH FILES\n.TP\n.I /etc/nanorc\nSystem-wide configuration file.\n.TP\n.IR \\[ti]/.nanorc \" or \" $XDG_CONFIG_HOME/nano/nanorc \" or \" \\[ti]/.config/nano/nanorc\nPer-user configuration file.\n.TP\n.I /usr/share/nano/*\nSyntax definitions for the syntax coloring of common file types\n(and for less common file types in the \\fIextra/\\fR subdirectory).\n\n.SH SEE ALSO\n.BR nano (1)\n.TP\n.I https://nano\\-editor.org/cheatsheet.html\nAn overview of the default key bindings.\n" }, { "path": "doc/rnano.1", "content": ".\\\" Copyright (C) 2002-2007, 2014-2026 Free Software Foundation, Inc.\n.\\\"\n.\\\" This document is dual-licensed. You may distribute and/or modify it\n.\\\" under the terms of either of the following licenses:\n.\\\"\n.\\\" * The GNU General Public License, as published by the Free Software\n.\\\" Foundation, version 3 or (at your option) any later version. You\n.\\\" should have received a copy of the GNU General Public License\n.\\\" along with this program. If not, see\n.\\\" .\n.\\\"\n.\\\" * The GNU Free Documentation License, as published by the Free\n.\\\" Software Foundation, version 1.2 or (at your option) any later\n.\\\" version, with no Invariant Sections, no Front-Cover Texts, and no\n.\\\" Back-Cover Texts. You should have received a copy of the GNU Free\n.\\\" Documentation License along with this program. If not, see\n.\\\" .\n.\\\"\n.TH RNANO 1 \"April 2026\" \"GNU nano 9.0\"\n\n.SH NAME\nrnano \\- a restricted nano\n\n.SH SYNOPSIS\n.B rnano\n.RI [ options \"] [[\\fB+\" line [\\fB, column \"]] \" file ]...\n\n.SH DESCRIPTION\n\\fBrnano\\fR runs the \\fBnano\\fR editor in restricted mode. This allows\nediting only the \\fIfile\\fR (or files) specified on the command line.\n.sp\nIn restricted mode, \\fBnano\\fR will:\n.RS 4\n.IP \\[bu] 2\nnot make backups;\n.IP \\[bu]\nnot read nor write the history files;\n.IP \\[bu]\nnot allow suspending;\n.IP \\[bu]\nnot allow spell checking;\n.IP \\[bu]\nnot allow running any command in the shell;\n.IP \\[bu]\nnot allow saving the current buffer under a different name;\n.IP \\[bu]\nnot allow inserting another file or opening a new buffer;\n.IP \\[bu]\nnot allow appending or prepending to any file.\n.RE\n.sp\nAs an exception, before the specified file or files, the nanorc files are\nread, to allow customization. If customization should not be allowed,\nuse option \\fB\\-I\\fR (\\fB\\-\\-ignorercfiles\\fR) as well.\n.sp\nWhen no \\fIfile\\fR is specified on the command line, the user may save\nthe contents that they type into the new buffer under any name, except\nthat existing files may not be overwritten. If the places where this\nnew file may be created should be limited, then additionally use the\noption \\fB\\-o\\fR (\\fB\\-\\-operatingdir\\fR).\n\n.SH OPTIONS\n.TP\n.BR \\-h \", \" \\-\\-help\nShow the available command-line options and exit.\n.P\nFor all existing options, see the \\fBnano\\fR(1) man page.\n\n.SH BUGS\nPlease report bugs via\n.IR https://savannah.gnu.org/bugs/?group=nano .\n\n.SH HOMEPAGE\n.I https://nano-editor.org/\n\n.SH SEE ALSO\n.BR nano (1)\n" }, { "path": "doc/sample.nanorc.in", "content": "## Sample initialization file for GNU nano.\n##\n## For the options that take parameters, the default value is shown.\n## Other options are unset by default. To make sure that an option\n## is disabled, you can use \"unset