David Cougle | 1 Jul 2003 01:18
Picon
Favicon

no color in nano

I build nano 1.2.1 from the spec file, which has enable -all, but i don't see any color?(but i do with vim and stuff)

MSN 8 helps ELIMINATE E-MAIL VIRUSES. Get 2 months FREE*.
_______________________________________________
Nano-devel mailing list
Nano-devel <at> gnu.org
http://mail.gnu.org/mailman/listinfo/nano-devel
Jordi Mallach | 2 Jul 2003 13:28
Favicon
Gravatar

Re: no color in nano

On Mon, Jun 30, 2003 at 06:18:26PM -0500, David Cougle wrote:
>    I build nano 1.2.1 from the spec file, which has enable -all, but i don't
>    see any color?(but i do with vim and stuff)

Have you created a ~/.nanorc with your colour configuration?
Find an example in the tarball, nanorc.sample.

Jordi
--

-- 
Jordi Mallach Pérez  --  Debian developer     http://www.debian.org/
jordi <at> sindominio.net     jordi <at> debian.org     http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/~jordi/
_______________________________________________
Nano-devel mailing list
Nano-devel <at> gnu.org
http://mail.gnu.org/mailman/listinfo/nano-devel
Jordi Mallach | 2 Jul 2003 13:29
Picon

FAQ update

Can someone with 2 spare minutes (I'm not so lucky right now..) add a
new item to the FAQ regarding the colour configuration? I think we've
had like 15 questions about this since 1.2.0.

Jordi
--

-- 
Jordi Mallach Pérez  --  Debian developer     http://www.debian.org/
jordi <at> sindominio.net     jordi <at> debian.org     http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/~jordi/
_______________________________________________
Nano-devel mailing list
Nano-devel <at> gnu.org
http://mail.gnu.org/mailman/listinfo/nano-devel
Joseph Birthisel | 2 Jul 2003 16:11

Re: FAQ update

> Can someone with 2 spare minutes (I'm not so lucky right now..) add a
> new item to the FAQ regarding the colour configuration? I think we've
> had like 15 questions about this since 1.2.0.
>
> Jordi

I would really appreciate that. I searched the website over and over and
then started off-list mailing people from the list. Also, if the bugs page
could be beefed up a bit, and the news and cvs pages updated. :)
David Lawrence Ramsey | 2 Jul 2003 16:25

Re: FAQ update

>Can someone with 2 spare minutes (I'm not so lucky right now..) add a
>new item to the FAQ regarding the colour configuration? I think we've
>had like 15 questions about this since 1.2.0.

I just did.

_____________________________________________________________
Sluggy.Net: The Sluggy Freelance Community!
David Lawrence Ramsey | 2 Jul 2003 20:17

more on Home/End not working at statusbar w/ALT_KEYPAD on xterm

The old problem with the Home and End keys' not being recognized when
pressing them at the statusbar prompt in ALT_KEYPAD mode on an xterm has
cropped up on my box again.  However, this time I've figured out how to
fix it.  Apparently, the keystrokes for shifted Home and shifted End
(what the xterm terminfo entry calls them) are generated when pressing
Home and End in this case, and nano doesn't currently handle those.  The
following patch adds support for them.

(Btw, the xterm terminfo entry on my box is the one included with
ncurses 5.3.  Is anyone else with ncurses 5.3 having this problem?)

http://pooka_regent.tripod.com/patches/nano/nanohomeend-patch.txt

_____________________________________________________________
Sluggy.Net: The Sluggy Freelance Community!
Jordi Mallach | 2 Jul 2003 20:45
Picon

Re: more on Home/End not working at statusbar w/ALT_KEYPAD on xterm

On Wed, Jul 02, 2003 at 11:17:37AM -0700, David Lawrence Ramsey wrote:
> The old problem with the Home and End keys' not being recognized when
> pressing them at the statusbar prompt in ALT_KEYPAD mode on an xterm has
> cropped up on my box again.  However, this time I've figured out how to
> fix it.  Apparently, the keystrokes for shifted Home and shifted End
> (what the xterm terminfo entry calls them) are generated when pressing
> Home and End in this case, and nano doesn't currently handle those.  The
> following patch adds support for them.

It works for me, using the Debian package:

^W, scribble something and home end works ok.

Xterm, ncurses version: 5.3.20030510-2

Applying your patch makes it not work, unfortunately...

Jordi
--

-- 
Jordi Mallach Pérez  --  Debian developer     http://www.debian.org/
jordi <at> sindominio.net     jordi <at> debian.org     http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/~jordi/
_______________________________________________
Nano-devel mailing list
Nano-devel <at> gnu.org
http://mail.gnu.org/mailman/listinfo/nano-devel
David Lawrence Ramsey | 2 Jul 2003 23:57

Re: more on Home/End not working at statusbarw/ALT_KEYPAD on xterm

Jordi Mallach:
>It works for me, using the Debian package:
>
>^W, scribble something and home end works ok.
>
>Xterm, ncurses version: 5.3.20030510-2
>
>Applying your patch makes it not work, unfortunately...

Looking at the documentation added by the -2 diff pointed me in the
right direction:

http://dickey.his.com/xterm/xterm.faq.html#xterm_pc_style

The problem here appears to be that nano should be in cursor application
mode (via keypad(window, TRUE)) while the statusbar prompt is being
used, but isn't when in ALT_KEYPAD mode, and hence generates the wrong
key sequences for Home and End.

With current CVS, ncurses 5.3, and nano with -K, if I manually check
"Enable application cursor keys", it fixes the problem in bottomwin but
breaks it in other places.

Using these results, I've recreated the patch.  Now it forces cursor
application mode on in the bottomwin window in nanogetstr() and turns it
off after reading the input, which appears to fix the problem, at least
in my preliminary testing.

However, I don't know whether this is due to a bug in ncurses 5.3 that's
been fixed in 5.3.20030510-2 or not.  I've read the NEWS file for
ncurses-20030510, and the only explicit mention of a keypad() bug is
between ncurses 5.2 and 5.3.

In any case, does the new patch still break nano for you?  All other
input routines besides the edit window input routines force cursor
application mode on for at least some windows (the file browser: edit;
the help browser: edit and bottomwin), so I'm wondering whether what the
patch adds is correct behavior or not.

_____________________________________________________________
Sluggy.Net: The Sluggy Freelance Community!
Chris Allegretta | 3 Jul 2003 04:52

Re: more on Home/End not working at statusbarw/ALT_KEYPAD on xterm

On Wed, Jul 02, 2003 at 02:57:51PM -0700, David Lawrence Ramsey wrote:
> Jordi Mallach:
> >It works for me, using the Debian package:
> >
> >^W, scribble something and home end works ok.
> >
> >Xterm, ncurses version: 5.3.20030510-2
> >
> >Applying your patch makes it not work, unfortunately...
> 
> Looking at the documentation added by the -2 diff pointed me in the
> right direction:
> 
> http://dickey.his.com/xterm/xterm.faq.html#xterm_pc_style
> 
> The problem here appears to be that nano should be in cursor application
> mode (via keypad(window, TRUE)) while the statusbar prompt is being
> used, but isn't when in ALT_KEYPAD mode, and hence generates the wrong
> key sequences for Home and End.
> 
> With current CVS, ncurses 5.3, and nano with -K, if I manually check
> "Enable application cursor keys", it fixes the problem in bottomwin but
> breaks it in other places.
> 
> Using these results, I've recreated the patch.  Now it forces cursor
> application mode on in the bottomwin window in nanogetstr() and turns it
> off after reading the input, which appears to fix the problem, at least
> in my preliminary testing.
> 
> However, I don't know whether this is due to a bug in ncurses 5.3 that's
> been fixed in 5.3.20030510-2 or not.  I've read the NEWS file for
> ncurses-20030510, and the only explicit mention of a keypad() bug is
> between ncurses 5.2 and 5.3.
> 
> In any case, does the new patch still break nano for you?  All other
> input routines besides the edit window input routines force cursor
> application mode on for at least some windows (the file browser: edit;
> the help browser: edit and bottomwin), so I'm wondering whether what the
> patch adds is correct behavior or not.

I wonder if this would not allow FreeBSD users to use their backspace 
keys properly.  Currently that's one large reason to use -K, that 
keypad() seems to change the backspace key into delete.  I don't have a 
FreeBSD system to test this on anymore though...

Chris A
--

-- 
Chris Allegretta	http://www.asty.org

"Share and Enjoy" - Douglas Adams, 1952 - 2001
Jordi Mallach | 3 Jul 2003 14:00
Picon

Re: more on Home/End not working at statusbarw/ALT_KEYPAD on xterm

On Wed, Jul 02, 2003 at 02:57:51PM -0700, David Lawrence Ramsey wrote:
> In any case, does the new patch still break nano for you?  All other
> input routines besides the edit window input routines force cursor
> application mode on for at least some windows (the file browser: edit;
> the help browser: edit and bottomwin), so I'm wondering whether what the
> patch adds is correct behavior or not.

With the new patch, home and end works, yes.

Jordi
--

-- 
Jordi Mallach Pérez  --  Debian developer     http://www.debian.org/
jordi <at> sindominio.net     jordi <at> debian.org     http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/~jordi/
_______________________________________________
Nano-devel mailing list
Nano-devel <at> gnu.org
http://mail.gnu.org/mailman/listinfo/nano-devel

Gmane