Ctrl+V, and this is going to
cause problems.
Benno
OpenPGP_signature.asc
Description: OpenPGP digital signature
quot;groff"; is not shipped]
That's too much trouble -- if I can't `apt install` it, I won't bother.
Benno
OpenPGP_signature.asc
Description: OpenPGP digital signature
solution (since nano-7.0) is to add two lines to your .nanorc:
## For snipping trailing blanks when you save a file:
bind ^S "{execute}| sed 's/\s\+$//' {enter}{savefile}" main
Benno
OpenPGP_signature.asc
Description: OpenPGP digital signature
the trimming of all trailing whitespace yourself.
Search for "snipping" in the sample nanorc:
grep -A1 snipping /usr/share/doc/nano/examples/sample.nanorc
That gives:
## For snipping trailing blanks when you save a file:
# bind ^S "{execute}| sed 's/\s\+$//' {enter}{sa
) that is in Bullseye was still linked
against Slang, which has its own ideas about what which terminals do.
The nano-udeb (7.2) that is in Bookworm links against ncurses, and
ncurses wants TERM to be set to something valid -- something for
which a terminfo file is available.
Benno
Dear Florian,
On 18/10/2022 13:01, Florian Schlichting wrote:
On Mon, Oct 10, 2022 at 12:46:57PM +0200, Benno Overeinder wrote:
Unfortunately the problem persists after updating to davical 1.1.11-1. I see
the same messages in the Apache2 error.log as previously reported.
looking at your
Thank you for your message.
Unfortunately the problem persists after updating to davical 1.1.11-1. I
see the same messages in the Apache2 error.log as previously reported.
I am available to debug and test, as long as I can install packages or
other necessary software.
-- Benno
-- System
x27;, then multibuffer is available.)
I've added a note at the start of each old FAQ saying that it is
an old FAQ, and with a link to the latest FAQ.
Benno
OpenPGP_signature
Description: OpenPGP digital signature
tice] [pid 49688] [client
192.168.1.1:64521] davical: LOG: headers:-->Content-type: text/plain;
charset="utf-8"
[Fri Feb 18 21:14:59.311259 2022] [php:notice] [pid 49688] [client
192.168.1.1:64521] davical: LOG: : Response
[Fri Feb 18 21:14:59.3
!
-- Benno
Package: wireplumber
Version: 0.4.7-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: be...@overeinder.net
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
After a recent upgrade of wireplumber, vlc freezes for abou
Some additional information.
On 24/01/2022 11:58, Benno Overeinder wrote:
* What exactly did you do (or not do) that was effective (or
ineffective)?
I have looked at the apache2 log files and checked the /etc/php and
/etc/davical directories if there were any references to php7
Package: davical
Version: 1.1.10-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: be...@overeinder.net
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I am using debian testing. After upgr
Sorry, that was my Yaml test file (all the Yaml fragments from
the Wikipedia article).
Correct file is attached now.
Benno
## Syntax highlighting for YAML files.
## Original author: Benno Schulenberg
## License: GPL version 3 or newer
(Adjusted to work on older nanos -- V2.)
syntax
stuff, there can
be keys that contain a double colon, so I've added that to the rules.
Improved version of the syntax file (for older nanos) is attached.
(I've also dropped the 'tabgives' command, as that probably doesn't
work in your version of nano.)
Benno
yaml.yaml
5.0 or later).
Attached is a version that should work on older nanos (but shows too much
bold and some other colors than the intended ones, and is fully readable
only on a terminal with a dark background).
Benno
## Syntax highlighting for YAML files.
## Original author: Benno Schulenberg
## L
Op 08-02-2021 om 16:46 schreef Benno Schulenberg:
> But it's unclear what license covers the file -- the site says nothing
> about the yaml.nanorc.
I mailed the author but did not get a response. So this morning I
constructed my own yaml.nanorc file -- see attached.
What I'm qu
Op 11-08-2021 om 09:51 schreef Benno Schulenberg:
> Nano will "run" in any terminal, but the user (or rather: the system) /must/
> specify the terminal. There does not seem to be a way for a program to probe
> which terminal is being used.
Mitigated in git, commit 46cdf8b7,
saster can leave TERM unset?
You didn't answer the question.
> posix said about vi that the behavior for empty term should be consistant
> and documented. If nano want to be a vi replacement it should be consistant.
Who says that nano wants to be a replacement for vi?
Benno
OpenPGP_signature
Description: OpenPGP digital signature
for -- that is: a non-functioning nano.
Benno
OpenPGP_signature
Description: OpenPGP digital signature
to exist? I ask,
because 'dumb' and 'vt52' are not good enough for nano (ncurses) to work
properly, and 'ansi' leaves the cursor invisible on a VTE-based terminal.
Benno
OpenPGP_signature
Description: OpenPGP digital signature
om). If you wish this yaml.nanorc to be included in nano,
please ask him if he will license this file under GPL v3+. (When you
do so, please CC me.) Or provide a file that you have designed yourself.
Benno
signature.asc
Description: OpenPGP digital signature
ve checked that a nano_5.3-1_amd64.deb downloaded from a Debian
mirror still contains those malformed lines in the included /etc/nanorc.
It would be nice if this would get fixed for the next iteration.
Benno
signature.asc
Description: OpenPGP digital signature
452d49b2339e607365b6652987
https://github.com/NLnetLabs/unbound/commit/a08fe8ca609b651c8d8c8379780aad508d492421
Best,
— Benno
--
Benno J. Overeinder
NLnet Labs
https://www.nlnetlabs.nl/
p1_and_2.diff
Description: Binary data
the
user -- because the BOM is part of the file format and must of course stay
where it is. And 2) you want to be able to remove the BOM in some way.
But... in what circumstances would you want to remove the BOM?
Another question. These *.ass files, are they in DOS format?
Or do you also have U
nd add it back when it is written. But that would
make it impossible to delete an unwanted BOM with a simple backspace.
Then the user would need to fall back to a tool like dos2unix.
Benno
diff --git a/src/nano.c b/src/nano.c
index 8e8b9952..db213857 100644
--- a/src/nano.c
+++ b/src/nano.c
@@ -1
ugs.launchpad.net/ubuntu/+source/nano/+bug/1045062
Benno
diff --git a/src/files.c b/src/files.c
index 04476c44..aad58b78 100644
--- a/src/files.c
+++ b/src/files.c
@@ -459,7 +459,10 @@ bool open_buffer(const char *filename, bool new_one)
openfile->lock_filename = thelocksname;
#endif
openfile-&
nano in an existing shell. So, why
not apply the patch that Marco posted?
However, Andrew, it is a very tiny bug. When you encounter it, the
solution is to tell the shell to forget the paths it cached, with:
hash -r. It does not require restarting the terminal or the shell.
Benno
sig
n the packaging of grub? Or did they
eliminate the script? Or were the scripts moved to a separate
package?
Benno
signature.asc
Description: OpenPGP digital signature
ii libc62.27-3ubuntu1
From 242992a278fc67cab3e0ce6586da75fa697780a0 Mon Sep 17 00:00:00 2001
From: Benno Schulenberg
Date: Sun, 3 May 2020 14:11:03 +0200
Subject: [PATCH] accept also translations of "on" when detecting auto-added
menu items
When a system is localized, then the ti
Op 03-02-2020 om 14:56 schreef Jonas Smedegaard:
> Quoting Benno Schulenberg (2020-02-03 14:23:38)
>> I see. However, the files in include statements can only contain
>> color syntaxes, not any option settings.
>
> Oh! I missed that "minor detail" which chang
nstall
an /etc/nanorc at all, but would instead have included the contents
of that file as /etc/skel/.nanorc, so that it gets copied into each
user's home directory at account creation, and the user can edit it
and strip from it anything that is unneeded or unwanted.
Benno
signature.asc
Description: OpenPGP digital signature
's address (with maybe a CC to the last translator).
You can find the addresses in the po/da.po file, or on:
https://translationproject.org/team/da.html
Benno
signature.asc
Description: OpenPGP digital signature
the one and only
nanorc file to read (which can of course have include statements).
This allows the user to skip an /etc/nanorc that has unwelcome
settings or includes.)
Benno
signature.asc
Description: OpenPGP digital signature
Op 31-01-2020 om 16:44 schreef Jonas Smedegaard:
> Quoting Benno Schulenberg (2020-01-31 14:19:10)
>> For ^C, yes, I will make the suggested change.
Fixed in git: https://git.savannah.gnu.org/cgit/nano.git/commit/?id=0a52e92d
>>> #bind ^S savefile main
>
> Ah, I wasn u
ault bind, so there is no need to make it. Or do you
wish to have it listed for documentation purpose, so that the user knows
from reading that list which important keystrokes are available in that
alternative set?
Benno
signature.asc
Description: OpenPGP digital signature
changed
from to , so that it is much less likely to be typed by
accident, and to free up the keystroke for other prograsm. So I would
like to see the above fragment changed to:
} elsif ($mainsym eq 'Up') {
$vector[$coord + 12] = 'KeyboardSignal';
}
Benno
I'm considering applying the attached patch.
Anything else you would like to see added?
Benno
From f8cdeb3386695b61d7918c9c43178d26ba4757cd Mon Sep 17 00:00:00 2001
From: Benno Schulenberg
Date: Tue, 6 Aug 2019 18:51:58 +0200
Subject: [PATCH] syntaxes: recognize .ctp extension as a PHP
ke more sense
> than -l because permit to make copy paste without line number.
Understood.
> (my en is very poor)
Si tu veux, tu peux écrire en français. Je comprendrai.
>> Why not make or upload a .nanorc file for the relevant user?
> it take time ;)
Which you will quickly regain by seeing things better. :)
Benno
n alias: alias nano="nano --line --soft"?
(By the way, the short option for line numbers is -l, not -c;
-c is for constantly showing the cursor position.)
Why not make or upload a .nanorc file for the relevant user?
Benno
s if the wrapped stuff
is a separate line (unlike vim: it skips to the next true line).
Benno
The bug has been fixed in git, commit 1b2018e9:
http://git.savannah.gnu.org/cgit/nano.git/commit/?id=1b2018e9
The fix will appear in version 4.3.
Benno
since then)
gives back the ability to edit a FIFO to nano-4.2. So... I will be
looking into this, also because is_file_writable() causes another issue:
https://savannah.gnu.org/bugs/?29312
Benno
hat the LF was selected; then doing
'Paste' after 'Copy' will paste the LF too. Please try it, and
report back.
Benno
th type and drag a window edge at the
same time.
Benno
ug as bug #787914, and is fixed since 2.4.3.
Benno
Hello Sebastien,
I don't understand the original report. What is $HOME/.nano_saved-files
used for? Does Debian create this directory upon installing nano? Because
as far as I know, nano itself does not create it.
Regards,
Benno
cters, not multibyte UTF-8
ones.) So... I'm inclined to attribute the problem that you saw
to some misconfiguration of the locale settings. But maybe you can
shed some more light on this?
Regards,
Benno
'set stripecolor'.
Benno
Attached is a version with a working --edge option,
plus some other buglets ironed out.
Benno
From 7f2d295b6e85bec215d355c2dd347fda019b7e22 Mon Sep 17 00:00:00 2001
From: Benno Schulenberg
Date: Mon, 17 Dec 2018 19:57:30 +0100
Subject: [PATCH] possible new feature: add option --edgecolumn that
Please try the attached patch.
Use --edge= to show a colored bar at the desired column.
Benno
From 119491bbdedf2c727135e5e331f0714d94644351 Mon Sep 17 00:00:00 2001
From: Benno Schulenberg
Date: Mon, 17 Dec 2018 19:57:30 +0100
Subject: [PATCH] new feature: add option --edgecolumn that shows a
"limit" is baked in as 68;
it would of course have to become settable by some option.
This doesn't give you an indication of how many columns you can
still use before reaching the limit, but this is the best I can
do with a simple patch.
Benno
diff --git a/src/winio.c b/src/winio.c
nly the
udeb version should use --with-slang, *if* the installation environment
does not provide ncurses.)
Benno
Control: retitle -1 "the order of syntax definitions in nanorc matters"
Control: fixed -1 2.3.2-1
Control: fixed -1 2.3.6-1
Control: fixed -1 2.6.3-1
fixed -1 1.0.0-1
tags fixed-upstream
stop
Hunspell (and any other speller) is supported via the 'speller' command
and the --speller option. No need to hard bind nano to a certain speller.
Benno
Control: fixed -1 2.7.3-1
Stop
Since nano-3.0, deletes the word to the right of the cursor,
and deletes the word to the left.
If you never use ^H, on some terminals you can also make
delete the word to the left of the cursor when you add in your ~/.nanorc:
bind ^H cutwordleft main
Benno
u tell me which script or
recipe is used to build nano-udeb? So that I stand a chance to
build a comparable version.
Benno
our
nanorc file, then nano will not pause at all between warnings and
you will get to see the first file immediately.
So... if you want the new behavior, you could set your package manager
to allow it to install nano from "testing" instead of from "stable".
Regards,
Benno
gmerge has filled in because of similarity with
another msgid.
What's more, 'msgfmt -cv' will report an error for the above msgstr,
so your solution will fail for a couple of languages.
Regards,
Benno
avoided entirely by putting the linked list
of syntaxes upside-down and not bothering to free a redefined
syntax at all.
Benno
you redefine later.
You could also prevent this by simply giving your awk syntax
a different name. Not the file, but the syntax. For example:
syntax "WAAK" ...
As long as the file regex and header regex catch all your awk
and gawk and mawk files, it will work. The name is just meant
so you can force a syntax on the command line: --syntax=python.
Benno
rumour was caused by your bug report three years ago. :)
Let's find out where things go wrong by first making your situation as standard
as possible, as described above, and then making small modifications.
Regards,
Benno
Hello Bernward,
Please see my answer from two years ago on the Debian page for this bug
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743179). I didn't
know then that one has to CC the reporter in order to get a message
across.
Regards,
Benno
On 2017-01-03 13:12, Benno Schulenberg wrote:
> To show exactly what I mean, I've also attached an example nanorc
> file, which you could copy over your ~/.nanorc file.
Ehm... I didn't actually attach the file... Man! How many more
mistakes will I make? :|
Now then.
Benn
hat I mean, I've also attached an example nanorc
file, which you could copy over your ~/.nanorc file.
Benno
few who use
files that have the same extension as files of other languages
it will cause frowns.
Benno
x, you could use the option -Ynone
when editing MUMPS files. (You could make an alias that includes this
option.)
> The files could be edited just like I have for years and just like I
> am editing this file.
It worked fine in an earlier version of nano? Which version was that?
Benno
On 2016-12-23 08:55, Arturo Borrero Gonzalez wrote:
> On 22 December 2016 at 19:17, Benno Schulenberg wrote:
>> Have you also tried removing the \ from \@?
>
> Yes, it works too.
Thanks. Committed and pushed: 2fbb71d5. It will be in 2.7.3 next week.
Regards,
Benno
On 2016-12-21 12:34, Jordi Mallach wrote:
> Benno, there's also #801103, which I've been wondering about.
I'm not pushing much on that, because how many people use Groovy?
How many GNU/Linux systems have Groovy installed? True, there are
also other syntax files that almos
On 2016-12-22 13:30, Arturo Borrero Gonzalez wrote:
> On 21 December 2016 at 13:55, Benno Schulenberg wrote:
>> I've reordered the families, and condensed the variables.
>> Please verify that this is okay. (I think, though, that
>> the "\" in "\@"
Hello Arturo,
On 2016-12-21 12:55, Arturo Borrero Gonzalez wrote:
> Signed-off-by: Arturo Borrero Gonzalez
I've reordered the families, and condensed the variables.
Please verify that this is okay. (I think, though, that
the "\" in "\@" is superfluous.)
See
?
Before when do you want a release, Jordi, in order to get it into
Stretch still?
Regards,
Benno
A fix for this was pushed to git, commit 2eafe7b.
Will be in nano-2.6.3.
(The patch applies cleanly to 2.6.1 or 2.6.2, if you want to test
beforehand.)
Benno
From 2eafe7bf582a7e9b978789d108ad969e4577f11b Mon Sep 17 00:00:00 2001
From: Benno Schulenberg
Date: Mon, 1 Aug 2016 15:50:37 +0200
from vim. But if vim does it correctly,
then it was copied incompletely and it will get fixed.)
Benno
-O, M-S, M-T, and
of course ^S and ^Q, which key strokes would you prefer to use for
cutwordleft and cutwordright?
Benno
After having just updated a system, it is best to run 'hash -r',
to tell the shell to forget everything it thinks to know about
paths. After that, it should find nano again. Logging back in
should work too. If that does not solve it, please report back.
On Mon, Dec 14, 2015, at 12:34, Arturo Borrero Gonzalez wrote:
> On 17 November 2015 at 14:57, Benno Schulenberg
> wrote:
> > Please try the attached patch. (You have to undo the previous patch.)
> > It works here on a Pantheon terminal.
>
> It works, thanks.
Tha
On Wed, Dec 2, 2015, at 09:46, Arturo Borrero Gonzalez wrote:
> On 1 December 2015 at 21:34, Benno Schulenberg wrote:
> > Are you okay with this version?
>
> yeah, thanks!
In SVN, r5465. Should be in the next release.
Thanks.
Benno
--
http://www.fastmail.com - Or how I
Hi Arturo,
Thanks for the update.
Attached is a slightly modified version of the file:
I've alphabetized the words, and contracted a few of
them. Are you okay with this version?
Regards,
Benno
--
http://www.fastmail.com - A no graphics, no pop-ups email service
nftables.n
Hi Emmanuel,
Thanks for the suggestion.
Added in SVN, r5435. Should be in the next release.
(By the way, will you post an update of the Groovy file
on the other bug?)
Regards,
Benno
--
http://www.fastmail.com - mmm... Fastmail...
s.
You might even write it as:
header "^#!.*nft(ables)"
Benno
--
http://www.fastmail.com - The professional email service
Thanks for the report. This should be fixed in nano-2.4.3.
(The hard limit is still there, but that is because we simply
don't need more characters. But now the overflow case is
handled properly.)
Benno
--
http://www.fastmail.com - The professional email service
himself
to realize how this worked, and how to obtain the actual key code.
(Thanks, Thomas.)
Please try the attached patch. (You have to undo the previous patch.)
It works here on a Pantheon terminal.
Benno
--
http://www.fastmail.com - Same, same, b
ok
possible for a KDE Konsole (if a modern Konsole produces
different codes still from a pantheon or xfce).
Benno
--
http://www.fastmail.com - A no graphics, no pop-ups email service
gnome-terminal too, pantheon...
Hmm, what does 'env | grep -i term' say in your case?
For me it outputs:
TERM=xterm
COLORTERM=gnome-terminal
Benno
--
http://www.fastmail.com - Send your email first class
e these codes
come from. I haven't been able to find them in the source of
xfce4-terminal nor of pantheon-terminal. Nor are the defined
anywhere in ncurses. So... do I simply have to try all kinds
of terminals and add all those codes to nano? Puzzles...
For now you can use your patched nano,
Hello Clancy,
Thanks for your report, and for your patience.
I believe I have it fixed with the attached patch.
If you could try and test it, that would be great.
(It should apply cleanly to 2.4.2, with only offsets.)
--
http://www.fastmail.com - Or how I learned to stop worrying and
On Tue, Nov 3, 2015, at 20:35, Arturo Borrero Gonzalez wrote:
> On 31 October 2015 at 16:14, Benno Schulenberg wrote:
> > Anyway, when you apply the attached patch to your self-compiled
> > source tree and rerun make, src/nano should behave correctly.
> > Does it?
>
>
ce or an opening parenthesis. Afterward one can
then colour all periods and parentheses in some other colour.
(What nano is lacking is the colour "none", to uncolour things
that were coloured by earlier regexes.)
Benno
--
http://www.fastmail.com - mmm... Fastmail...
On Sat, Oct 31, 2015, at 13:03, Arturo Borrero Gonzalez wrote:
> On 30 October 2015 at 13:27, Benno Schulenberg wrote:
> >
> > src/nano README 2>TRAIL
> >
> > press Ctrl+Right three times, and Ctrl+Left twice,
> > and then Ctrl+X and attach the TR
syntax uses this too,
but it's terrible -- I try to avoid it in all new syntaxes.
Also, in the Wikipedia article, many more things are coloured.
Maybe you could extend your groovy.nanorc before I commit it
to SVN?
https://en.wikipedia.org/wiki/Groovy_%28programming_language%29
Benno
--
es, and Ctrl+Left twice,
and then Ctrl+X and attach the TRAIL file here?
(Meanwhile you could of course add the following lines
to your nanorc:
bind ^B prevword main
bind ^N nextword main
and use those key combos instead.)
Benno
--
http://www.fastmail.com - Or how I learned to stop worrying and
On Fri, Oct 30, 2015, at 12:21, Arturo Borrero Gonzalez wrote:
> On 30 October 2015 at 12:18, Benno Schulenberg wrote:
> > But... do the Ctrl+Left and Ctrl+Right key combinations
> > not work for you inside nano to go to the previous/next word?
> > If not, what terminal e
ual.
That your keyboard/terminal accepts the next character
while you are still holding the Esc key is a nice feature,
but is not universal.
But... do the Ctrl+Left and Ctrl+Right key combinations
not work for you inside nano to go to the previous/next word?
If not, what terminal emulator are yo
of changes I have made to the code. See:
https://lists.gnu.org/archive/html/nano-devel/2015-10/msg1.html
So... a little more patience, to see how this pans out.
Or maybe you can let your voice be heard, as a somewhat high-profile
nano user?
:)
Benno
--
http://www.fastmail.com - The professio
gs = NULL;
#endif
}
This fixes it for me.
Fixed in SVN, r5338. Should be in 2.4.3.
Benno
--
http://www.fastmail.com - Does exactly what it says on the tin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
1 - 100 of 148 matches
Mail list logo
