gmane.editors.nano.devel

Re: Spanish translation for current

Benno Schulenberg — 2013-05-04T11:36:02

Hello Jorge,

On Sat, May 4, 2013, at 12:52, Jorge González wrote:

Nano is translated via the Translation Project: http://translationproject.org/team/es.html
You appear to be a member there already, so please ask the team leader
for a reassignment of nano to you, and then you can submit the file there.
Reassignment won't  a problem, seeing that the last translator hasn't made
an update for more than six years.

Regards,

Benno

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.

Re: FW: Porting nano

Chris Allegretta — 2013-04-16T23:03:27

Anyone interested in a project to decouple nano from [n]curses?

This is not something I'm interested in right now given the number of
outstanding bugs and feature requests which are much smaller in scale
than a UI decoupling.  I'm not sure what else one could use for UIs on
a Unix workalike besides straight termcap, and my understanding is
that's pretty hard to use, which is why curses and associated programs
exist to begin with .

regarding libc, if there are GNU specifics nano is relying on that are
not in your Unix-like OS' libc, we can make autoconf check for them.


On Tue, Apr 16, 2013 at 4:10 AM, Pratik Mankawde(MT2012101)
<Pratik.Mankawde< at >iiitb.org> wrote:

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

Benno Schulenberg — 2013-04-14T13:40:05

On Sat, Apr 13, 2013, at 4:57, Chris Allegretta wrote:

Yes, it is fixed now, with r4575.  Thanks!

Benno

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

Chris Allegretta — 2013-04-13T02:57:49

Er, oh, sorry I totally misinderstood.  I think the patch that Michael
submitted was good, it just fixes a separate issue.  Can you see if
this behavior is also now fixed with r4574?

On Fri, Apr 12, 2013 at 5:42 AM, Benno Schulenberg
<bensberg< at >justemail.net> wrote:

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

Benno Schulenberg — 2013-04-12T09:42:42

On Fri, Apr 12, 2013, at 8:15, Chris Allegretta wrote:

Yep.  Even tried it on a different system, a recent Linux Mint

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

Chris Allegretta — 2013-04-12T06:15:14

Um, you're running svn version r4573?  I no longer see this behavior
following the steps you describe.

On Mon, Apr 8, 2013 at 8:18 AM, Benno Schulenberg
<bensberg< at >justemail.net> wrote:

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

Chris Allegretta — 2013-04-08T03:26:22

Hi Benno, thanks for the report!

I received a patch off-list for this from Michael Berg; let me know if
current SVN does not DTRT for you.  If it does we can add it to the
mountain of fixes which should go back to 2.2.

On Sat, Mar 30, 2013 at 4:15 PM, Benno Schulenberg
<bensberg< at >justemail.net> wrote:

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

Benno Schulenberg — 2013-04-08T12:18:40

On Mon, Apr 8, 2013, at 5:26, Chris Allegretta wrote:

It does not do the right thing -- nano still says the file was modified
since opening it.  Sorry.

Regards,

Benno

Re: ANNOUNCEMENT: Exciting news about our acquisition by VIM [PATCH]

Joshua Rogers — 2013-04-01T11:30:43

10/10.
That is all.
*Joshua Rogers* - Retro Game Collector && IT Security Specialist
gpg pubkey <http://www.internot.info/docs/gpg_pubkey.asc.gpg>
On 01/04/13 19:20, Chris Allegretta wrote:

_______________________________________________
Nano-devel mailing list
Nano-devel< at >gnu.org
https://lists.gnu.org/mailman/listinfo/nano-devel

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 fr

[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

Re: GNU nano 2.3.2

Kamil Dudka — 2013-03-26T15:06:56

Yep, the above signature works.  Thanks!

Kamil

Re: GNU nano 2.3.2

Chris Allegretta — 2013-03-26T14:38:57

Wrong signature, and thank you for verifying.  When I encountered the
automake bug looks like I didnt regenerate the ascii signature.  It
should be:

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAlFRsnwACgkQvLNW35EAn6f9wwCdHmY/WKtwVoLR49vPgr/D8mwN
ULcAn0nHgbd3m7B5XKaWrF5hJkypsss/
=ZC4W
-----END PGP SIGNATURE-----

and should be updated on the website.

On Tue, Mar 26, 2013 at 9:54 AM, Kamil Dudka <kdudka< at >redhat.com> wrote:

Re: GNU nano 2.3.2

Kamil Dudka — 2013-03-26T13:54:01

I have downloaded <http://www.nano-editor.org/dist/v2.3/nano-2.3.2.tar.gz>
and attempted to verify the signature:

$ gpg --verify nano-2.3.2.tar.gz.asc
gpg: Signature made Fri 22 Mar 2013 03:10:54 PM CET using DSA key ID 91009FA7
gpg: BAD signature from "Chris Allegretta <chrisa< at >asty.org>"

Do I have a wrong tarball or a wrong signature?

$ sha1sum nano-2.3.2.tar.gz
5d4bed4f15088fc3cba0650a89bd343b061f456d  nano-2.3.2.tar.gz

Kamil

Re: [Info-nano] GNU nano 2.3.2

Eitan Adler — 2013-03-23T03:46:40

Thank you for this release.  I have updated the FreeBSD development
version of nano.

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.

Re: msgid typos in nano 2.3.2pre4

Benno Schulenberg — 2013-03-19T20:45:33

On Tue, Mar 19, 2013, at 0:24, Jean-Philippe Guérard wrote:

Oh yes, a stutter in hostname.  And also it says twice
"lock file", and twice "lockfile".   You may want to choose
one of those forms (after the release of 2.3.2).

Please don't forget to pull in the files from
https://translationproject.org/latest/nano/
just before release.

Regards,

Benno

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.

Re: 2.3.2pre3

Chris Allegretta — 2013-03-17T22:13:52

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

On Sun, Mar 17, 2013 at 6:08 PM, Chris Allegretta <chrisa< at >asty.org> wrote:

Re: 2.3.2pre3

Chris Allegretta — 2013-03-17T22:08:47

Okay I am rolling back the r4547 commit and make one last pre-release,
so we can get something out for people to try out the locking code.
Ill put that commit back in post-release, maybe after we get git
figured out.

On Wed, Jan 23, 2013 at 11:35 AM, Jordi Mallach <jordi< at >gnu.org> wrote: