Issue 184 in msysgit: GNU less reports WARNING: terminal is not fully functional
codesite...@google.com
Comment #13 on issue 184 by peter.is.a.geek: GNU less reports WARNING:
terminal is not fully functional
http://code.google.com/p/msysgit/issues/detail?id=184
For what it's worth, less 418 has native ANSI emulation support for Win32.
I've been
avoiding the 'not fully functional' cmd.exe problem by deleting the copy
of 'less'
bundled with msysgit, setting LESS=R, and placing the Win32 binary from
http://www.greenwoodsoftware.com/less/ on my path.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
codesite...@google.com
Comment #14 on issue 184 by kusmabite: GNU less reports WARNING: terminal
http://code.google.com/p/msysgit/issues/detail?id=184
Thanks for the tip. Doing so would surely make my day more pleasant, but
I'd also
like to figure out why this started happening here lately instead of just
hiding the
symptoms. :)
codesite...@google.com
Comment #15 on issue 184 by johannes.schindelin: GNU less reports WARNING:
http://code.google.com/p/msysgit/issues/detail?id=184
kusmabite: I have a hunch that maybe the wrong 'less' is called. Could you
experiment if your 'less' complains about the not fully functional terminal
at all
when called directly from the bash?
codesite...@google.com
Comment #16 on issue 184 by kusmabite: GNU less reports WARNING: terminal
http://code.google.com/p/msysgit/issues/detail?id=184
[kusma@KUSMABITE usr (master)]$ /c/msysgit/bin/less
WARNING: terminal is not fully functional
Missing filename ("less --help" for help)
[kusma@KUSMABITE usr (master)]$
So no, I'm pretty sure I'm calling the right less.
codesite...@google.com
Comment #17 on issue 184 by kusmabite: GNU less reports WARNING: terminal
http://code.google.com/p/msysgit/issues/detail?id=184
By the way, the less.exe I have was added in commit 2914373, and hasn't
been modified
since. I'm on the master-branch.
codesite...@google.com
Comment #18 on issue 184 by aaroncraelius: GNU less reports WARNING:
http://code.google.com/p/msysgit/issues/detail?id=184
For all those that are having this problem, as I reported earlier
(http://code.google.com/p/msysgit/issues/detail?id=184#c1) adding export
TERM=msys to
~/.bashrc always seems to fix it.
It would help if those experiencing the problem indicated whether or not
this fixes
it. Before setting this echo $TERM usually outputs "dumb". Must be that
less checks
the TERM variable to see if it's something it likes and then outputs that
message.
Would be pretty easy to search the GNU less code for that WARNING and see
what
triggers it...
codesite...@google.com
Comment #19 on issue 184 by johannes.schindelin: GNU less reports WARNING:
http://code.google.com/p/msysgit/issues/detail?id=184
The thing is: it _works_ here, with TERM=cygwin.
codesite...@google.com
Comment #20 on issue 184 by kusmabite: GNU less reports WARNING: terminal
http://code.google.com/p/msysgit/issues/detail?id=184
aaroncraelius, as I said in comment #7 - it does not fix the issue for me.
codesite...@google.com
Comment #21 on issue 184 by johannes.schindelin: GNU less reports WARNING:
http://code.google.com/p/msysgit/issues/detail?id=184
Hey, I got lucky: Googling for 'msys less warning "not fully functional"'
not only
brought up this msysGit issue, but also some thread on the MSys mailing
list:
http://www.nabble.com/info,-less-etc-not-working-after-update-td19232562.html
Could you verify that your /etc/termcap contains these lines (and nothing
else about
'cygwin')?
cygwin:\
:xn@:op=\E[39;49m:Km=\E[M:tc=linux:
codesite...@google.com
Comment #22 on issue 184 by kusmabite: GNU less reports WARNING: terminal
http://code.google.com/p/msysgit/issues/detail?id=184
[kusma@KUSMABITE etc (master)]$ grep "cygwin" -A 2 /etc/termcap
cygwin:\
:xn@:op=\E[39;49m:Km=\E[M:tc=linux:
So yes, it does indeed contain those lines. My /etc/termcap was (also)
introduced in
commit 2914373, and never changed. Removing the termcap-file (as seemed to
be the
solution for the poster on that nabble-page) does not help.
Is there anything I can do to ensure that /etc/termcap is the termcap-file
being
used?
codesite...@google.com
Comment #23 on issue 184 by johannes.schindelin: GNU less reports WARNING:
http://code.google.com/p/msysgit/issues/detail?id=184
Do you have a .termcap or some such?
codesite...@google.com
Comment #24 on issue 184 by kusmabite: GNU less reports WARNING: terminal
http://code.google.com/p/msysgit/issues/detail?id=184
I don't have a ~/.termcap, if that's what you're asking. Is there anything
else I
should look out for?
codesite...@google.com
Comment #25 on issue 184 by kusmabite: GNU less reports WARNING: terminal
http://code.google.com/p/msysgit/issues/detail?id=184
One thing perhaps worth noting is that I do have a ~/.profile, that seems
to be
executed at setup, resulting in a "bash: .bashrc: No such file or
directory"-error
when starting up (because I usually don't start msysgit from my home-dir,
and my
.profile does assume so). Removing the ~/.profile does not help.
codesite...@google.com
Comment #26 on issue 184 by johannes.schindelin: GNU less reports WARNING:
http://code.google.com/p/msysgit/issues/detail?id=184
Hmm, I am out of ideas... Could you try a Google search yourself?
codesite...@google.com
Comment #27 on issue 184 by kusmabite: GNU less reports WARNING: terminal
http://code.google.com/p/msysgit/issues/detail?id=184
Do you really think I haven't bothered searching? :)
But yeah, I can play around a bit more and see if something pops out.
codesite...@google.com
Comment #28 on issue 184 by johannes.schindelin: GNU less reports WARNING:
http://code.google.com/p/msysgit/issues/detail?id=184
No, I think you did a Google search, but like I found something in comment
21, you
might find something new now, too.
No offense was intended.
codesite...@google.com
Comment #29 on issue 184 by kusmabite: GNU less reports WARNING: terminal
http://code.google.com/p/msysgit/issues/detail?id=184
I didn't take offense, don't think about it ;)
Anyway, I've found out what's going on here! my ~/.gitconfig has
core.autocrlf set to
"true", and it seems that the less shipped with msysgit doesn't handle
windows new-
lines in /etc/termcap. If I run "dos2unix /etc/termcap" the warning goes
away, and
less behaves as expected.
Attached is a commit (formatted with "git format-patch") that forces
/etc/termcap to
be checked out with unix-newlines. I'd call it a work-around, because I
believe a
less build for windows (even msys) should ideally handle windows
line-endings. On the
other hand, perhaps it'd be useful to make sure everything under /etc/ has
unix line-
endings to avoid similar issues later (even if it possibly could mask away
small
issues).
Attachments:
0001-.giattributes-make-sure-etc-termcap-has-unix-line.patch 839 bytes
codesite...@google.com
Comment #30 on issue 184 by kusmabite: GNU less reports WARNING: terminal
http://code.google.com/p/msysgit/issues/detail?id=184
I'm sorry that I didn't send this patch to the list, but I don't currently
have an
internet connection at home, and I've only been able to set up git
send-email to work
with an smtp-server, and I don't have access to one that I can use from
wherever I
want (as far as I know).
codesite...@google.com
Status: Fixed
Comment #31 on issue 184 by johannes.schindelin: GNU less reports WARNING:
terminal is not fully functional
http://code.google.com/p/msysgit/issues/detail?id=184
No need to be sorry! Thanks for your persistence and your fix (which I
applied with
a slightly adjusted commit message)!