27eccbec23
bump version numbers and add a news item for the 2.9.5 release
2018-03-29 09:59:13 +02:00
e01bcddf16
docs: document the newly added color name "normal"
2018-03-28 14:03:52 +02:00
336fa40055
docs: clarify what the scrollup and scrolldown bindable functions do
2018-03-17 14:27:23 +01:00
c782b4cb72
bump version numbers and add a news item for the 2.9.4 release
2018-03-08 10:59:32 +01:00
7f88eff96f
docs: mention that a key can be bound to a string
2018-02-28 17:28:16 +01:00
cb0289f0dc
tweaks: fix a copy-and-paste error
2018-02-24 13:31:59 +01:00
b027263a37
small addition: allow customizing the color of an error message
...
The new option 'set errorcolor' allows the user to specify the color
combination for the status bar when an error message is displayed.
2018-02-23 12:35:17 +01:00
467cc8edf3
tweaks: remove two deprecated options and six rebindable function names
...
This addresses https://savannah.gnu.org/bugs/?48992 .
2018-02-04 13:51:13 +01:00
bb667beb5a
bindings: rename the bindable function 'gototext' to 'flipgoto'
...
This brings it in line with the other three "flip" toggles.
2018-02-04 10:34:39 +01:00
ae7366616f
bump version numbers and add a news item for the 2.9.3 release
2018-01-29 09:31:12 +01:00
30f367e0db
bump version numbers and add a news item for the 2.9.2 release
2018-01-02 15:51:12 +01:00
66fd6a5ab1
options: rename 'justifytrim' to 'trimblanks', because it has morphed
...
The option now causes nano to trim trailing whitespace also when
hardwrapping occurs while the user is typing.
2017-12-06 20:38:13 +01:00
800a997008
bump version numbers and add a news item for the 2.9.1 release
2017-11-27 19:06:26 +01:00
0465adb9ce
bump version numbers and add a news item for the 2.9.0 release
2017-11-18 11:33:28 +01:00
7ea13d4269
tweaks: correct two minor things in the documentation
2017-11-17 21:52:31 +01:00
06049f5141
docs: update references to the nanorc files for the XDG changes
2017-11-17 21:40:54 +01:00
c3a11fb7ed
options: remove '--quiet' and 'set quiet', because they hide problems
...
If the user uses a single version of nano, they have no need for
--quiet. If they do sometimes use an older version and don't want
to see the warnings, they can use 2>/dev/null (they could make an
alias for that and put it before the call of nano).
2017-11-02 17:27:53 +01:00
2356693b81
docs: document the more everyday names of three bindable functions
...
List "browser", "pageup" and "pagedown" in the manuals; the first
because it matches "speller", and the latter two because they are
what these functions are commonly known by. The names "tofiles",
"prevpage" and "nextpage" are now undocumented, but they are still
recognized by the code, as they match the tags for these functions.
2017-10-25 17:44:13 +02:00
4d35835189
docs: decribe the bindable functions 'recordmacro' and 'runmacro'
2017-10-19 21:37:41 +02:00
fc36ff7275
options: retire 'set backwards' -- it's still recognized but a no-op
2017-10-15 10:45:22 +02:00
c7eecd74de
new feature: a bindable function that starts always a backward search
2017-10-14 20:30:46 +02:00
80ed2568fc
tweaks: remove a comment from the docs that is no longer accurate
...
Date and version are updated to match each release, so the user does
not have to wonder whether the man page really describes the binary.
Also remove a bit of superfluous markup.
2017-10-12 21:17:39 +02:00
a09eedf0a3
bump version numbers and add a news item for the 2.8.7 release
2017-08-27 09:37:01 +02:00
1c1cbae6bc
small addition: allow customizing the color of selected text
...
The new option 'set selectedcolor' applies to marked text, to the
currently selected file in the file browser, and to the highlighted
match during interactive search-and-replace.
2017-08-06 09:30:32 +02:00
8f2ac1b7f6
bump version numbers and add a news item for the 2.8.6 release
2017-07-21 09:51:22 +02:00
e4a69f8b94
docs: move the descriptions of 'header' and 'magic' next to 'syntax'
...
And reword them too, so that it is clearer what the mechanism is
for determining which syntax to use for a file.
2017-07-15 12:32:57 +02:00
63c428ad08
options: rename --cut to --cutfromcursor, to be clearer
...
Rename the corresponding rc-file option too, of course.
2017-07-14 16:06:52 +02:00
f4c3670f64
docs: reword the explanation of the 'syntax' command
2017-07-14 15:21:30 +02:00
bb4d0d548a
new feature: allow lines to be softwrapped at whitespace
...
Extend get_softwrap_breakpoint() to break softwrapped lines on
whitespace when a flag is set. This flag is controlled by the new
rcfile option "atblanks". The '>' characters marking two-column
characters at the edge of the screen are disabled when it's on.
If get_softwrap_breakpoint() can't find whitespace in screen range, it
will break the line on the screen edge. (In this case, a blank can be
on the last column of the screen, but text can't, so that a blank on the
last column doesn't become invisible and possibly break the display.)
This fulfills https://savannah.gnu.org/bugs/index.php?49959 .
Requested-by: Nicholas Boel <axxisd@gmail.com>
2017-07-07 13:07:10 +02:00
30986db708
docs: mention that boldtext can be overridden also for function tags
2017-07-07 10:27:18 +02:00
79971a309f
docs: remove the mention of backslashes for the argument of 'comment'
...
Also remove the backslashes from the two syntaxes that contained them.
This completes the fix for https://savannah.gnu.org/bugs/?51370 .
2017-07-07 10:15:17 +02:00
1ae97076cd
docs: make the guillemot and the middle dot appear correctly in HTML
...
For the man page, encode them properly, and for the Info stuff,
just set the right document encoding.
This fixes https://savannah.gnu.org/bugs/?51369 .
2017-07-03 13:03:54 +02:00
09f516a58b
syntax: man, groff: fix the string that introduces a comment
...
The comment marker is not «."» but «.\"», which requires three
backslashes to specify. Also adjust the documentation.
2017-07-03 11:07:21 +02:00
025232b25b
docs: mention the default values for comment and whitespace directives
...
Also, use proper mark-up for the examples.
2017-07-03 10:43:09 +02:00
9ffd3c0222
docs: consistently describe the -U/-c and -r/-w overrides
2017-06-29 17:48:50 +02:00
6520aa0079
bump version numbers and add a news item for the 2.8.5 release
2017-06-25 10:37:17 +02:00
b4a955512e
docs: spell "title bar" and "status bar" correctly
2017-06-18 20:09:30 +02:00
5907f8801b
bump version numbers and add a news item for the 2.8.4 release
2017-05-21 10:21:03 +02:00
afd8a4e804
bump version numbers and add a news item for the 2.8.3 release
2017-05-18 11:53:19 +02:00
e1e15fd0f4
bump version numbers and add a news item for the 2.8.2 release
2017-05-04 10:24:54 +02:00
ac1444578c
docs: harmonize the nanorc man page and Info document a bit
...
And make the strings after "start=" and "end=" more readable.
2017-04-21 11:29:19 +02:00
9a4c384afa
docs: reword the main paragraph of the man page
...
Mention some things that really set nano apart from Pico.
Plus some other small tweaks here and there.
2017-04-19 20:31:04 +02:00
bbc718633e
docs: mention that also numbercolor overrides boldtext
2017-04-16 19:30:40 +02:00
1e8f6fd7a9
bump version numbers and add a news item for the 2.8.1 release
2017-04-12 10:11:45 +02:00
754c62c5cc
copyright: update the years, use ranges, and explain this usage
...
The interval 2013-2017 for the Free Software Foundation is valid
because in those years there were releases with changes by either
Chris or David, and the GNU maintainers guide advises to mention
a new year in all files of a package, not just in the ones that
actually changed, and be done with it for the rest of the year.
2017-04-09 12:09:23 +02:00
032030566c
bump version numbers and add a news item for the 2.8.0 release
2017-03-31 10:54:55 +02:00
6d873d3760
startup: add option 'nopauses' to disable pausing after a warning
...
This addresses a followup of https://savannah.gnu.org/bugs/?50362 .
Reported-by: Mike Frysinger <vapier@gentoo.org>
2017-03-16 19:26:39 +01:00
926fe5f789
bump version numbers and add a news item for the 2.7.5 release
2017-02-23 11:33:45 +01:00
f119a90fe5
bump version numbers and add a news item for the 2.7.4 release
2017-01-10 11:29:34 +01:00
6981294c9d
build: move all documentation into a single directory
...
There are just a handful of source files for the documentation --
it is wasteful and cumbersome to have these in separate directories.
Also: remove the French man pages -- they are too far out of date.
(And anyway, we should acquire a general framework for translating
the documentation.)
2016-12-30 22:05:00 +01:00
Benno Schulenberg