Package: nano
Version: 7.2-1
Severity: normal
Dear Maintainer,
Upstream changed the literal control characters in their "nanorc.sample"
file[1] to the new
"{function}" syntax in v7.0, but it looks like this change wasn't synced into
the Debian-provided
"/etc/nanorc" file[2], unlike the other changes in this version.
I guess this was an oversight? Seems many text editors get caught up on them
(particularly the "CR"
character - that's what caused me to investigate why they were there in the
first place!)
Thanks, Sam
[1] https://git.savannah.gnu.org/cgit/nano.git/commit/?id=2a515058
[2] https://salsa.debian.org/debian/nano/-/commit/4ce7611e
-- System Information:
Debian Release: 12.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-5-amd64 (SMP w/1 CPU thread; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages nano depends on:
ii libc6 2.36-8
ii libncursesw6 6.4-2
ii libtinfo6 6.4-2
nano recommends no packages.
Versions of packages nano suggests:
pn hunspell <none>
-- no debconf information
