gmane.editors.nano.devel

Spanish translation for current

Jorge González — 2013-05-04T10:52:32

Hello,

I have translated, reviewed and fixed the current translation of nano,
since there were several mistakes, fuzzy and untranslated strings.

Please find it attached, since I am completely unable to register in
Savanna and post it there.

Best regards.

ANNOUNCEMENT: Exciting news about our acquisition byVIM [PATCH]

Chris Allegretta — 2013-04-01T08:20:33

Hello,

First, I want to give a hearty thank you to all our users and
developers who have been using nano all this time.  I wanted you let
you know that I received word from the FSF legal offices that we have
been acquired by VIM, hopefully putting to rest a lot of bad blood
between the text editor factions.

For those of you who have been keeping up with development, the key
bindings code and vim-style locking were probably dead giveaways that
this was going to happen soon, and congrats to everyone who figured
this out before today.

For those of you who have contributed to the code base, the details of
this deal are as follows:
- All right, likenesses and the nano domain become the property of the
VIM Development Corporation LLC OMG WTF BBQ
- Our recursive acronym Nano's Another Editor, is being changed to the
classic vi  tagline, "What Mode Am I In Again??"

In exchange, the following compensation is being offered:
- One thousand "vim rules" bumper stickers (FCFS on these!)
- At least 150 coupons for a free KFC Double Down.  Must give your
name as "vim" when you order.  No free refills.
- We will be recognized on a special plaque, near home plate at a
to-be-announced  vim-owned sports stadium (once a few more tech
companies go under or are bought by Google).
- That happy feeling that we didn't end up owned by emacs

The attached patch is a sneak peak at the transition plan we will be
using in the development versions of nano.  Please see the following
timetable for transition:

- Starting today with this patch, through versions
2.4.99pl47-omg[ac]1, nano will continue to default to what is
effectively vim's Insert Mode.  You can get into insert mode via Esc,
or the usual method of pressing random keys until it works.
- As of version 2.5.0, Command Mode will become the default, but we
will retain backward compatibility with legacy nano commands
- In version 2.7.0, we will all be dead by then so don't worry about
it.  Have you seen how long just point releases take me? :P

Thank you again for using our editor, and I'm looking forward to
seeing all those bumper stickers in the KFC parking lot.  Eat up
friends, we've all earned it!
_______________________________________________
Nano-devel mailing list
Nano-devel< at >gnu.org
https://lists.gnu.org/mailman/listinfo/nano-devel

[bug] after a writeout,nano sees original file as changed

Benno Schulenberg — 2013-03-30T20:15:21

Hi,

After writing out a marked portion of text to a separate file,
nano says the original file has changed when trying to save
the current full buffer.  To reproduce:

src/nano ChangeLog
<Alt+A>  <Arrow down>  <Ctrl+O>  <X>  <Enter>
<Alt+A>  <Ctrl+O>  <Enter>

Result:

"File was modified since you opened it, continue saving ?"

But the file was not changed and has not changed.  The
message is confusing.

(Bug encountered in nano-2.2.5, still present in SVN.)

Regards,

Benno

GNU nano 2.3.2

Chris Allegretta — 2013-03-22T14:08:57

is released

2013.03.22 - GNU nano 2.3.2 "Annoy your coworkers for fun and profit" is
                released.  This release introduces vim-style file locking
                (though not backup/restore), useful when using nano
                in a multi-editor environment.  Feedback is welcome if
                you run into any issues with this new code.  Other new
                features include additional support for word boundary
                checking when cross compiling, fixes for trying to go to
                an invalid line number, and the usual documentation
                tweaks.

nano 2.3.2pre4

Jean-Philippe Guérard — 2013-03-18T23:24:15

Hello,

I'm working on updating the French translation of nano.

In the latest batch, the following string seems a bit suspicious to me:

#: src/files.c:143
#, c-format
msgid "Couldn't determine hosttname for lock file: %s"
msgstr ""

Thanks.

Tab copy and paste?

Joshua Rogers — 2013-02-23T09:54:50

Hi,

Perhaps this is the wrong place to ask, but is it possible to preserve
the tab character then copy and pasting within Nano?
I really love Nano for coding small applications, but sometimes I need
to copy and paste some things from a few lines up, but it is problematic
because I have to remove all the spaces and re-add the tab.

I looked over the manpage, but couldn't find anything.

Thanks

[patch] colorizing more manpage format strings

Benno Schulenberg — 2013-01-28T16:59:16

Hi,

When editing man pages, nano does not color the lines that
start with .RB (for alternating normal and bold).  Attached
patch is a suggestion to add this coloring.  It simplifies the
expression by coloring in some cases also the subsequent
space.

Nano also does not color the lines that start with .SS
(a subsection header).  The patch fixes that too.

Does this look okay, Mike?

Regards,

Benno

2.3.2pre3

Chris Allegretta — 2013-01-21T21:12:52

Now up at http://nano-editor.org/dist/test/nano-2.3.2pre3.tar.gz and
should contain reasonable fixes for the recently discussed resize
during justify, invalid goto line # and the official fix for
cross-compiling and GNU-style word boundaries.  Still working on some
latent syntax highlighting problems pointed out by way of Savannah
patch 7561, but hoping to get an official release out soon.

[patch] fixing the failing redisplay of the file list

Benno Schulenberg — 2013-01-14T17:12:33

Hi,

After the sequence ^R ^T ^W ^G ^X, not the list of files gets
redisplayed but the current edit buffer.  Rather confusing.  The
same happens for ^R ^T ^_ ^G ^X.  Attached patch fixes this.
(This is probably not the fully correct nor an elegant solution,
but it works.)

Cheers,

Benno

[patch] update some translator comments and othertweaks

Benno Schulenberg — 2013-01-13T14:26:28

Hi,

Attached patch updates three translator comments to match the
current situation.  Further it reorders the "Next Word" command
to match the order of the "Prev Line"/"Next Line" commands.

It also removes several irregular/superfluous blank lines, adds a
comment, removes one space, and fixes a typo in a comment.

The second patch fixes a few typos in the NEWS file:
checkng => checking, allowing => allow, updated => updates,
plus better linewraps.

Regards,

Benno

[patch] allow ^C to exit from Help

Benno Schulenberg — 2013-01-13T13:44:04

Hi,

Attached patch adds the key combo <Ctrl+C> as a way to exit
from the display of a help text.  It is kind of the natural
combo when the user wishes to "undo" or "stop" something,
and in the rest of nano it is used as such.

The patch also removes two superfluous lines; the ^X and F2
keys have been added already near the start of the list.

Regards,

Benno

Vulnerability

Joshua Rogers — 2013-01-12T00:11:00

Which email would be the best to report a vulnerability in GNU Nano?

Thanks

[PATCH] do not write to stderr on magic errors

Mike Frysinger — 2013-01-04T19:33:01

If the magic db has errors such that magic_load() fails, the current
code dumps to stderr which messes up the ncurses terminal control.

The error message is also vague to the point where it's confusing.
I thought nano had problems writing to the file I was editing.

Instead, use statusbar() and clarify the messages.

Signed-off-by: Mike Frysinger <vapier< at >gentoo.org>
---
 src/color.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/color.c b/src/color.c
index e5d3348..3ddd9d6 100644
--- a/src/color.c
+++ b/src/color.c
< at >< at > -161,19 +161,19 < at >< at > void color_update(void)
 
 #ifdef HAVE_LIBMAGIC
 
-    if (strcmp(openfile->filename,"") && stat(openfile->filename, &fileinfo) == 0) {
+    if (stat(openfile->filename, &fileinfo) == 0) {
 m = magic_open(MAGIC_SYMLINK |
 #ifdef DEBUG
                        MAGIC_DEBUG | MAGIC_CHECK |
 #endif /* DEBUG */
                        MAGIC_ERROR);
 if (m == NULL || magic_load(m, NULL) < 0)
-    fprintf(stderr, "something went wrong: %s [%s]\n", strerror(errno), openfile->filename);
+    statusbar("magic_load() failed: %s", strerror(errno));
 else {
     magicstring = magic_file(m,openfile->filename);
     if (magicstring == NULL) {
 magicerr = magic_error(m);
-fprintf(stderr, "something went wrong: %s [%s]\n", magicerr, openfile->filename);
+statusbar("magic_file(%s) failed: %s", openfile->filename, magicerr);
             }
 #ifdef DEBUG
     fprintf(stderr, "magic string returned: %s\n", magicstring);

[PATCH] ignore generated files

Mike Frysinger — 2013-01-03T19:11:19

Signed-off-by: Mike Frysinger <vapier< at >gentoo.org>
---
 .gitignore | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/.gitignore b/.gitignore
index 21b165d..b285320 100644
--- a/.gitignore
+++ b/.gitignore
< at >< at > -1,9 +1,14 < at >< at >
+*~
 *.o
 .deps
 .libs
 Makefile
 Makefile.in
 
+core
+.gdb_history
+.gdbinit
+
 /ABOUT-NLS
 /INSTALL
 /aclocal.m4

[PATCH] rename INCLUDES to AM_CPPFLAGS

Mike Frysinger — 2013-01-03T19:11:22

Automake changed the naming of these a while ago, and at least version
1.13 now starts warning about it:
src/Makefile.am:2: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')

Signed-off-by: Mike Frysinger <vapier< at >gentoo.org>
---
 src/Makefile.am | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/Makefile.am b/src/Makefile.am
index f0b21c0..a0af063 100644
--- a/src/Makefile.am
+++ b/src/Makefile.am
< at >< at > -1,5 +1,5 < at >< at >
 localedir = $(datadir)/locale
-INCLUDES = -DLOCALEDIR=\"$(localedir)\" -DSYSCONFDIR=\"$(sysconfdir)\"
+AM_CPPFLAGS = -DLOCALEDIR=\"$(localedir)\" -DSYSCONFDIR=\"$(sysconfdir)\"
 
 ACLOCAL_AMFLAGS = -I m4

memory error in svn rev 4547

Mike Frysinger — 2013-01-02T06:34:04

hmm, looks like there is a memory error new to the post 2.3.1 release

# check out svn rev 4545
$ ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --
infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --bindir=/bin --enable-color 
--enable-multibuffer --enable-nanorc --disable-wrapping-as-root --enable-speller --disable-justify --disable-debug --enable-nls --
enable-utf8 --disable-tiny --without-slang
$ make clean && make -j
$ ./src/nano /etc/nanorc ~/.nanorc
# hit alt+. to switch to the 2nd buffer
# things work fine

# check out svn rev 4547
$ make clean && make -j
$ ./src/nano /etc/nanorc ~/.nanorc
# hit alt+. to switch to the 2nd buffer
# see crash:

*** Error in `./src/nano': free(): invalid next size (fast): 0x000000000260a280 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7b81d)[0x7fc760b9881d]
/lib64/libc.so.6(+0x7c5f3)[0x7fc760b995f3]
./src/nano[0x426d12]
./src/nano[0x427d39]
./src/nano[0x428858]
./src/nano[0x40853a]
./src/nano[0x4085ad]
./src/nano[0x408616]
./src/nano[0x415864]
./src/nano[0x417183]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fc760b3e975]
./src/nano[0x403aa9]
======= Memory map: ========
00400000-00435000 r-xp 00000000 09:00 121915886                          /usr/local/src/nano/src/nano
00634000-00635000 r--p 00034000 09:00 121915886                          /usr/local/src/nano/src/nano
00635000-00636000 rw-p 00035000 09:00 121915886                          /usr/local/src/nano/src/nano
0240b000-02651000 rw-p 00000000 00:00 0                                  [heap]
7fc75fd41000-7fc75fd57000 r-xp 00000000 08:32 2111208                    /usr/lib/gcc-lib/x86_64-pc-linux-gnu/4.7.2/libgcc_s.so.1
7fc75fd57000-7fc75ff56000 ---p 00016000 08:32 2111208                    /usr/lib/gcc-lib/x86_64-pc-linux-gnu/4.7.2/libgcc_s.so.1
7fc75ff56000-7fc75ff57000 r--p 00015000 08:32 2111208                    /usr/lib/gcc-lib/x86_64-pc-linux-gnu/4.7.2/libgcc_s.so.1
7fc75ff57000-7fc75ff58000 rw-p 00016000 08:32 2111208                    /usr/lib/gcc-lib/x86_64-pc-linux-gnu/4.7.2/libgcc_s.so.1
7fc75ffd9000-7fc75ffda000 rw-p 00000000 00:00 0 
7fc75ffda000-7fc760207000 rw-p 00000000 08:32 2243027                    /usr/share/misc/magic.mgc
7fc760207000-7fc760434000 rw-p 00000000 08:32 2243027                    /usr/share/misc/magic.mgc
7fc760434000-7fc760907000 r--p 00000000 08:32 6747949                    /usr/lib64/locale/locale-archive
7fc760907000-7fc76091c000 r-xp 00000000 08:32 4456549                    /lib64/libz.so.1.2.7
7fc76091c000-7fc760b1b000 ---p 00015000 08:32 4456549                    /lib64/libz.so.1.2.7
7fc760b1b000-7fc760b1c000 r--p 00014000 08:32 4456549                    /lib64/libz.so.1.2.7
7fc760b1c000-7fc760b1d000 rw-p 00015000 08:32 4456549                    /lib64/libz.so.1.2.7
7fc760b1d000-7fc760cc5000 r-xp 00000000 08:32 4462793                    /lib64/libc-2.17.so
7fc760cc5000-7fc760ec5000 ---p 001a8000 08:32 4462793                    /lib64/libc-2.17.so
7fc760ec5000-7fc760ec9000 r--p 001a8000 08:32 4462793                    /lib64/libc-2.17.so
7fc760ec9000-7fc760ecb000 rw-p 001ac000 08:32 4462793                    /lib64/libc-2.17.so
7fc760ecb000-7fc760ecf000 rw-p 00000000 00:00 0 
7fc760ecf000-7fc760f2b000 r-xp 00000000 08:32 4459932                    /lib64/libncursesw.so.5.9
7fc760f2b000-7fc76112a000 ---p 0005c000 08:32 4459932                    /lib64/libncursesw.so.5.9
7fc76112a000-7fc76112e000 r--p 0005b000 08:32 4459932                    /lib64/libncursesw.so.5.9
7fc76112e000-7fc761130000 rw-p 0005f000 08:32 4459932                    /lib64/libncursesw.so.5.9
7fc761130000-7fc76114a000 r-xp 00000000 08:32 5919636                    /usr/lib64/libmagic.so.1.0.0
7fc76114a000-7fc76134a000 ---p 0001a000 08:32 5919636                    /usr/lib64/libmagic.so.1.0.0
7fc76134a000-7fc76134b000 r--p 0001a000 08:32 5919636                    /usr/lib64/libmagic.so.1.0.0
7fc76134b000-7fc76134c000 rw-p 0001b000 08:32 5919636                    /usr/lib64/libmagic.so.1.0.0
7fc76134c000-7fc76136e000 r-xp 00000000 08:32 4466385                    /lib64/ld-2.17.so
7fc7614e7000-7fc7614eb000 rw-p 00000000 00:00 0 
7fc761563000-7fc76156a000 r--s 00000000 08:32 6695295                    /usr/lib64/gconv/gconv-modules.cache
7fc76156c000-7fc76156d000 rw-p 00000000 00:00 0 
7fc76156d000-7fc76156e000 r--p 00021000 08:32 4466385                    /lib64/ld-2.17.so
7fc76156e000-7fc76156f000 rw-p 00022000 08:32 4466385                    /lib64/ld-2.17.so
7fc76156f000-7fc761570000 rw-p 00000000 00:00 0 
7fffe8eb2000-7fffe8ed4000 rw-p 00000000 00:00 0                          [stack]
7fffe8f80000-7fffe8f81000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
Aborted (core dumped)

gdb ./src/nano core 

Reading symbols from /usr/local/src/nano/src/nano...done.
[New LWP 21864]

warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
Core was generated by `./src/nano /etc/nanorc /home/vapier/.nanorc'.
Program terminated with signal 6, Aborted.
#0  0x00007fc760b526f5 in __GI_raise (sig=sig< at >entry=0x6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56      ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x00007fc760b526f5 in __GI_raise (sig=sig< at >entry=0x6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007fc760b53b67 in __GI_abort () at abort.c:90
#2  0x00007fc760b92a35 in __libc_message (do_abort=do_abort< at >entry=0x2, fmt=fmt< at >entry=0x7fc760c8e360 "*** Error in 
`%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:196
#3  0x00007fc760b9881d in malloc_printerr (action=0x3, str=0x7fc760c8e520 "free(): invalid next size (fast)", ptr=<optimized 
out>) at malloc.c:4902
#4  0x00007fc760b995f3 in _int_free (av=<optimized out>, p=0x260a270, have_lock=0x0) at malloc.c:3758
#5  0x0000000000426d12 in edit_draw (fileptr=0x241e560, converted=0x261ab50 "set speller \"aspell -x -c\"", line=0xf, 
start=0x0) at winio.c:2500
#6  0x0000000000427d39 in update_line (fileptr=0x241e560, index=0x0) at winio.c:2915
#7  0x0000000000428858 in edit_refresh () at winio.c:3274
#8  0x000000000040853a in display_buffer () at files.c:221
#9  0x00000000004085ad in switch_to_prevnext_buffer (next_buf=0x1) at files.c:247
#10 0x0000000000408616 in switch_to_next_buffer_void () at files.c:268
#11 0x0000000000415864 in do_input (meta_key=0x7fffe8ecfaff, func_key=0x7fffe8ecfafe, s_or_t=0x7fffe8ecfafd, 
ran_func=0x7fffe8ecfafc, finished=0x7fffe8ecfafb, allow_funcs=0x1) at nano.c:1658
#12 0x0000000000417183 in main (argc=0x3, argv=0x7fffe8ed01a8) at nano.c:2728
(gdb) 

this is my ~/.nanorc:
set const
set fill -2
set historylog
set morespace
set multibuffer
set noconvert
set nohelp
set nowrap
# set regexp
set smarthome
set smooth
set suspend
set tabsize 4
set whitespace "»·"
set speller "aspell -x -c"

# disable stupid justify logic
unbind ^J all
unbind M-J all
-mike
_______________________________________________
Nano-devel mailing list
Nano-devel< at >gnu.org
https://lists.gnu.org/mailman/listinfo/nano-devel

http://www.nano-editor.org/dist/test/nano-2.3.2pre1.tar.gz

Chris Allegretta — 2013-01-01T05:27:59

If you want to try the vim-style locking code, I just uploaded 2.3.2pre1 to
the above address, feedback always welcome.

Still catching up on the bug reports recently.  Happy New Year all.
_______________________________________________
Nano-devel mailing list
Nano-devel< at >gnu.org
https://lists.gnu.org/mailman/listinfo/nano-devel

[PATCH] Fix memory errors in parse_syntax

David Benjamin — 2012-11-27T19:22:02

Hi,

I dropped this into savannah a while ago, but I haven't heard back.
Not sure where nano development is actually happening these days as
SVN seems dead. I see some activity on this list, so here's a patch.

https://savannah.gnu.org/patch/?7665

David

Softwrap option $ or --softwrap

James Freer — 2012-11-18T20:09:15

I'd be grateful if one of you on the development could confirm how the
option is intended to/should work. No one in Help seemed to know.

I'd be grateful if someone could confirm if the --softwrap option
works as i expect like vim's 'linebreak'. --softwrap truncates but
chops a word up instead of like 'linebreak which was what i was hoping for.

What i want to do is use a console editor for editing text words (not
code) and didn't want to use vim with all it's complexity if i could
help it.

thanks
james

[PATCH 1/2] shell syntax: major updates

Mike Frysinger — 2012-08-26T03:19:11

Highlight more shell builtins and common commands.

Rewrite the variable highlighting to be more exact and handle cases where
string operations are used.

Signed-off-by: Mike Frysinger <vapier< at >gentoo.org>
---
 doc/syntax/sh.nanorc |   13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/doc/syntax/sh.nanorc b/doc/syntax/sh.nanorc
index f660105..a664ef6 100644
--- a/doc/syntax/sh.nanorc
+++ b/doc/syntax/sh.nanorc
< at >< at > -4,12 +4,17 < at >< at > syntax "sh" "\.sh$"
 magic "(POSIX|Bourne.*) shell script text"
 header "^#!.*/(ba|k|pdk)?sh[-0-9_]*"
 icolor brightgreen "^[0-9A-Z_]+\(\)"
-color green "\<(case|do|done|elif|else|esac|exit|fi|for|function|if|in|local|read|return|select|shift|then|time|until|while)\>"
-color green "(\{|\}|\(|\)|\;|\]|\[|`|\\|\$|<|>|!|=|&|\|)"
+color green "\<(break|case|continue|do|done|elif|else|esac|exit|fi|for|function|if|in|read|return|select|shift|then|time|until|while)\>"
+color green "\<(declare|eval|exec|export|let|local)\>"
+color green "[{}():;|`$<>!=&\\]" "(\]|\[)"
 color green "-[Ldefgruwx]\>"
 color green "-(eq|ne|gt|lt|ge|le|s|n|z)\>"
-color brightblue "\<(cat|cd|chmod|chown|cp|echo|env|export|grep|install|let|ln|make|mkdir|mv|rm|sed|set|tar|touch|umask|unset)\>"
-icolor brightred "\$\{?[0-9A-Z_!< at >#$*?-]+\}?"
+color brightblue "\<(awk|cat|cd|ch(grp|mod|own)|cp|echo|env|grep|install|ln|make|mkdir|mv|popd|printf|pushd|rm|rmdir|sed|set|tar|touch|umask|unset)\>"
+# Basic variable names (no braces)
+color brightred "\$[-0-9< at >*#?$!]" "\$[[:alpha:]_][[:alnum:]_]*"
+# More complicated variable names; handles braces
+# and replacements and arrays
+color brightred "\$\{[#!]?([-< at >*#?$!]|[0-9]+|[[:alpha:]_][[:alnum:]_]*)(\[([[:space:]]*[[:alnum:]_]+[[:space:]]*|< at >)\])?(([#%/]|:?[-=?+])[^}]*\}|\[|\})"
 color cyan "(^|[[:space:]])#.*$"
 color brightyellow ""(\\.|[^"])*"" "'(\\.|[^'])*'"
 color ,green "[[:space:]]+$"

[bug] segfault when pasting then cutting,when mark is on

Benno Schulenberg — 2012-07-22T16:42:08

Hi,

The editor segfaults when some text is marked, something is
pasted, then something cut, and then a Cursor-up is done.

How to reproduce:

Start nano with an empty buffer, then type
for example the following two lines:

first line
second line

Place the cursor in the first line and type ^K
to have a non-empty cut buffer.

Then type:  Alt-A  Cursor-right  ^U  ^K  Cursor-up

(The Cursor-right may be done several times, as long
as it stays on the same line.)

Result: Segmentation fault

Found on nano 2.2.5, bug still present in SVN (nano 2.3.1).

Regards,

Benno