On Tue, May 30, 2000 at 02:39:38PM +1000, G.Embery wrote:
> > you can always make your own (setenv TERMINFO, etc.)
> >
>
> Beauty!
> I've (temporarily) set up my own terminfo from your src file and
> setenv TERMINFO and now the function keys are being recognized.
> Now to make it more permanent
On Mon, May 29, 2000 at 09:19:49PM -0400, Thomas Dickey wrote:
> On Tue, May 30, 2000 at 11:05:38AM +1000, G.Embery wrote:
> >
> > I'm on SGI IRIX 6.5 , X is possibly Release 6.3 (from the X man page)
> >
> > I run mutt in color_xterm
> > % color_xterm -version==>
> > UGCS color
On Tue, May 30, 2000 at 11:05:38AM +1000, G.Embery wrote:
>
> I'm on SGI IRIX 6.5 , X is possibly Release 6.3 (from the X man page)
>
> I run mutt in color_xterm
> % color_xterm -version==>
> UGCS color xterm ver. 6.1 beta 3
color_xterm has its own terminfo description in
On Mon, May 29, 2000 at 08:01:25AM -0400, Thomas Dickey wrote:
> On Mon, May 29, 2000 at 01:38:40PM +0200, clemensF wrote:
>
> > could this have to do more with X than slang/curses? i've never had any
> > problems using either, and i don't run X. i'd be interested in the
> > environment in gen
On Mon, May 29, 2000 at 03:30:53PM +0200, clemensF wrote:
> > Thomas Dickey:
>
> > perhaps it's the terminal description (XFree86 xterm by default sends the
> > vt100-style F1 code rather than the bogus-vt220 F1 code).
> >
> > infocmp:
> > kf1: '\E[11~', '\EOP'.
>
> excuse me, this is a non
On Mon, May 29, 2000 at 01:38:40PM +0200, clemensF wrote:
> could this have to do more with X than slang/curses? i've never had any
> problems using either, and i don't run X. i'd be interested in the
> environment in general. as i said, no probs with either slang or curses on
> freebsd 2.8.8
> G.Embery:
> I haven't been able to get function keys to work at all with
> s-lang lib but they are quite okay with [n]curses lib.
>
> Here is what i get for the 2 cases:
> s-lang:
> color ok; function-keys not-ok; "grey" keys got-working;
> ncurses:
> color none; fun
On Fri, May 26, 2000 at 02:24:34PM -0400, Hardy Merrill wrote:
> Since I upgraded to mutt 1.2, I haven't been able to get my
> f1 help macros to work. These used to work for me:
>
> # Show documentation when pressing F1
> macro generic "!less /usr/doc/mutt-1.0i/manual.txt\n" "Show Mutt document
On Fri, May 26, 2000 at 03:38:43PM -0400, Hardy Merrill wrote:
> In /etc/Muttrc, I only have the "mutt-1.0i" directory - I don't
> have mutt-1.2. That was something I was wondering about - why
> didn't the install give me a /usr/doc/mutt-1.2 directory?
If you installed from tarball, it might be
On Fri, May 26, 2000 at 15:38:43 -0400, Hardy Merrill wrote:
> In /etc/Muttrc, I only have the "mutt-1.0i" directory - I don't
> have mutt-1.2. That was something I was wondering about - why
> didn't the install give me a /usr/doc/mutt-1.2 directory?
If you didn't told the configure script to do
Telsa Gwynne [[EMAIL PROTECTED]] wrote:
> On Fri, May 26, 2000 at 02:24:34PM -0400 or thereabouts, Hardy Merrill wrote:
> > Since I upgraded to mutt 1.2, I haven't been able to get my
>
> > # Show documentation when pressing F1
> > macro generic "!less /usr/doc/mutt
On Fri, May 26, 2000 at 02:24:34PM -0400 or thereabouts, Hardy Merrill wrote:
> Since I upgraded to mutt 1.2, I haven't been able to get my
> # Show documentation when pressing F1
> macro generic "!less /usr/doc/mutt-1.0i/manual.txt\n"
Thus spake Hardy Merrill ([EMAIL PROTECTED]):
> Since I upgraded to mutt 1.2, I haven't been able to get my
> f1 help macros to work. These used to work for me:
>
> # Show documentation when pressing F1
> macro generic "!less /usr/doc/mutt-1.0i/manual.txt\n" "Show Mutt documentation"
> macro i
Since I upgraded to mutt 1.2, I haven't been able to get my
f1 help macros to work. These used to work for me:
# Show documentation when pressing F1
macro generic "!less /usr/doc/mutt-1.0i/manual.txt\n" "Show Mutt documentation"
macro index"!less /usr/doc/mutt-1.0i/manual.txt\n" "Show Mutt
14 matches
Mail list logo
