less, misbehaving

less, misbehaving

[Charles Wilson]

I'm having some wierd problems with less, and I don't know if it's my
environment settings, or my ncurses library, or what. I'm using less
v332 from andy's local.tar.

Less operates as expected, until I try to view a file with less than a
full screen of data. If I execute 'less shortfile', the file is
displayed in the terminal window, followed by the message: '[1]+
Stopped    less shortfile'

From that point on, all (?) interactive console mode programs misbehave.
When invoking less on a file with _more_ than a full screen of data,
e.g. 'less longfile', the first screen worth of data is displayed
followed by '[2]+ Stopped    less longfile'. (This identical command
worked fine _before_ my 'mistake' with shortfile)  Ditto with vi, or
hexedit. I can always bring the executable back to the foreground, and
things seem to work okay after that, but this is annoying.

Does anybody know what's going on? My cygwin variable is 'tty notitle
ntea binmode'

--Chuck Wilson


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: less, misbehaving

[Charles Wilson]

This problem is the only thing delaying a full rollout of gnu-win at my
workplace. Can anybody help?

Charles Wilson wrote:

> I'm having some wierd problems with less, and I don't know if it's my
> environment settings, or my ncurses library, or what. I'm using less
> v332 from andy's local.tar.
>
> Less operates as expected, until I try to view a file with less than a
> full screen of data. If I execute 'less shortfile', the file is
> displayed in the terminal window, followed by the message: '[1]+
> Stopped    less shortfile'
>
> >From that point on, all (?) interactive console mode programs misbehave.
> When invoking less on a file with _more_ than a full screen of data,
> e.g. 'less longfile', the first screen worth of data is displayed
> followed by '[2]+ Stopped    less longfile'. (This identical command
> worked fine _before_ my 'mistake' with shortfile)  Ditto with vi, or
> hexedit. I can always bring the executable back to the foreground, and
> things seem to work okay after that, but this is annoying.
>
> Does anybody know what's going on? My cygwin variable is 'tty notitle
> ntea binmode'
>
> --Chuck Wilson

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

RE: less, misbehaving - BASH 2.02

[Jonathan Storey]

I have come across this problem on my WinNT(SP3) box using
cygwinb19(.4).dll (669150bytes) and BASH.EXE 2.0.2(1) when
using telnet utilising Sergey's inetd remote utilities.

I have since got round the problem by reverting to BASH.EXE 2.01(1).EXE

Whats happening here is that the process is requesting input from
the terminal i.e END: (less's case) and the shell thinks that the
process is in background. Under UNIX the message would be
Stopped: (tty input) or similar. Therefore I would conclude that
the new version of BASH.EXE is incorrectly flagging processes
as being in background albeit intermittently, although using 
less(1) to output a file that is less than a screen full seems to
cause the problem to manifest itself consistently...

If you're not already Go Back to BASH.EXE 2.0.1(2).EXE 
and this should sort out your problem....


> 
> I'm having some wierd problems with less, and I don't know if it's my
> environment settings, or my ncurses library, or what. I'm using less
> v332 from andy's local.tar.
> 
> Less operates as expected, until I try to view a file with less than a
> full screen of data. If I execute 'less shortfile', the file is
> displayed in the terminal window, followed by the message: '[1]+
> Stopped    less shortfile'
> 
> >From that point on, all (?) interactive console mode programs misbehave.
> When invoking less on a file with _more_ than a full screen of data,
> e.g. 'less longfile', the first screen worth of data is displayed
> followed by '[2]+ Stopped    less longfile'. (This identical command
> worked fine _before_ my 'mistake' with shortfile)  Ditto with vi, or
> hexedit. I can always bring the executable back to the foreground, and
> things seem to work okay after that, but this is annoying.
> 
> Does anybody know what's going on? My cygwin variable is 'tty notitle
> ntea binmode'
> 
> --Chuck Wilson
> 



 ``)OZ`` > Jonathan Storey Esq. <
 Technical Systems Analyst/Programmer
 e-mail-personal:  joz@thinktank.demon.co.uk
 e-mail-business:  joz@mentor-systems.com
 e-fax-anytime:    +44(0)870 1641756
 http:  www.thinktank.demon.co.uk
 icq#:  13848691
"I can picture in my mind a world without war, 
 a world without hate. And I can picture us
 attacking that world, because they'd never
 expect it."


------------------------------------------------------------------------

The views and opinions expressed in this e-mail message are the sender's
and do not necessarily represent the views of Mentor Systems plc.

------------------------------------------------------------------------


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: less, misbehaving

[Charles Wilson]

Well, I've tried many of the suggestions given concerning this problems, but
the only thing that has changed is the description of the symptoms. Sorry
for the length of this post; you can scan for '------' to get the major
points.
--------
Recommendation 1 (Earnie Boyd): TERM=linux
    I already had this.
--------
Recommendation 2 (Jeff Sturm & Larry Hall): get latest cygwinb19.dll from
Sergey's site, and recompile ncurses and less myself, as both build easily
OOB.
    I already had latest dll, but ncurses didn't compile. I got 4.2 from the
canonical site, ftp://www.clark.net/pub/dickey/ncurses/ ...  Here's a quick
transcript snippet from configure / make:
configure:
<snip>
creating Makefile
creating include/ncurses_cfg.h
sed: Unknown option to 's'
Appending rules for normal model (ncurses)
Appending rules for debug model (ncurses)
sed: Unknown option to 's'
Appending rules for normal model (progs)
Appending rules for debug model (progs)
sed: Unknown option to 's'
Appending rules for normal model (panel)
Appending rules for debug model (panel)
sed: Unknown option to 's'
Appending rules for normal model (menu)
Appending rules for debug model (menu)
sed: Unknown option to 's'
Appending rules for normal model (form)
Appending rules for debug model (form)
sed: Unknown option to 's'
Appending rules for normal model (test)
Appending rules for debug model (test)
sed: Unknown option to 's'
Appending rules for normal model (c++)
Appending rules for debug model (c++)
creating headers.sh

** Configuration summary for NCURSES 4.2 980228:

      bin directory: /usr/local/bin
      lib directory: /usr/local/lib
  include directory: /usr/local/include
      man directory: /usr/local/man
 terminfo directory: /usr/local/share/terminfo

--I don't speak 'sed' so I can't debug this...

and from make:
/usr/local/src/ncurses-4.2/ make
cd man && make --unix INSTALL_PREFIX="" all
sh ./MKterminfo.sh ./terminfo.head ./../include/Caps ./terminfo.tail
>terminfo.5
cd include && make --unix INSTALL_PREFIX="" all
sh ./MKhashsize.sh ./Caps >hashsize.h
AWK=gawk sh ./MKparametrized.sh ./Caps >parametrized.h
gawk -f MKterm.h.awk ./Caps > term.h
sh ./edit_cfg.sh ../include/ncurses_cfg.h term.h
** edit: HAVE_TCGETATTR
** edit: HAVE_TERMIOS_H
** edit: HAVE_TERMIO_H
** edit: NCURSES_CONST
** edit: BROKEN_LINKER
cd ncurses && make --unix INSTALL_PREFIX="" all
make[1]: *** No rule to make target `all'.  Stop.
make: *** [all] Error 2

Hey, wait a minute, I didn't say "make all" so stop whining about no "all"
target. I just said "make."  Oh well.
-------------
Recommendation 3 (Jan Tomasek): type 'cat file.name | less'
    this seems to work without bombing. But why? Other people don't have to
resort to this, so what's wrong with my setup? (and Jan's, too)
-------------
Recommendation 4 (Earnie Boyd): use a different precompiled port of
ncurses/less
    haven't tried this yet, but will do so soon.
-------------
Change in my assessment of behavior:
    The pattern I described with shortfiles and longfiles is bunk. More
experimentation showed there is no pattern that I can see. Sometimes less
bombs on short files, sometimes on long files, and sometimes it doesn't
bomb. As Jan reported, 'cat file.name | less' seems to work fine. If nothing
else works, I'll put a function in my .bashrc to do this as a workaround. If
anybody has anymore suggestions, I'll take 'em, and I'll let you know if
using a different port fixes the problem.

****Andy: does your port of ncurses / less / vim use terminfo, termcap, or a
terminfo with a fallback to termcap?

--Chuck

Charles Wilson wrote:

> I'm having some wierd problems with less, and I don't know if it's my
> environment settings, or my ncurses library, or what. I'm using less
> v332 from andy's local.tar.
>
> Less operates as expected, until I try to view a file with less than a
> full screen of data. If I execute 'less shortfile', the file is
> displayed in the terminal window, followed by the message: '[1]+
> Stopped    less shortfile'
>
> >From that point on, all (?) interactive console mode programs misbehave.
> When invoking less on a file with _more_ than a full screen of data,
> e.g. 'less longfile', the first screen worth of data is displayed
> followed by '[2]+ Stopped    less longfile'. (This identical command
> worked fine _before_ my 'mistake' with shortfile)  Ditto with vi, or
> hexedit. I can always bring the executable back to the foreground, and
> things seem to work okay after that, but this is annoying.
>
> Does anybody know what's going on? My cygwin variable is 'tty notitle
> ntea binmode'
>
> --Chuck Wilson
>
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: less, misbehaving - BASH 2.02

[Gary V. Vaughan]

Jonathan Storey wrote:
> 
> I have come across this problem on my WinNT(SP3) box using
> cygwinb19(.4).dll (669150bytes) and BASH.EXE 2.0.2(1) when
> using telnet utilising Sergey's inetd remote utilities.
> 
> I have since got round the problem by reverting to BASH.EXE 2.01(1).EXE

I am still using Sergey's coolview cygwinb19.dll, and have the same
problem.  Here is a script to which I have aliased less to get around
the problem.  Is Earnie Boyd fixing bash for b20?  Or should we bring it
to the attention of someone else?

I make that two fairly critical bugs in bash that I would like addressed
in b20:

	a) The ^C sends SIGINT to all background jobs
        b) SIGTTYIN/OUT signal arrives spuriously from time to time

Cheers,
	Gary.
Cheers,
	Gary.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: less, misbehaving

[h5]

>
> sed: Unknown option to 's'

This is caused by incorrect tab -characters in Makefile, translate all your
files to unix with trans.exe (switches -i -l) and your problems will go away :)

Have you mounted your drives as binary?

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: less, misbehaving - BASH 2.02

[Gary V. Vaughan]

This time I really  did attach the script!

"Gary V. Vaughan" wrote:
> 
> Jonathan Storey wrote:
> >
> > I have come across this problem on my WinNT(SP3) box using
> > cygwinb19(.4).dll (669150bytes) and BASH.EXE 2.0.2(1) when
> > using telnet utilising Sergey's inetd remote utilities.
> >
> > I have since got round the problem by reverting to BASH.EXE 2.01(1).EXE
> 
> I am still using Sergey's coolview cygwinb19.dll, and have the same
> problem.  Here is a script to which I have aliased less to get around
> the problem.  Is Earnie Boyd fixing bash for b20?  Or should we bring it
> to the attention of someone else?
> 
> I make that two fairly critical bugs in bash that I would like addressed
> in b20:
> 
>         a) The ^C sends SIGINT to all background jobs
>         b) SIGTTYIN/OUT signal arrives spuriously from time to time
> 
> Cheers,
>         Gary.
#! /bin/sh

# work around a problem in bash-2.02 w. cygwin32 b19

LESS=${LESS-/usr/local/bin/less}

for arg; do
  case $arg in
  -)  files="$files $arg"; shift;;
  -*) LESSFLAGS="$LESSFLAGS $arg"; shift;;
  *)  files="$files $arg"; shift;;
  esac
done

cat $files | $LESS $LESSFLAGS

exit 0

Re: less, misbehaving

[Charles Wilson]

h5 wrote:

> >
> > sed: Unknown option to 's'
>
> This is caused by incorrect tab -characters in Makefile, translate all your
> files to unix with trans.exe (switches -i -l) and your problems will go away :)
>

okay, I'll try this...but I thought I had un-targz'ed using the cygwin tools (NOT
winzip) so the files should've already been in canonical Unix form with respect to
LF's (and TABs). But I'll give it a shot.

>
> Have you mounted your drives as binary?

yup, all of them are binary mounts

--Chuck


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

RE: less, misbehaving

[Suhaib M. Siddiqi]

The ncurses compilation errors you are writing can be fixed easily by doing
minor editing of configure script.  Make all can be fixed in Makefile by
editing it.  Programming does require some editing or source code and
scripts.  You can rarely port a code from one platform to another without
adapting at least Makefile and configure scripts.

Suhaib


--
=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Suhaib M. Siddiqi, Ph.D.
Senior Research Chemist
Inspire Pharmaceuticals, Inc.
4222 Emperor Blvd.,
Suite 470
Durham, NC 27703-8466

Tel:  (919) 941-9777 Ext. 238
Fax: (919) 941-9797
E-Mail: ssiddiqi@inspirepharm.com
http://www.inspirepharm.com
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

> -----Original Message-----
> From: owner-gnu-win32@cygnus.com [ mailto:owner-gnu-win32@cygnus.com]On
> Behalf Of Charles Wilson
> Sent: Monday, October 05, 1998 2:53 PM
> To: gnu-win32@cygnus.com
> Cc: Geoffrey Noer
> Subject: Re: less, misbehaving
>
>
> Well, I've tried many of the suggestions given concerning this
> problems, but
> the only thing that has changed is the description of the symptoms. Sorry
> for the length of this post; you can scan for '------' to get the major
> points.
> --------
> Recommendation 1 (Earnie Boyd): TERM=linux
>     I already had this.
> --------
> Recommendation 2 (Jeff Sturm & Larry Hall): get latest cygwinb19.dll from
> Sergey's site, and recompile ncurses and less myself, as both build easily
> OOB.
>     I already had latest dll, but ncurses didn't compile. I got
> 4.2 from the
> canonical site, ftp://www.clark.net/pub/dickey/ncurses/ ...  Here's a quick
> transcript snippet from configure / make:
> configure:
> <snip>
> creating Makefile
> creating include/ncurses_cfg.h
> sed: Unknown option to 's'
> Appending rules for normal model (ncurses)
> Appending rules for debug model (ncurses)
> sed: Unknown option to 's'
> Appending rules for normal model (progs)
> Appending rules for debug model (progs)
> sed: Unknown option to 's'
> Appending rules for normal model (panel)
> Appending rules for debug model (panel)
> sed: Unknown option to 's'
> Appending rules for normal model (menu)
> Appending rules for debug model (menu)
> sed: Unknown option to 's'
> Appending rules for normal model (form)
> Appending rules for debug model (form)
> sed: Unknown option to 's'
> Appending rules for normal model (test)
> Appending rules for debug model (test)
> sed: Unknown option to 's'
> Appending rules for normal model (c++)
> Appending rules for debug model (c++)
> creating headers.sh
>
> ** Configuration summary for NCURSES 4.2 980228:
>
>       bin directory: /usr/local/bin
>       lib directory: /usr/local/lib
>   include directory: /usr/local/include
>       man directory: /usr/local/man
>  terminfo directory: /usr/local/share/terminfo
>
> --I don't speak 'sed' so I can't debug this...
>
> and from make:
> /usr/local/src/ncurses-4.2/ make
> cd man && make --unix INSTALL_PREFIX="" all
> sh ./MKterminfo.sh ./terminfo.head ./../include/Caps ./terminfo.tail
> >terminfo.5
> cd include && make --unix INSTALL_PREFIX="" all
> sh ./MKhashsize.sh ./Caps >hashsize.h
> AWK=gawk sh ./MKparametrized.sh ./Caps >parametrized.h
> gawk -f MKterm.h.awk ./Caps > term.h
> sh ./edit_cfg.sh ../include/ncurses_cfg.h term.h
> ** edit: HAVE_TCGETATTR
> ** edit: HAVE_TERMIOS_H
> ** edit: HAVE_TERMIO_H
> ** edit: NCURSES_CONST
> ** edit: BROKEN_LINKER
> cd ncurses && make --unix INSTALL_PREFIX="" all
> make[1]: *** No rule to make target `all'.  Stop.
> make: *** [all] Error 2
>
> Hey, wait a minute, I didn't say "make all" so stop whining about no "all"
> target. I just said "make."  Oh well.
> -------------
> Recommendation 3 (Jan Tomasek): type 'cat file.name | less'
>     this seems to work without bombing. But why? Other people
> don't have to
> resort to this, so what's wrong with my setup? (and Jan's, too)
> -------------
> Recommendation 4 (Earnie Boyd): use a different precompiled port of
> ncurses/less
>     haven't tried this yet, but will do so soon.
> -------------
> Change in my assessment of behavior:
>     The pattern I described with shortfiles and longfiles is bunk. More
> experimentation showed there is no pattern that I can see. Sometimes less
> bombs on short files, sometimes on long files, and sometimes it doesn't
> bomb. As Jan reported, 'cat file.name | less' seems to work fine.
> If nothing
> else works, I'll put a function in my .bashrc to do this as a
> workaround. If
> anybody has anymore suggestions, I'll take 'em, and I'll let you know if
> using a different port fixes the problem.
>
> ****Andy: does your port of ncurses / less / vim use terminfo,
> termcap, or a
> terminfo with a fallback to termcap?
>
> --Chuck
>
> Charles Wilson wrote:
>
> > I'm having some wierd problems with less, and I don't know if it's my
> > environment settings, or my ncurses library, or what. I'm using less
> > v332 from andy's local.tar.
> >
> > Less operates as expected, until I try to view a file with less than a
> > full screen of data. If I execute 'less shortfile', the file is
> > displayed in the terminal window, followed by the message: '[1]+
> > Stopped    less shortfile'
> >
> > >From that point on, all (?) interactive console mode programs
> misbehave.
> > When invoking less on a file with _more_ than a full screen of data,
> > e.g. 'less longfile', the first screen worth of data is displayed
> > followed by '[2]+ Stopped    less longfile'. (This identical command
> > worked fine _before_ my 'mistake' with shortfile)  Ditto with vi, or
> > hexedit. I can always bring the executable back to the foreground, and
> > things seem to work okay after that, but this is annoying.
> >
> > Does anybody know what's going on? My cygwin variable is 'tty notitle
> > ntea binmode'
> >
> > --Chuck Wilson
> >
> > -
> > For help on using this list (especially unsubscribing), send a
> message to
> > "gnu-win32-request@cygnus.com" with one line of text: "help".
>
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".
>

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: less, misbehaving

[Geoffrey Noer]

On Mon, Oct 05, 1998 at 02:52:40PM -0400, Charles Wilson wrote:
[...]
>     I already had latest dll, but ncurses didn't compile. I got 4.2 from the
> canonical site, ftp://www.clark.net/pub/dickey/ncurses/ ...  Here's a quick
> transcript snippet from configure / make:
[...]
> Appending rules for debug model (test)
> sed: Unknown option to 's'
> Appending rules for normal model (c++)
> Appending rules for debug model (c++)
> creating headers.sh
[...]
> sh ./edit_cfg.sh ../include/ncurses_cfg.h term.h
> ** edit: HAVE_TCGETATTR
> ** edit: HAVE_TERMIOS_H
> ** edit: HAVE_TERMIO_H
> ** edit: NCURSES_CONST
> ** edit: BROKEN_LINKER
> cd ncurses && make --unix INSTALL_PREFIX="" all
> make[1]: *** No rule to make target `all'.  Stop.
> make: *** [all] Error 2

I'm seeing this problem as well with my latest pre-b20 build.  If
anyone knows the solution, please let me know.  I would like to
include ncurses/less in b20.

-- 
Geoffrey Noer
noer@cygnus.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: less, misbehaving

[Charles Wilson]

Charles Wilson wrote:

> Well, I've tried many of the suggestions given concerning this problems, but
> the only thing that has changed is the description of the symptoms. Sorry
> for the length of this post; you can scan for '------' to get the major
> points.
> --------
> Recommendation 1 (Earnie Boyd): TERM=linux
>     I already had this.
> --------
> Recommendation 2 (Jeff Sturm & Larry Hall): get latest cygwinb19.dll from
> Sergey's site, and recompile ncurses and less myself, as both build easily
> OOB.
>     I already had latest dll, but ncurses didn't compile. I got 4.2 from the
> canonical site, ftp://www.clark.net/pub/dickey/ncurses/ ...  Here's a quick
> transcript snippet from configure / make:

<big snip>

> -------------
> Recommendation 3 (Jan Tomasek): type 'cat file.name | less'
>     this seems to work without bombing. But why? Other people don't have to
> resort to this, so what's wrong with my setup? (and Jan's, too)
> -------------
> Recommendation 4 (Earnie Boyd): use a different precompiled port of
> ncurses/less
>     haven't tried this yet, but will do so soon.

Tried it. didn't work.

<more snips>

Two things did work, however:
--------------
Recommendation 5 (Jonathan Storey): use old bash version
So, I replaced bash-2.0.2(1) with bash-2.0.1(2) Now less works just fine. The
only problem that could crop up (although I haven't seen it) - didn't
bash-2.0.1(2) have some wierd problems with random pauses? I seem to remember
seeing that on the mailing list archives, but it was before I started using
gnu-win (I've been using bash-2.0.2(1) exclusively from the beginning).

QUESTION: one of the main changes in these two version of bash was the switch
from fork() in the older version to spawn()/exec() in the newer one. (I think)
Could that be the difficulty here? I quote part of Jonathan's explanation:

"Whats happening here is that the process is requesting input from
the terminal i.e END: (less's case) and the shell thinks that the
process is in background. Under UNIX the message would be
Stopped: (tty input) or similar. Therefore I would conclude that
the new version of BASH.EXE is incorrectly flagging processes
as being in background albeit intermittently, although using
less(1) to output a file that is less than a screen full seems to
cause the problem to manifest itself consistently..."
----------------
The following over-engineered bashrc function works with bash-2.0.2(1)

# this deals adequately with the less misbehavior problems.
# downside: can only "less" one file at a time (I know, that means
# the prompts could do without the "file %i of %m" stuff, but I wanted
# to keep everything as close to the defaults as I could.)
# The +Gg options force less to run down to the end of the file, and back
# to the beginning..this allows less to know how many lines are in the
# file for displaying "line x of X" and percentage in the prompts.
# I don't find this distracting, since my K6-200 is fast enough that I
# don't see the display flickering to the end-of-file and back.
less() {
        local fn=$1
        shift
        cat $fn | /usr/local/bin/less -PM"$fn .?n?m(file %i of %m) \
..?ltline %lt?L/%L. :byte %bB?s/%s. .?e(END) ?x- Next\\: \
%x.:?pB%pB\\%..%t\$ -Pm?n$fn .?m(file %i of %m) ..?e(END) ?x- Next\\: \
%x.:?pB%pB\\%:byte %bB?s/%s...%t\$ -Ps?n$fn .?m(file %i of %m) ..?e(END) \
?x- Next\\: %x..%t\$" +Gg $*
}
export LESS="-isMd"

--Chuck


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: compiling ncurses (WAS Re: less, misbehaving)

[Charles Wilson]

Geoffrey Noer wrote:

> I'm seeing this problem as well with my latest pre-b20 build.  If
> anyone knows the solution, please let me know.  I would like to
> include ncurses/less in b20.
>

Larry Hall said: "Someone recently added an option
for bash of the form "@<file>" where <file> is the name of a file.  This
causes problems for a sed script that uses '@' as field separators."

He's right - "@" is the problem, but you can't use "/" as the separator in the
offending sed command, because the search/replace strings are pathnames and might
contain "/". I applied the attached patch and everything compiled fine. The patch
modifies line 5917 only, and changes some of the @'s in that line to %'s.

-               sed -e "s@\@LIBS_TO_MAKE\@@$cf_libs_to_make@" \
+               sed -e "s%\@LIBS_TO_MAKE\@%$cf_libs_to_make%" \

I ran the test programs, and it seemed okay when I ran bash -login from an NT
command window. However, in an rxvt window, the test programs ran without
crashing, but had minor display defects. I dunno - it's probably my font / env
var settings.

I haven't tried to build a new "less" against this ncurses, but I think consensus
is that my original "less misbehaving" problem was a bash version thing, and not
an ncurses thing.

--Chuck

Re: compiling ncurses (WAS Re: less, misbehaving)

[Geoffrey Noer]

On Wed, Oct 07, 1998 at 01:59:00AM -0400, Charles Wilson wrote:
>
> Larry Hall said: "Someone recently added an option
> for bash of the form "@<file>" where <file> is the name of a file.  This
> causes problems for a sed script that uses '@' as field separators."

Yeah, we're in the midst of fixing the code in Cygwin that handles
@file.  This one's our fault.  :-)

> He's right - "@" is the problem, but you can't use "/" as the
> separator in the offending sed command, because the search/replace
> strings are pathnames and might contain "/". I applied the attached
> patch and everything compiled fine. The patch modifies line 5917
> only, and changes some of the @'s in that line to %'s.

I've also seen this problem though in sed expressions which don't
contain the @ symbol so that's not the only problem I'm seeing.
Well, I'll go play with it some more...

-- 
Geoffrey Noer
noer@cygnus.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: less, misbehaving

[Earnie Boyd]

The modified bash on Sergey's site only spawns if there is no piping
or no redirection.  The problem is that the spawnve() command is
issued with the _P_NOWAIT flag which will not allow less to control
the stdio.  If this were changed to _P_WAIT then you shouldn't see any
problems with less.  Also, it would be a good idea to flushall()
before spawning.

BTW, since `cat file | less' didn't use the spawnve() it worked as it
should have.

==
-                \\||//
-----------o0O0--Earnie--0O0o------------
--        earnie_boyd@yahoo.com        --
-- http://freeyellow.com/members5/gw32 --
--------------ooo0O--O0ooo---------------

PS: Newbie's, you should visit my page.
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

RE: less, misbehaving

[Parker, Ron]

If my /bin/sh is not bash, I get this behavior during some configures or
builds.

-----Original Message-----
From: Geoffrey Noer [ mailto:noer@cygnus.com ]
Sent: Tuesday, October 06, 1998 7:00 PM
To: Charles Wilson
Cc: gnu-win32@cygnus.com
Subject: Re: less, misbehaving


On Mon, Oct 05, 1998 at 02:52:40PM -0400, Charles Wilson wrote:
[...]
>     I already had latest dll, but ncurses didn't compile. I got 4.2
from the
> canonical site, ftp://www.clark.net/pub/dickey/ncurses/ ...  Here's a
quick
> transcript snippet from configure / make:
[...]
> Appending rules for debug model (test)
> sed: Unknown option to 's'
> Appending rules for normal model (c++)
> Appending rules for debug model (c++)
> creating headers.sh
[...]
> sh ./edit_cfg.sh ../include/ncurses_cfg.h term.h
> ** edit: HAVE_TCGETATTR
> ** edit: HAVE_TERMIOS_H
> ** edit: HAVE_TERMIO_H
> ** edit: NCURSES_CONST
> ** edit: BROKEN_LINKER
> cd ncurses && make --unix INSTALL_PREFIX="" all
> make[1]: *** No rule to make target `all'.  Stop.
> make: *** [all] Error 2

I'm seeing this problem as well with my latest pre-b20 build.  If
anyone knows the solution, please let me know.  I would like to
include ncurses/less in b20.

-- 
Geoffrey Noer
noer@cygnus.com
-
For help on using this list (especially unsubscribing), send a message
to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: less, misbehaving

[Jan Tomasek]

Hi,
I'm using Andy's port, and I've same problems but I've discovered
that if I do type 'cat file.name |less' I've no problem.

Bye Jan
-- 
                            Jan Tomasek,          student FEL-CVUT
                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                            e-mail: xtomasej@fel.cvut.cz
                            www: http://www.feld.cvut.cz/~xtomasej
                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~H~


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: less, misbehaving

[Earnie Boyd]

What TERM setting are you using?

It is suggested that you `export TERM=linux'.

There are other ports of less, check my web page at
http://www.freeyellow.com/members5/gw32

---Charles Wilson <cwilson@ee.gatech.edu> wrote:
>
> This problem is the only thing delaying a full rollout of gnu-win at
my
> workplace. Can anybody help?
> 
> Charles Wilson wrote:
> 
> > I'm having some wierd problems with less, and I don't know if it's
my
> > environment settings, or my ncurses library, or what. I'm using less
> > v332 from andy's local.tar.
> >
> > Less operates as expected, until I try to view a file with less
than a
> > full screen of data. If I execute 'less shortfile', the file is
> > displayed in the terminal window, followed by the message: '[1]+
> > Stopped    less shortfile'
> >
> > >From that point on, all (?) interactive console mode programs
misbehave.
> > When invoking less on a file with _more_ than a full screen of data,
> > e.g. 'less longfile', the first screen worth of data is displayed
> > followed by '[2]+ Stopped    less longfile'. (This identical command
> > worked fine _before_ my 'mistake' with shortfile)  Ditto with vi, or
> > hexedit. I can always bring the executable back to the foreground,
and
> > things seem to work okay after that, but this is annoying.
> >
> > Does anybody know what's going on? My cygwin variable is 'tty
notitle
> > ntea binmode'
> >
> > --Chuck Wilson
> 
> -
> For help on using this list (especially unsubscribing), send a
message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".
> 

==
-                \\||//
-----------o0O0--Earnie--0O0o------------
--        earnie_boyd@yahoo.com        --
-- http://freeyellow.com/members5/gw32 --
--------------ooo0O--O0ooo---------------

PS: Newbie's, you should visit my page.
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".