non selected windows code borked

non selected windows code borked

[stark]

This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.

In GNU Emacs 21.4.1 (i486-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2006-05-14 on trouble, modified by Debian
configured using `configure '--build=i486-linux-gnu' '--host=i486-linux-gnu' '--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib' '--localstatedir=/var/lib' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes' '--with-x=yes' '--with-x-toolkit=athena' 'CFLAGS=-DDEBIAN -g -O2' 'build_alias=i486-linux-gnu' 'host_alias=i486-linux-gnu''
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
  locale-coding-system: iso-latin-1
  default-enable-multibyte-characters: nil

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:


The logic to detect "non-selected-windows" seems to get it wrong as often as
it gets it right. I'm typing right now with a hollow cursor for example. I
can't tell when it happens, it happens more often than not though.
Occasionally I'm pleasantly surprised to find it isn't happening.


Usually this just means I can't tell which window is active since they all
have hollow cursors. But it gets really painful when something sets
cursor-in-non-selected-windows to nil -- then I'm typing entirely blind.
Incidentally I find it somewhat offensive that some packages set this
variable, shouldn't it be a user choice?

I'm using Xorg from the Debian package version 1:7.0.22. My window manager is
BOG standard twm from the Debian package version 1:1.0.1-4. I can't imagine
what else might relate to this. I'm not even running any GUI programs with a
tendency to grab the mouse, just a couple xterms.





Recent input:
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n 
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n 
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-v C-x o <switch-frame> 
C-v <down-mouse-1> <switch-frame> <mouse-1> C-v <down-mouse-1> 
<mouse-1> c u r s o r - i n - n o n <tab> <return> 
t <return> <switch-frame> C-n C-n C-n <switch-frame> 
<down-mouse-1> <mouse-1> C-n C-n C-n C-p C-l <escape> 
x b u g - e m a c s <return> <M-backspace> <M-backspace> 
e m <backspace> <backspace> r e p o r <tab> <retur
n>

Recent messages:
Saving /home/stark/News/.newsrc.eld...done
Loading etags...done
Making completion list...
Loading view (compiled; note, source file is newer)...done
Starting a new list of tags tables
Loading cc-mode...done
Mark set
Loading apropos...done
End of buffer [2 times]
Loading emacsbug...done

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

Re: non selected windows code borked

[Richard Stallman]

Would you please try installing the development Emacs from 
CVS on savannah.gnu.org, and see if the problem is fixed?

Re: non selected windows code borked

[Gregory Stark]

Richard Stallman <rms@gnu.org> writes:

> Would you please try installing the development Emacs from 
> CVS on savannah.gnu.org, and see if the problem is fixed?

I haven't seen the problem in the latest development version.

(I do some see some other problems like font-lock-mode not working properly
but I assume these are just normal bugs due to using a development version)


-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

Re: non selected windows code borked

[Kevin Rodgers]

Gregory Stark wrote:
> Richard Stallman <rms@gnu.org> writes:
> 
>> Would you please try installing the development Emacs from 
>> CVS on savannah.gnu.org, and see if the problem is fixed?
> 
> I haven't seen the problem in the latest development version.
> 
> (I do some see some other problems like font-lock-mode not working properly
> but I assume these are just normal bugs due to using a development version)

Not at all.  Please report any bugs via M-x report-emacs-bug (on
<menu-bar> <help-menu> <report-emacs-bug>).

-- 
Kevin

Re: non selected windows code borked

[Richard Stallman]

    (I do some see some other problems like font-lock-mode not working properly
    but I assume these are just normal bugs due to using a development version)

Please report each of these bugs.  If you don't report them,
how can we fix them?

Font Lock Mode only highlights strings

[Gregory Stark]

Richard Stallman <rms@gnu.org> writes:

>     (I do some see some other problems like font-lock-mode not working properly
>     but I assume these are just normal bugs due to using a development version)
>
> Please report each of these bugs.  If you don't report them,
> how can we fix them?

Well the problem is that font-lock-mode seems to be hilighting only strings.
Nothing else. No keywords, types, nothing.

I'm in c-mode from cc-mode.el. I have extensive customizations though so it
would be hard to pin down exactly what's causing this.

The only code in my .emacs that seems to relate to font-lock-mode is this
which I do in my c-mode-hook:

 		   (font-lock-mode 1)
		   (set-face-foreground 'font-lock-string-face "cyan")


-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

Re: Font Lock Mode only highlights strings

[Gregory Stark]

Gregory Stark <stark@enterprisedb.com> writes:

> The only code in my .emacs that seems to relate to font-lock-mode is this
> which I do in my c-mode-hook:
>
>  		   (font-lock-mode 1)
> 		   (set-face-foreground 'font-lock-string-face "cyan")

and when I remove that set-face-foreground then *nothing* gets highlighted.

it's as if font-lock-mode isn't actually setting up its faces. It just leaves
them set to the default green on black.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

Re: Font Lock Mode only highlights strings

[martin]

>>>>> Gregory Stark <stark@enterprisedb.com> writes:
 >  Gregory Stark <stark@enterprisedb.com> writes:
 >> The only code in my .emacs that seems to relate to font-lock-mode
 >> is this which I do in my c-mode-hook:
 >> 
 >> (font-lock-mode 1) (set-face-foreground 'font-lock-string-face
 >> "cyan")
 > 
 > and when I remove that set-face-foreground then *nothing* gets
 > highlighted.
 > 
 > it's as if font-lock-mode isn't actually setting up its faces. It
 > just leaves them set to the default green on black.
 > 
 > -- Gregory Stark EnterpriseDB http://www.enterprisedb.com
 > 
 > 
 > 

Hi,

start emacs with the command line options --no-site-file and
-no-init-file and look at your c-sourcecode.

Fontlocking works very well for me with
GNU Emacs 22.0.50.1 (i386-mingw-nt5.0.2195) of 2006-07-31 on DTOP
and
GNU Emacs 23.0.0.1 (i386-mingw-nt5.0.2195) of 2006-07-31 on DTOP

Martin
-- 
parozusa at web dot de

Re: Font Lock Mode only highlights strings

[Richard Stallman]

    Well the problem is that font-lock-mode seems to be hilighting only strings.
    Nothing else. No keywords, types, nothing.

Please report a precise test case that we can try.
Please read the Bugs section in the Emacs manual, which provides
guidelines on how to write a bug report to give us the
necessary information so we can fix the bug.