lp:nano

Branch merges

This import branch has no branches proposed for merge into it.

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

10199. By Benno Schulenberg on 2023-11-25

display: show the help lines down to the tiniest possible terminal size

That is: compute the minimum needed terminal height more accurately.

10198. By Benno Schulenberg on 2023-11-25

general: let the constant-show toggle override the zero-interface mode

When the user hits the M-C toggle while option --zero is in effect,
instead of complaining "Not possible", do what the user probably
tries to achieve: cancel `zero` mode and switch on `constantshow`.

10197. By Benno Schulenberg on 2023-11-24

bindings: make ^F start a forward search by default

This makes nano more usable for users that are accustomed to the
near universal use of ^F for Find/Search in other programs, and
especially for users that somehow access a terminal through their
browser (where ^W will, destructively, close the terminal tab).

(To keep the bindings consistent, make ^B start a backward search,
and let M-F and M-B search for the next occurrence in the matching
direction.)

Suggested-by: Chris Allegretta <email address hidden>
Suggested-by: Donnie Ferris <email address hidden>
  https://lists.gnu.org/archive/html/nano-devel/2023-01/msg00001.html

10196. By Benno Schulenberg on 2023-11-24

undo the prelast commit in order to redo it with a fuller commit message

10195. By Benno Schulenberg on 2023-11-22

docs: mention how to get the old behavior of ^F, ^B, M-F, and M-B back

10194. By Benno Schulenberg on 2023-10-30

bindings: make ^F start a forward search by default

This makes nano more usable for users that are accustomed to the
near universal use of ^F for Find/Search in other programs.

To keep the bindings consistent, make ^B start a backward search,
and let M-F and M-B search for the next occurrence in the matching
direction.

10193. By Benno Schulenberg on 2023-10-16

input: neutralize two spurious keycodes from VTE terminals

At least some of the VTE-based terminals claim to be compatible with
xterm-25color (and set TERM to that value). But they really aren't:
they mishandle the focus-in and focus-out events, for example. So,
catch and discard the corresponding keycodes that nano shouldn't be
seeing at all.

This improves the fix for https://savannah.gnu.org/bugs/?64578.

10192. By Benno Schulenberg on 2023-10-03

tweaks: adjust a comment for the changed handling of gray #rgb codes

10191. By Andy Koppe <email address hidden> on 2023-09-25

rcfile: map the gray #rgb codes (#111 to #EEE) to the xterm grayscale

When the red, green and blue components of a three-digit hex #RGB code
are equal and they aren't #000 for black or #FFF for white, map them to
xterm-256color's 24-level grayscale ranging from index 232 to 255.

This means that the 14 gray levels available in #RGB codes all map to
different tones, whereas previously they mapped to only the four gray
tones available in the 6x6x6 color cube.

Signed-off-by: Andy Koppe <email address hidden>

10190. By Benno Schulenberg on 2023-08-29

tweaks: add a comment that refers to the VTE spurious-code issue