Rafael Filipe Lúcio Romão | 10 Sep 13:27 2015


I want nano source code, where I can get?

Rafael Romão

Help-nano mailing list
Help-nano <at> gnu.org
Fergus Daly | 31 Mar 13:57 2015

Compiling nano from source, for Cygwin

Nano v.2.4.0 comes with Cygwin.
Just install Cygwin (making the appropriate selection of optional packages, of which nano is just one of
many) and Hey Presto, it works.
If you want something outside the options list, it can usually (often) be rendered available by
downloading the source e.g. from gnu and compiling (./configure ... make ... make install) from within
Recently a patch to 2.4.0 has been made available on nano-devel which I would like to try on a Cygwin
platform. I'll need to patch nano from source. So I downloaded the source.
./configure works fine.
make proceeds quite energetically for a while and then fails as follows:

gcc -DHAVE_CONFIG_H -I. -I..  -DLOCALEDIR=\"/usr/local/share/locale\"
-DSYSCONFDIR=\"/usr/local/etc\" -D_XOPEN_SOURCE=600   -g -O2 -Wall -MT text.o -MD -MP -MF
.deps/text.Tpo -c -o text.o text.c
text.c: In function 'do_alt_speller':
text.c:2667:5: error: unknown type name '__time_t'
     __time_t timestamp;
Makefile:411: recipe for target 'text.o' failed
make[2]: *** [text.o] Error 1
make[2]: Leaving directory '/home/user/nano-2.4.0/src'
Makefile:395: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/user/nano-2.4.0'
Makefile:333: recipe for target 'all' failed
make: *** [all] Error 2

It is possible that I have not installed enough of Cygwin (the entire provision is huge) but generally
speaking I have found compilation to work all right. (I install gcc-core and any dependencies but stop
there. In the past I have had to be explicit about ... bison, flex ... and some others.) 
Can anybody offer advice on what package in Cygwin Devel (or other) I might be missing that is preventing
compilation of nano from source?
Or is there a tweak to the script Makefile that I need to attend to?
Thank you.
mike _ | 25 Mar 15:37 2015

nano-2.4.0-1.x86_64.rpm glibc version

http://www.nano-editor.org/download.php states that
nano-2.4.0-1.x86_64.rpm is "Binary RPM for x86_64 platform
(glibc2.4+)."  but it won't install on SLED 11 SP3 which has glibc
2.11. The package appears to actually require 2.14.

nano-2.4.0-1.src.rpm seems to build OK on SLED 11 SP3 though.

Fergus Daly | 24 Mar 08:51 2015

Altering DOS/Mac/Unix terminated text files

Hello -
Just started using nano 2.4.0. As with many previous versions
	nano -help
	-N    --noconvert    Don't convert files from DOS/Mac format
carrying the implication that without the switch -N, files will be converted to Unix format.
But this is not what happens.
	nano (no argument)
	nano -N
are identical: they don't convert. 
If you go back far enough the following beautiful behaviour is what happened with v.1.3.4:
	nano (no argument) = if not Unix, convert convert to Unix
	nano -D = if not DOS, convert to DOS
	nano -M = if not Mac, convert to Mac
	nano -N = do not change format
PLEASE could nano v.current be made to mimic the marvellous behaviour of 1.3.4?
Or, if not, how can I get
	nano {? switch} = if not Unix, convert to Unix 
Thank you.
Josu Lazkano | 20 Feb 21:27 2015

Compile for PowerPC


This is my first post in this list.

I love nano and I want to use it in my satellite receiver, it is based
in PowerPC. Here is the toolchain:

I have no idea how to compile it.

Anyone could help?

Thanks for your help.



Josu Lazkano
Hart Larry | 24 Jan 17:45 2015

Can I Cut Before Cursor?

Well, following up on an earlier message before I subscribed to this list. 
Essentially what I want to do is edit the contents of a pine addressbook and cut 
out everything before the word "whitelist" Sure it would be nice if there were 
an easy way in Nano to do this, but manually looking over 730 lines would be 
time consuming.
Now in answering a question about special symbols, NANO will not let me search 
for or replace a charactor called "null" at least thats what my screen-reader 
says it is. So even pasting a null in, NANO ignores it.
Another type of thing I cannot do in NANO, are searching/replace to nuke blank 
lines. You must work on a file like this:
sed '/^[ \t*]*$/d' in_file.txt > out_file.txt
Word-Perfect, at least when I was in DOS would let me work on soft-and-hard 
returns, but I am going to need `alot of asistance getting a Linux version 
And lastly, maybe would be nice having a current number of lines in a file, 
always near an end of screen, as they are when you first enter. Also, the nain 
NANO home page would be more helpful with links to the mailing lists, also in 
the toolbar you have many links on a single line, not so easy listing with 
speech. Thanks so much in advance for suggestions.
Chris Allegretta | 22 Jan 19:34 2015

Re: Can I cut before Cursor?

Hello Hart,

At the moment if you wanted to cut-to-from beginning of line to cursor
position, there's unfortunately no built-in way to do so.  Today the
fastest way to do this would probably be to set the marker for where
you are: (^^ or ^6), then moving to the beginning of the line (^A) and
then cutting (^K).

Other users are welcome to chime in here if they'd like to see an
official option to force ^K to do this.

I hope this helps, and thank you for using nano!

On 1/21/15, Hart Larry <chime <at> hubert-humphrey.com> wrote:
> I really like nano-and-use the control+k to delete to end of line, but is
> their
> a way to delete from where I am to beginning? I know I can nuke an entire
> line.
> By the way, I really wish I could see-and-edit special symbols or turn on
> reveal
> codes as Word Perfect has. Thanks so much in advance
> Hart
Ronald Fischer | 10 Nov 17:24 2014

nano for Windows doesn't find .nanorc

Using nano 2.2.6 Windows 7. 

Compiled options: --disable-mouse --enable-color --enable-extra
uffer --enable-nanorc

I have the following environment variable setting:

  set SYSCONFDIR=c:/conf

and c:/conf contains my .nanorc. 

Nano does however not honor the settings in .nanorc. Is there something
special I need to observe when defining the SYSCONFDIR?

Nicholas Boel | 13 Aug 00:25 2014

Free flowing onscreen text

Hey all,

I've been trying to get the right combination of command line options in 
order to create free flowing text (with no hardwraps) that fits the 
width of my screen (currently the VM is 1024x768 which gives me about 
128 columns wide), and softwraps to the next line without breaking up 
the last word of the line if it ends on the 128th column in the middle 
of the word.

Basically, I'm trying to use the -w option in conjunction with the -$ 
option, so that there is no hard wraps, but also doesn't keep everything 
on one never ending line.

Except at the end of the line, if a word hits the last column, the 
entire word doesn't wrap on to the next line, only the letters after the 
last column is hit.. so the word gets split up.

Is there a better way to go about doing this? At the moment I'm using 
Thunderbird to compose this message, and it does exactly what I'm asking 
for here. I can resize the window and all the text flows to the size of 
the window.

Is there a way for nano to handle this? I'm not trying to resize the 
window in nano, though, I'm just trying to flow the text to the size of 
my console window and keep the words readable and in view.



Mario Blättermann | 29 Jul 20:50 2014

Re: man-html translated in RO

Hi Mihai,

Am 29.07.2014 16:14, schrieb Mihai Cristescu:
> I would like to start also help2man after nano, but it seems the
> Romanian team is inactive. Last message on the list is from 2012, and
> Laurentiu's last message is that he has no longer time to make
> translations and ask for volunteers to continue the project.I sent
> another message today to the whole list, and wait for sign of life
> there. So, if there is nobody there who can revise the material, does
> it make sense to continue the translation?
> Best regards,
> Mihai
If really nobody responses within a reasonable time frame, or nobody of the
responders is willing to continue there as the new coordinator, then it would
become your job! First, write to the list, and if you don't get an answer next
two weeks, then the team and its list is to be considered as dead. Write then to
the global TP coordinators <coordinator <at> translationproject.org> (Benno
Schulenberg is one of them) to let the coordinatorship change.

Maybe you could ask some other Romanian translation teams for a review:




Archlinux (Pacman only):

Romanian Translation Team <debian-l10n-romanian <at> lists.debian.org>, Andrei
Popescu <andreimpopescu <at> gmail.com>, Ionel Mugurel Ciobîcă <I.M.Ciobica <at> tue.nl>

Best Regards,

Help-nano mailing list
Help-nano <at> gnu.org
Mario Blättermann | 27 Jul 22:05 2014

Re: man-html translated in RO

Hi Mihai,

Am 27.07.2014 13:43, schrieb Mihai Cristescu:
> Dear Mario,
> Thanks for your reply and very good material you sent me.
> Well, I was already finished translating the man files, after I have created a
> special filter based on regular expresions in memoq for importing groff files. 
> I was almost finished with the reviewing for errors. I also have generated the
> html files with groff-utf8 command.
> But, now after receiving your scripts I made some tests.
> Actually they work like a charm. I wish I had them before, they create much
> better quality of pot file (po4a seems a good tool for the future).
> So, I have generated the ro.po file (combined from all text sources) and
> imported successfully in my CAT system, that means I can use the translation
> memory already done for this project.
> I have installed also Lokalize, Gtranslator and Poedit to have an idea and they
> all are good but I will keep working in memoq because I have more experience in
> it for complex tasks.
> Maybe for the future I'll start using Lokalize seems to have more features inside.
> Question: After I finish translating the file, I send the material to this list
> or to the http://translationproject.org for revision?
No, as Benno already wrote, you should contact the Romanian TP team for all
those issues.

> After I finish nano I can have a look also to help2man, but that is already
> generated pot file isn't it? ... no po4a involved.
No, help2man is very different: It generates man pages from the --help and
--version output of a command, in its own case also in native languages. I
mentioned it rather to get a kind of dictionary for future doc translations,
because the basic terms e.g. for headers etc. are included in the help2man
translation. Besides that, if you or someone else translates it into Romanian,
also a Romanian man page of help2man will be generated and released. And if some
other project maintainers decide to use help2man to create localized man pages
for their man pages, then also Romanian ones will be created, as long as the
--help and --version strings of that project are already translated. In the
nearest future I will convince the coreutils developers to do so -- especially
to get rid of the lots of external translations which are not shipped with the
project files itself, which are not in sync with the latest version, and which
can cause package conflicts.

> And is with this robot thing, for newr versions of the sources, how is that working?
As said, contact the Romanian TP team first. In any case we work with pot
templates and the resulting po files, no need for translators to import anything
from source files or create own scripts.

I've officially written to the nano-devel mailing list to get the po4a toolchain
included and get created the new domain for the docs at TP.

Best Regards,

> 2014-07-26 23:44 GMT+03:00 Mario Blättermann <mario.blaettermann <at> gmail.com
> <mailto:mario.blaettermann <at> gmail.com>>:
>     Hi Mihai and Benno,
>     Am 25.07.2014 11:47, schrieb Benno Schulenberg:
>     >
>     > Hi Mihai,
>     >
>     > (For Mario: Mihai made Romanian translations of the nano docs, but
>     > of the HTML pages.  I'm wondering, how are you getting along with
>     > applying po4a to nano?)
>     >
>     Nice to know! New doc translators are always welcome.
>     > On Fri, Jul 25, 2014, at 11:25, Mihai Cristescu wrote (quoted in full):
>     >> Thanks for reply and sorry that the files can't be used in this form.
>     >> I know that the html page are generated from the man groff format, but the
>     >> thing is I am using a CAT system (memoQ) which uses a translation memory
>     >> and speed up the translation process significantly.
>     >
>     > Ah, very good.  Then, when the nano docs become available in
>     > POT files, this translation memory will save you a lot of work.
>     >
>     Off-line translation tools like Lokalize, Poedit or Gtranslator also have a
>     translation memory. But as long as your special tools can handle normal po files
>     (which I strongly assume) then it shouldn't be a problem to keep your software
>     which your are familiar with.
>     >> The problem is that I can't import the groff files into memoQ.
>     >>
>     >> I have tried several approaches to convert the man groff files to: rtf ,
>     >> ps, html formats which can be imported in memoQ, omegat , Trados SDL etc,
>     >> but the issue is that there is no way to convert the translated files to
>     >> man groff back. It seems that the only productive way to translate the man
>     >> pages is to translate the files directly, but this is time consuming since
>     >> you are not using a translation memory and term base.
>     >>
>     >> Regarding po4a :
>     >> I have installed yesterday this package on my arch system and followed the
>     >> documentation. I succeeded converting the man pages to pot files, import
>     >> them in memoQ, translated, but I was not able to convert back to man page
>     >> (I had some strange errors on po4a-translate command) and I had to give up.
>     >> Maybe I didn't quite understand how the po4a system works.
>     >
>     > Mario has some experience with po4a.  Maybe you can work together
>     > on solving the issues?
>     >
>     First, forget about the too difficult process described in the po4a docs, with
>     the configuration file which allows to accept non-UTF8 files, add extended
>     translator acknowledgements and some other things which we don't really need.
>     Just generate the pot file and localized docs with the attached scripts.
>     Put both scripts in the doc directory. With create-docs-pot.sh you generate then
>     a merged pot template for all groff and texinfo sources.
>     Then use the pot file to create your po file as usual, put the file ro.po (note
>     the file name, no other naming scheme will be accepted) into the doc directory
>     and launch translate-docs.sh. The translated groff files will be created in
>     subdirectories, named according to the locale. The texinfo file gets a suffix
>     (ro in your case, because there's currently no default way to install localized
>     texinfo files on a system).
>     Note, per default po4a needs at least 80% of the po strings translated for each
>     source file, otherwise the creation of that file will be skipped. For testing
>     purposes you can screw down ${threshold}, currently it is set to zero. But in my
>     mind, users won't benefit of translations lower than 80%, who wants to read a
>     documentation with more holes than real info in his/her native language...?
>     >> Nevertheless I shall contact Laurentiu to have a chat with him about the
>     >> process.
>     >>
>     Would be nice in any case to complete (or at least almost complete) the UI
>     translation first. Besides that, I don't see any other examples of Romanian man
>     pages, so it would be a good idea to translate the 49 messages from help2man [1]
>     first and let the terms confirm by a Romanian reviewer. Would be a good base for
>     future man page translations.
>     Moreover, there are already French plain text translations of the manpages. I
>     will try to import those into po files, once someone with Autotools skills has
>     setup the installation chain and the TP domain has been initialized.
>     [1] http://translationproject.org/domain/help2man.html
>     Best Regards,
>     Mario
> _______________________________________________
> Help-nano mailing list
> Help-nano <at> gnu.org
> https://lists.gnu.org/mailman/listinfo/help-nano