bug#6535: 24.0.50; grep seems not to work

bug#6535: 24.0.50; grep seems not to work

[john ffitch]

I an in dired mode and attempt to do M-x grep
It hangs; if I try again later it says i still have a grep process
reports
-*- mode: grep; default-directory: "~/Sourceforge/csound5/Engine/" -*-
Grep started at Mon Jun 28 17:58:43

grep -nH -e cpuprc *.c
tset: unknown terminal type emacs-grep
Terminal type? 

The grep seems to hang at this point.  It used to work.  Tried
searching for terminal type without success

In GNU Emacs 24.0.50.3 (x86_64-unknown-linux-gnu, GTK+ Version 2.18.6)
 of 2010-06-17 on harvey
Windowing system distributor `The X.Org Foundation', version 11.0.10605000
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_GB.UTF-8
  value of $XMODIFIERS: @im=local
  locale-coding-system: utf-8-unix
  default enable-multibyte-characters: t

Major mode: Dired by name

Minor modes in effect:
  auto-image-file-mode: t
  show-paren-mode: t
  display-time-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
<up> <up> <down> S h e SPC w a s SPC l i v i n g SPC 
w i t h SPC h u s n <backspace> b a n d , SPC s t e 
p <backspace> <backspace> <backspace> <backspace> s 
o n SPC b y SPC f u <backspace> i r t s SPC m a r r 
i a g e SPC <backspace> , SPC a n d SPC 4 SPC s o n 
s SPC b y SPC s e c o n d SPC <down-mouse-1> <mouse-1> 
C-t <down> i n SPC F u n t i n g d o n SPC i n SPC 
1 9 0 1 <return> <down-mouse-1> <mouse-1> , SPC o r 
SPC a n y SPC f u r t h e r SPC s u g g e s t i o n 
s SPC o r C-\ C-g C-e SPC C-d <down-mouse-1> <mouse-1> 
SPC ( i e SPC b 1 8 7 3 ) <down-mouse-1> <mouse-1> 
( o f SPC SPC 7 <backspace> <backspace> 7 ) SPC M-q 
C-x C-s C-x k <return> d n n d SPC n s y C-x C-f S 
O u r <tab> <backspace> <backspace> <backspace> o u 
r c e <tab> c s p o u <backspace> <backspace> <backspace> 
o <tab> 5 / E n g i <tab> e n t <tab> c <return> C-s 
c p u p r c C-x C-f <backspace> <backspace> <backspace> 
<backspace> <backspace> <backspace> <backspace> O p 
c o <tab> <return> M-x g r e p <return> c p u p r c 
SPC * . c <return> M-c M-x e m a c s - r <tab> <backspace> 
<backspace> <backspace> <backspace> <backspace> <backspace> 
<backspace> r e p o <tab> i <backspace> r t <tab> 
<return>

Recent messages:
Invalid face reference: my-trailing-space-face
Invalid face reference: my-tab-face
Loading vc-cvs...done
Mark saved where search started
Loading dired-add...done
Invalid face reference: my-trailing-space-face [2 times]
call-interactively: Buffer is read-only: #<buffer Opcodes>Invalid face reference: my-trailing-space-face
Invalid face reference: my-trailing-space-face [3 times]
Making completion list...
Invalid face reference: my-trailing-space-face

Load-path shadows:
/home/jpff/GNU_21/local-lisp/scroll-lock hides /home/jpff/GNU_21/emacs/trunk/lisp/scroll-lock
/home/jpff/GNU_21/local-lisp/t-mouse hides /home/jpff/GNU_21/emacs/trunk/lisp/t-mouse
/home/jpff/GNU_21/local-lisp/ruler-mode hides /home/jpff/GNU_21/emacs/trunk/lisp/ruler-mode
/home/jpff/GNU_21/local-lisp/emerge hides /home/jpff/GNU_21/emacs/trunk/lisp/vc/emerge
/home/jpff/GNU_21/local-lisp/url-gw hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-gw
/home/jpff/GNU_21/local-lisp/url-file hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-file
/home/jpff/GNU_21/local-lisp/url-cid hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-cid
/home/jpff/GNU_21/local-lisp/url-parse hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-parse
/home/jpff/GNU_21/local-lisp/url-cache hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-cache
/home/jpff/GNU_21/local-lisp/url-http hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-http
/home/jpff/GNU_21/local-lisp/url-misc hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-misc
/home/jpff/GNU_21/local-lisp/url hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url
/home/jpff/GNU_21/local-lisp/url-auth hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-auth
/home/jpff/GNU_21/local-lisp/url-ldap hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-ldap
/home/jpff/GNU_21/local-lisp/url-news hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-news
/home/jpff/GNU_21/local-lisp/url-vars hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-vars
/home/jpff/GNU_21/local-lisp/url-cookie hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-cookie
/home/jpff/GNU_21/local-lisp/url-nfs hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-nfs
/home/jpff/GNU_21/local-lisp/url-ns hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-ns
/home/jpff/GNU_21/local-lisp/url-irc hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-irc
/home/jpff/GNU_21/local-lisp/remember hides /home/jpff/GNU_21/emacs/trunk/lisp/textmodes/remember
/home/jpff/GNU_21/local-lisp/socks hides /home/jpff/GNU_21/emacs/trunk/lisp/net/socks

Features:
(shadow emacsbug help-mode grep compile dired multi-isearch parse-time
vc-cvs imenu cc-mode cc-fonts cc-menus cc-cmds cc-styles cc-align
cc-engine cc-vars cc-defs ispell feedmail newcomment mailabbrev
mailalias rmailout rmailkwd etach sendmail mime-compose
mail-alias-menu mailcrypt mail-extr comint ring rmail mail-utils eldoc
package image-file logger crypt crypt++ crypt+pgp-pub paren cal-julian
uniquify advice help-fns advice-preload view cal-china cal-bahai
cal-islam cal-hebrew lunar solar cal-dst appt diary-lib diary-loaddefs
holidays hol-loaddefs regexp-opt cal-menu easymenu calendar
cal-loaddefs time tooltip ediff-hook vc-hooks lisp-float-type mwheel
x-win x-dnd tool-bar dnd fontset image fringe lisp-mode register page
menu-bar rfn-eshadow timer select scroll-bar mldrag mouse jit-lock
font-lock syntax facemenu font-core frame cham georgian utf-8-lang
misc-lang vietnamese tibetan thai tai-viet lao korean japanese hebrew
greek romanian slovak czech european ethiopic indian cyrillic chinese
case-table epa-hook jka-cmpr-hook help simple abbrev loaddefs button
minibuffer faces cus-face files text-properties overlay md5 base64
format env code-pages mule custom widget hashtable-print-readable
backquote make-network-process dynamic-setting font-render-setting gtk
x-toolkit x multi-tty emacs)

==John ffitch

bug#6535: 24.0.50; grep seems not to work

[Štěpán Němec]

john ffitch <jpff@codemist.co.uk> writes:

> I an in dired mode and attempt to do M-x grep
> It hangs; if I try again later it says i still have a grep process
> reports
> -*- mode: grep; default-directory: "~/Sourceforge/csound5/Engine/" -*-
> Grep started at Mon Jun 28 17:58:43
>
> grep -nH -e cpuprc *.c
> tset: unknown terminal type emacs-grep
> Terminal type? 
>
> The grep seems to hang at this point.  It used to work.  Tried
> searching for terminal type without success

You might try to set `debug-on-quit' and when Emacs hangs, press C-g and
send the backtrace.

Anyway, the problem looks very much like the issue discussed here:

http://article.gmane.org/gmane.emacs.devel/126393

Unfortunately, the developers seem to be ignoring it.

bug#6535: 24.0.50; grep seems not to work

[Jan Djärv]

Štěpán Němec skrev 2010-06-29 10.31:
> john ffitch<jpff@codemist.co.uk>  writes:
>
>> I an in dired mode and attempt to do M-x grep
>> It hangs; if I try again later it says i still have a grep process
>> reports
>> -*- mode: grep; default-directory: "~/Sourceforge/csound5/Engine/" -*-
>> Grep started at Mon Jun 28 17:58:43
>>
>> grep -nH -e cpuprc *.c
>> tset: unknown terminal type emacs-grep
 >
> You might try to set `debug-on-quit' and when Emacs hangs, press C-g and
> send the backtrace.
>
> Anyway, the problem looks very much like the issue discussed here:
>
> http://article.gmane.org/gmane.emacs.devel/126393

The hang may be caused by that problem, but the cause is the terminal type 
being set is not recognized.  Fixing the hang will probably not make grep work 
in this case.

>
> Unfortunately, the developers seem to be ignoring it.
>

I think the correct term is "not talking about the work being done in public" :-)

	Jan D.

bug#6535: 24.0.50; grep seems not to work

[Štěpán Němec]

Jan Djärv <jan.h.d@swipnet.se> writes:

> Štěpán Němec skrev 2010-06-29 10.31:
>> Anyway, the problem looks very much like the issue discussed here:
>>
>> http://article.gmane.org/gmane.emacs.devel/126393
>
> The hang may be caused by that problem, but the cause is the terminal type
> being set is not recognized. Fixing the hang will probably not make grep work
> in this case.
>
>>
>> Unfortunately, the developers seem to be ignoring it.
>>
>
> I think the correct term is "not talking about the work being done in public"
> :-)

Nothing suggests anyone is working on fixing the problem. If you have a
fix, why don't you commit it? If you don't have a fix *now*, why is the
breakage not reverted for the time being? I didn't even get any reaction
on this question.

I don't expect the trunk to be perfectly usable all the time, but I fail
to see any value in leaving a known and repeatedly reported breakage in
for an extended period of time.

Anyway, thanks for at least expressing your (IMO overly) optimistic view
on the matter.

Štěpán

bug#6535: 24.0.50; grep seems not to work

[Jan Djärv]

Štěpán Němec skrev 2010-06-29 13.14:
>
> Nothing suggests anyone is working on fixing the problem. If you have a
> fix, why don't you commit it?

I don't have a recepie for repeating the problem turning off ICANON would 
solve.  It isn't a high priority for me.

> If you don't have a fix *now*, why is the
> breakage not reverted for the time being? I didn't even get any reaction
> on this question.

That you must ask the person who made that checkin.

>
> I don't expect the trunk to be perfectly usable all the time, but I fail
> to see any value in leaving a known and repeatedly reported breakage in
> for an extended period of time.
>

The breakage must have fixed some other problem.  If breakage one is better 
than breakage two is a matter of opinion, depending which one you see the 
most.  AFAIK, I haven't seen either.

	Jan D.

bug#6535: 24.0.50; grep seems not to work

[Štěpán Němec]

Jan Djärv <jan.h.d@swipnet.se> writes:

> Štěpán Němec skrev 2010-06-29 13.14:
>>
>> Nothing suggests anyone is working on fixing the problem. If you have a
>> fix, why don't you commit it?
>
> I don't have a recepie for repeating the problem turning off ICANON would
> solve.  It isn't a high priority for me.

I wonder what makes you assume somebody is working on it then.

>> If you don't have a fix *now*, why is the
>> breakage not reverted for the time being? I didn't even get any reaction
>> on this question.
>
> That you must ask the person who made that checkin.

...which I did. I posted the URL in this thread already.

>>
>> I don't expect the trunk to be perfectly usable all the time, but I fail
>> to see any value in leaving a known and repeatedly reported breakage in
>> for an extended period of time.
>>
>
> The breakage must have fixed some other problem.  If breakage one is better
> than breakage two is a matter of opinion, depending which one you see the
> most.  AFAIK, I haven't seen either.

I can't make much sense of Stefan's commit message. It also doesn't
mention any related bug it would be supposed to fix.

>
> 	Jan D.

bug#6535: 24.0.50; grep seems not to work

[Jan Djärv]

Štěpán Němec skrev 2010-06-29 20.27:
> Jan Djärv<jan.h.d@swipnet.se>  writes:
>
>> Štěpán Němec skrev 2010-06-29 13.14:
>>>
>>> Nothing suggests anyone is working on fixing the problem. If you have a
>>> fix, why don't you commit it?
>>
>> I don't have a recepie for repeating the problem turning off ICANON would
>> solve.  It isn't a high priority for me.
>
> I wonder what makes you assume somebody is working on it then.

I did some tests when this come up.  Basically I adopted xterm:s approach with 
buffering.  But this makes send_process asynchronous when the subprocess isn't 
reading.  It may be a too big of a change.
Besides, with the current send_process implementation, it does seem to do the 
right thing, so asynchronous send is perhaps not needed.  As I said, I haven't 
been able to trigger any problem with it, RAW or ICANON.  The only problem is 
if the subprocess doesn't read, Emacs hangs forever.

The code and the documentation is not in sync w.r.t. EOF either.

>
>>> If you don't have a fix *now*, why is the
>>> breakage not reverted for the time being? I didn't even get any reaction
>>> on this question.
>>
>> That you must ask the person who made that checkin.
>
> ...which I did. I posted the URL in this thread already.

He may not read this thread.

>
>>>
>>> I don't expect the trunk to be perfectly usable all the time, but I fail
>>> to see any value in leaving a known and repeatedly reported breakage in
>>> for an extended period of time.
>>>
>>
>> The breakage must have fixed some other problem.  If breakage one is better
>> than breakage two is a matter of opinion, depending which one you see the
>> most.  AFAIK, I haven't seen either.
>
> I can't make much sense of Stefan's commit message. It also doesn't
> mention any related bug it would be supposed to fix.

The code mentions the same problem to the current one (EOF showing up as ^D) 
because the terminal is in raw mode.  The scenario is that Emacs puts the 
terminal in icanon mode and then the subprocess puts it in raw, ^D will be 
seen by the subprocess because Emacs sends EOF as a means to flush output.

But AFAIK, Emacs doesn't send EOF to flush output anymore.

So I wont put in my stuff until Stefan has commented on his.  I don't think 
this is a pressing matter, this is the trunk after all, and people have other 
things to do.  It must be resolved before next release though.

	Jan D.

bug#6535: 24.0.50; grep seems not to work

[Jan Djärv]

What kind of shell are you running?  Are you doing any stty or other terminal 
related things in your dot-files for that shell?  Are there perhaps some 
global files that the shell reads on startup, for example /etc/bashrc?

How does it look if you put

   TERM=vt100 grep -nH -e cp cpuprc *.c

as the grep command?

john ffitch skrev 2010-06-28 18.59:
> I an in dired mode and attempt to do M-x grep
> It hangs; if I try again later it says i still have a grep process
> reports
> -*- mode: grep; default-directory: "~/Sourceforge/csound5/Engine/" -*-
> Grep started at Mon Jun 28 17:58:43
>
> grep -nH -e cpuprc *.c
> tset: unknown terminal type emacs-grep
> Terminal type?
>
> The grep seems to hang at this point.  It used to work.  Tried
> searching for terminal type without success
>
> In GNU Emacs 24.0.50.3 (x86_64-unknown-linux-gnu, GTK+ Version 2.18.6)
>   of 2010-06-17 on harvey
> Windowing system distributor `The X.Org Foundation', version 11.0.10605000
> Important settings:
>    value of $LC_ALL: nil
>    value of $LC_COLLATE: nil
>    value of $LC_CTYPE: nil
>    value of $LC_MESSAGES: nil
>    value of $LC_MONETARY: nil
>    value of $LC_NUMERIC: nil
>    value of $LC_TIME: nil
>    value of $LANG: en_GB.UTF-8
>    value of $XMODIFIERS: @im=local
>    locale-coding-system: utf-8-unix
>    default enable-multibyte-characters: t
>
> Major mode: Dired by name
>
> Minor modes in effect:
>    auto-image-file-mode: t
>    show-paren-mode: t
>    display-time-mode: t
>    tooltip-mode: t
>    mouse-wheel-mode: t
>    menu-bar-mode: t
>    file-name-shadow-mode: t
>    global-font-lock-mode: t
>    font-lock-mode: t
>    auto-composition-mode: t
>    auto-encryption-mode: t
>    auto-compression-mode: t
>    line-number-mode: t
>    transient-mark-mode: t
>
> Recent input:
> <up>  <up>  <down>  S h e SPC w a s SPC l i v i n g SPC
> w i t h SPC h u s n<backspace>  b a n d , SPC s t e
> p<backspace>  <backspace>  <backspace>  <backspace>  s
> o n SPC b y SPC f u<backspace>  i r t s SPC m a r r
> i a g e SPC<backspace>  , SPC a n d SPC 4 SPC s o n
> s SPC b y SPC s e c o n d SPC<down-mouse-1>  <mouse-1>
> C-t<down>  i n SPC F u n t i n g d o n SPC i n SPC
> 1 9 0 1<return>  <down-mouse-1>  <mouse-1>  , SPC o r
> SPC a n y SPC f u r t h e r SPC s u g g e s t i o n
> s SPC o r C-\ C-g C-e SPC C-d<down-mouse-1>  <mouse-1>
> SPC ( i e SPC b 1 8 7 3 )<down-mouse-1>  <mouse-1>
> ( o f SPC SPC 7<backspace>  <backspace>  7 ) SPC M-q
> C-x C-s C-x k<return>  d n n d SPC n s y C-x C-f S
> O u r<tab>  <backspace>  <backspace>  <backspace>  o u
> r c e<tab>  c s p o u<backspace>  <backspace>  <backspace>
> o<tab>  5 / E n g i<tab>  e n t<tab>  c<return>  C-s
> c p u p r c C-x C-f<backspace>  <backspace>  <backspace>
> <backspace>  <backspace>  <backspace>  <backspace>  O p
> c o<tab>  <return>  M-x g r e p<return>  c p u p r c
> SPC * . c<return>  M-c M-x e m a c s - r<tab>  <backspace>
> <backspace>  <backspace>  <backspace>  <backspace>  <backspace>
> <backspace>  r e p o<tab>  i<backspace>  r t<tab>
> <return>
>
> Recent messages:
> Invalid face reference: my-trailing-space-face
> Invalid face reference: my-tab-face
> Loading vc-cvs...done
> Mark saved where search started
> Loading dired-add...done
> Invalid face reference: my-trailing-space-face [2 times]
> call-interactively: Buffer is read-only: #<buffer Opcodes>Invalid face reference: my-trailing-space-face
> Invalid face reference: my-trailing-space-face [3 times]
> Making completion list...
> Invalid face reference: my-trailing-space-face
>
> Load-path shadows:
> /home/jpff/GNU_21/local-lisp/scroll-lock hides /home/jpff/GNU_21/emacs/trunk/lisp/scroll-lock
> /home/jpff/GNU_21/local-lisp/t-mouse hides /home/jpff/GNU_21/emacs/trunk/lisp/t-mouse
> /home/jpff/GNU_21/local-lisp/ruler-mode hides /home/jpff/GNU_21/emacs/trunk/lisp/ruler-mode
> /home/jpff/GNU_21/local-lisp/emerge hides /home/jpff/GNU_21/emacs/trunk/lisp/vc/emerge
> /home/jpff/GNU_21/local-lisp/url-gw hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-gw
> /home/jpff/GNU_21/local-lisp/url-file hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-file
> /home/jpff/GNU_21/local-lisp/url-cid hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-cid
> /home/jpff/GNU_21/local-lisp/url-parse hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-parse
> /home/jpff/GNU_21/local-lisp/url-cache hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-cache
> /home/jpff/GNU_21/local-lisp/url-http hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-http
> /home/jpff/GNU_21/local-lisp/url-misc hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-misc
> /home/jpff/GNU_21/local-lisp/url hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url
> /home/jpff/GNU_21/local-lisp/url-auth hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-auth
> /home/jpff/GNU_21/local-lisp/url-ldap hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-ldap
> /home/jpff/GNU_21/local-lisp/url-news hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-news
> /home/jpff/GNU_21/local-lisp/url-vars hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-vars
> /home/jpff/GNU_21/local-lisp/url-cookie hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-cookie
> /home/jpff/GNU_21/local-lisp/url-nfs hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-nfs
> /home/jpff/GNU_21/local-lisp/url-ns hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-ns
> /home/jpff/GNU_21/local-lisp/url-irc hides /home/jpff/GNU_21/emacs/trunk/lisp/url/url-irc
> /home/jpff/GNU_21/local-lisp/remember hides /home/jpff/GNU_21/emacs/trunk/lisp/textmodes/remember
> /home/jpff/GNU_21/local-lisp/socks hides /home/jpff/GNU_21/emacs/trunk/lisp/net/socks
>
> Features:
> (shadow emacsbug help-mode grep compile dired multi-isearch parse-time
> vc-cvs imenu cc-mode cc-fonts cc-menus cc-cmds cc-styles cc-align
> cc-engine cc-vars cc-defs ispell feedmail newcomment mailabbrev
> mailalias rmailout rmailkwd etach sendmail mime-compose
> mail-alias-menu mailcrypt mail-extr comint ring rmail mail-utils eldoc
> package image-file logger crypt crypt++ crypt+pgp-pub paren cal-julian
> uniquify advice help-fns advice-preload view cal-china cal-bahai
> cal-islam cal-hebrew lunar solar cal-dst appt diary-lib diary-loaddefs
> holidays hol-loaddefs regexp-opt cal-menu easymenu calendar
> cal-loaddefs time tooltip ediff-hook vc-hooks lisp-float-type mwheel
> x-win x-dnd tool-bar dnd fontset image fringe lisp-mode register page
> menu-bar rfn-eshadow timer select scroll-bar mldrag mouse jit-lock
> font-lock syntax facemenu font-core frame cham georgian utf-8-lang
> misc-lang vietnamese tibetan thai tai-viet lao korean japanese hebrew
> greek romanian slovak czech european ethiopic indian cyrillic chinese
> case-table epa-hook jka-cmpr-hook help simple abbrev loaddefs button
> minibuffer faces cus-face files text-properties overlay md5 base64
> format env code-pages mule custom widget hashtable-print-readable
> backquote make-network-process dynamic-setting font-render-setting gtk
> x-toolkit x multi-tty emacs)
>
> ==John ffitch
>
>

bug#6535: 24.0.50; grep seems not to work

[john ffitch]

I run tcsh as I have done for ~25yrs.  I have never got on with
bash/sh

No terminal stuff in .login or .cshrc, only environment variables and
aliases
  If it matters this is OpenSuSE 11.2

Emacs is started from a fvwm menu, not a terminal
/home/jpff/GNU_21/emacs/trunk/src/emacs -lsp 2 -geometry 84x46+64+10 -fn "-etl-fixed-medium-r-normal--16-160-72-72-c-80-iso8859-1"


==John ffitch

bug#6535: 24.0.50; grep seems not to work

[Jan Djärv]

And how about this:

>
> How does it look if you put
>
>   TERM=vt100 grep -nH -e cp cpuprc *.c
>
> as the grep command?

	Jan D.


john ffitch skrev 2010-06-29 12.10:
> I run tcsh as I have done for ~25yrs.  I have never got on with
> bash/sh
>
> No terminal stuff in .login or .cshrc, only environment variables and
> aliases
>    If it matters this is OpenSuSE 11.2
>
> Emacs is started from a fvwm menu, not a terminal
> /home/jpff/GNU_21/emacs/trunk/src/emacs -lsp 2 -geometry 84x46+64+10 -fn "-etl-fixed-medium-r-normal--16-160-72-72-c-80-iso8859-1"
>
>
> ==John ffitch

bug#6535: 24.0.50; grep seems not to work

[root]

The real problem is that in lisp/grep.el there is
(defun grep-process-setup ()
...
     ;; Any TERM except "dumb" allows GNU grep to use `--color=auto'
     (setenv "TERM" "emacs-grep")
     (setenv "GREP_OPTIONS"
             (concat (getenv "GREP_OPTIONS")
                     " --color=" (if (eq grep-highlight-matches 'always)
                                     "always" "auto")))
...

but there is no terminal type emacs-grep so the process call fails to 
start before it gets to call /bin/grep or set TERM=vt100

So, what is this emacs-grep terminal type and how did it change from when 
it worked.

==John ff

bug#6535: 24.0.50; grep seems not to work

[Jan Djärv]

root skrev 2010-06-29 13.03:
> The real problem is that in lisp/grep.el there is
> (defun grep-process-setup ()
> ...
> ;; Any TERM except "dumb" allows GNU grep to use `--color=auto'
> (setenv "TERM" "emacs-grep")
> (setenv "GREP_OPTIONS"
> (concat (getenv "GREP_OPTIONS")
> " --color=" (if (eq grep-highlight-matches 'always)
> "always" "auto")))
> ...
>
> but there is no terminal type emacs-grep so the process call fails to start
> before it gets to call /bin/grep or set TERM=vt100
>
> So, what is this emacs-grep terminal type and how did it change from when it
> worked.
>

emacs-grep was introduced in late 2007:

revno: 82277
committer: Juri Linkov <juri@jurta.org>
timestamp: Fri 2007-11-23 00:32:05 +0000
message:
   (grep-process-setup): Set envvar "TERM" to "emacs-grep".
   Set envvar "GREP_OPTIONS" to "--color=auto" instead of "--color=always".


My guess is that Suse changed if this worked for you on an Emacs newer than 
this change.

	Jan D.

bug#6535: 24.0.50; grep seems not to work

[Juri Linkov]

> emacs-grep was introduced in late 2007:
>
> revno: 82277
> committer: Juri Linkov <juri@jurta.org>
> timestamp: Fri 2007-11-23 00:32:05 +0000
> message:
>   (grep-process-setup): Set envvar "TERM" to "emacs-grep".
>   Set envvar "GREP_OPTIONS" to "--color=auto" instead of "--color=always".

This was a result of the following thread:

http://thread.gmane.org/gmane.emacs.devel/83316

So we could either set "TERM" to "emacs" (if it helps)
or create a terminfo file that describes "emacs-grep".

-- 
Juri Linkov
http://www.jurta.org/emacs/

bug#6535: 24.0.50; grep seems not to work

[Jan Djärv]

Juri Linkov skrev 2010-06-29 18.57:
>> emacs-grep was introduced in late 2007:
>>
>> revno: 82277
>> committer: Juri Linkov<juri@jurta.org>
>> timestamp: Fri 2007-11-23 00:32:05 +0000
>> message:
>>    (grep-process-setup): Set envvar "TERM" to "emacs-grep".
>>    Set envvar "GREP_OPTIONS" to "--color=auto" instead of "--color=always".
>
> This was a result of the following thread:
>
> http://thread.gmane.org/gmane.emacs.devel/83316
>
> So we could either set "TERM" to "emacs" (if it helps)
> or create a terminfo file that describes "emacs-grep".
>

"emacs" is also unknown in Suse, so it would not matter.  No, this is a Suse 
matter, they should not put in terminal stuff in their /etc/csh.cshrc.

	Jan D.

bug#6535: 24.0.50; grep seems not to work

[john ffitch]

This is beyond by experience
> So we could either set "TERM" to "emacs" (if it helps)
> or create a terminfo file that describes "emacs-grep".

Set which TERM to emacs?  What is a terminfo file?  Why did this start
being a problem in the last month?

==John ffitch

bug#6535: 24.0.50; grep seems not to work

[Juri Linkov]

> Set which TERM to emacs?  What is a terminfo file?  Why did this start
> being a problem in the last month?

Jan said that Suse should not put in terminal stuff in their /etc/csh.cshrc.
So please try a fix that Jan posted in another message.

-- 
Juri Linkov
http://www.jurta.org/emacs/

bug#6535: 24.0.50; grep seems not to work

[Jan Djärv]

Juri Linkov skrev 2010-06-30 10.16:
>> Set which TERM to emacs?  What is a terminfo file?  Why did this start
>> being a problem in the last month?
>
> Jan said that Suse should not put in terminal stuff in their /etc/csh.cshrc.
> So please try a fix that Jan posted in another message.
>

Just to clarify, the fix is to customize shell-file-name to /bin/sh.

	Jan D.

bug#6535: 24.0.50; grep seems not to work

[Jan Djärv]

john ffitch skrev 2010-06-29 12.10:
> I run tcsh as I have done for ~25yrs.  I have never got on with
> bash/sh
>
> No terminal stuff in .login or .cshrc, only environment variables and
> aliases
>    If it matters this is OpenSuSE 11.2
>
> Emacs is started from a fvwm menu, not a terminal
> /home/jpff/GNU_21/emacs/trunk/src/emacs -lsp 2 -geometry 84x46+64+10 -fn "-etl-fixed-medium-r-normal--16-160-72-72-c-80-iso8859-1"
>

Ok, it is probably tsch.  Check if you have this in /etc/csh.cshrc, I have it 
on Suse 11.2:

#
# Avoid trouble with Emacs shell mode
#
if ($?EMACS) then
   setenv LS_OPTIONS '-N --color=none -T 0';
   path tset -I -Q
   path stty cooked pass8 dec nl -echo
# if ($?tcsh) unset edit
endif


You can force Emacs to use sh or bash if you customize shell-file-name.  I 
don't know if Emacs should be able to handle this.

	Jan D.

bug#6535: 24.0.50; grep seems not to work

[Lars Magne Ingebrigtsen]

Jan Djärv <jan.h.d@swipnet.se> writes:

> Ok, it is probably tsch.  Check if you have this in /etc/csh.cshrc, I
> have it on Suse 11.2:
>
> #
> # Avoid trouble with Emacs shell mode
> #
> if ($?EMACS) then
>   setenv LS_OPTIONS '-N --color=none -T 0';
>   path tset -I -Q
>   path stty cooked pass8 dec nl -echo
> # if ($?tcsh) unset edit
> endif
>
> You can force Emacs to use sh or bash if you customize
> shell-file-name.  I don't know if Emacs should be able to handle this.

This doesn't seem to be an Emacs bug?

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

bug#6535: 24.0.50; grep seems not to work

[john ffitch]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

 Lars> Jan Djärv <jan.h.d@swipnet.se> writes:
 >> Ok, it is probably tsch.  Check if you have this in /etc/csh.cshrc, I
 >> have it on Suse 11.2:
 >> 
 >> #
 >> # Avoid trouble with Emacs shell mode
 >> #
 >> if ($?EMACS) then
 >> setenv LS_OPTIONS '-N --color=none -T 0';
 >> path tset -I -Q
 >> path stty cooked pass8 dec nl -echo
 >> # if ($?tcsh) unset edit
 >> endif
 >> 
 >> You can force Emacs to use sh or bash if you customize
 >> shell-file-name.  I don't know if Emacs should be able to handle this.

 Lars> This doesn't seem to be an Emacs bug?

Seems so.  I have not had any problems since fiddling with the tcsh
configuration.

==John ffitch

bug#6535: 24.0.50; grep seems not to work

[Lars Magne Ingebrigtsen]

john ffitch <jpff@codemist.co.uk> writes:

> Seems so.  I have not had any problems since fiddling with the tcsh
> configuration.

Ok; I'll close the bug report, then.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/