JDEE

Have you tried to customize the face?  If not, try that and let me  
know what happens.



On Apr 25, 2011, at 7:36 PM, <jahlborn@...> <jahlborn@... 
 > wrote:

> Hey,
> Just wondering if anyone else has experienced erratic font-lock  
> behavior.  When I run jdee in emacs 23 (and the trunk of jde), the  
> font-lock-keywords seems to bounce back and forth between 2  
> different sets of values.  When I first open up a java file, I’ll  
> get a certain font-lock behavior.  If I refresh the buffer, often  
> times (not always), I’ll be different font-lock behavior.  When I  
> dump the value of the font-lock-keywords, I actually see 2 different  
> values between the first buffer load and the refresh.  After the  
> first refresh, the font locking seems to settle down, but not always  
> to the ”correct” values.  I don’t know if this has something to do  
> with my own setup or what, so I was wondering if anyone else saw  
> similar behavior.  To me, the effects are most noticeable in the  
> import statements, as the package names are fontified in font-lock- 
> constant face sometimes (incorrect), and jde-java-font-lock-package  
> face other times (the “correct” face).
> Thanks,
> -james
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd_______________________________________________
> jdee-users mailing list
> jdee-users@...
> https://lists.sourceforge.net/lists/listinfo/jdee-users

I'm not sure I understand what you are asking.  I've customized all my
faces.  The issue isn't the face color, it's that the wrong faces are being
applied, seemingly due to the fact that the value of font-lock-keyworks
changes over the lifetime of the buffer.

 

 

From: Paul Landes [mailto:landes@...] 
Sent: Tuesday, April 26, 2011 9:58 PM
To: jahlborn@...
Cc: jdee-users@...
Subject: Re: [jdee-users] erratic font-lock behavior (emacs 23)

 

Have you tried to customize the face?  If not, try that and let me know what
happens.

 

 

 

On Apr 25, 2011, at 7:36 PM, <jahlborn@...>
<jahlborn@...> wrote:





Hey,

Just wondering if anyone else has experienced erratic font-lock behavior.
When I run jdee in emacs 23 (and the trunk of jde), the font-lock-keywords
seems to bounce back and forth between 2 different sets of values.  When I
first open up a java file, I'll get a certain font-lock behavior.  If I
refresh the buffer, often times (not always), I'll be different font-lock
behavior.  When I dump the value of the font-lock-keywords, I actually see 2
different values between the first buffer load and the refresh.  After the
first refresh, the font locking seems to settle down, but not always to the
"correct" values.  I don't know if this has something to do with my own
setup or what, so I was wondering if anyone else saw similar behavior.  To
me, the effects are most noticeable in the import statements, as the package
names are fontified in font-lock-constant face sometimes (incorrect), and
jde-java-font-lock-package face other times (the "correct" face).

Thanks,

-james

----------------------------------------------------------------------------
--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd__________________________________________
_____
jdee-users mailing list
jdee-users@...
https://lists.sourceforge.net/lists/listinfo/jdee-users

On Tue, Apr 26, 2011 at 11:12 PM,  <jahlborn@...> wrote:
> I’m not sure I understand what you are asking.  I’ve customized all my
> faces.  The issue isn’t the face color, it’s that the wrong faces are being
> applied, seemingly due to the fact that the value of font-lock-keyworks
> changes over the lifetime of the buffer.

Could it be that you are accidentally sometimes in java-mode, and
sometimes in jde-mode?  Could you C-h m and see which mode is active
when each set of faces is applied? I've tested and seen that java-mode
and jde-mode do have different sets of faces.

-- 
Jason F. McBrayer
http://jfm.carcosa.net/

All modes and minor modes are the same.

-----Original Message-----
From: jfmcbrayer@... [mailto:jfmcbrayer@...] On Behalf Of Jason
McBrayer
Sent: Wednesday, April 27, 2011 10:07 AM
To: jahlborn@...
Cc: jdee-users@...
Subject: Re: [jdee-users] erratic font-lock behavior (emacs 23)

On Tue, Apr 26, 2011 at 11:12 PM,  <jahlborn@...> wrote:
> I’m not sure I understand what you are asking.  I’ve customized all my 
> faces.  The issue isn’t the face color, it’s that the wrong faces are 
> being applied, seemingly due to the fact that the value of 
> font-lock-keyworks changes over the lifetime of the buffer.

Could it be that you are accidentally sometimes in java-mode, and sometimes
in jde-mode?  Could you C-h m and see which mode is active when each set of
faces is applied? I've tested and seen that java-mode and jde-mode do have
different sets of faces.

--
Jason F. McBrayer
http://jfm.carcosa.net/

A little more futzing led me to another interesting observation: it seems to
be related to file size.  A quick test on a few different files only showed
the coloring issues on files over ~700 lines.  Testing with a big file and a
small file, it seems that the _initial value for font-lock-keywords depends
on the file size_!  When I load a small file, the font-lock-keywords
variable get init-ed to one value (let's call that value "A") in that buffer
and the coloring is correct.  No amount of reverting of the buffer changes
the coloring or the value.  But, when I open a large file, the initial
coloring is wrong, and the value of font-lock-keywords is _different_ (let's
call that value "B").  when I revert the large file, then the coloring is
correct, and the font-lock-keywords is now set to "A" (and the coloring
seems to stay correct through subsequent buffer reverts).

So, anyone have an idea when the font-lock-keywords variable may get setup
differently (at least initially) depending on buffer size?

-----Original Message-----
From: jfmcbrayer@... [mailto:jfmcbrayer@...] On Behalf Of Jason
McBrayer
Sent: Wednesday, April 27, 2011 10:07 AM
To: jahlborn@...
Cc: jdee-users@...
Subject: Re: [jdee-users] erratic font-lock behavior (emacs 23)

On Tue, Apr 26, 2011 at 11:12 PM,  <jahlborn@...> wrote:
> I’m not sure I understand what you are asking.  I’ve customized all my
> faces.  The issue isn’t the face color, it’s that the wrong faces are
being
> applied, seemingly due to the fact that the value of font-lock-keyworks
> changes over the lifetime of the buffer.

Could it be that you are accidentally sometimes in java-mode, and
sometimes in jde-mode?  Could you C-h m and see which mode is active
when each set of faces is applied? I've tested and seen that java-mode
and jde-mode do have different sets of faces.

-- 
Jason F. McBrayer
http://jfm.carcosa.net/

Does this happen in other modes?  It sounds like an issue more related  
to font-lock.

Do you have beanshell running while this is happening?  If so, kill  
the *JDEE bsh* buffer.


On Apr 27, 2011, at 10:48 AM, <jahlborn@...> <jahlborn@... 
 > wrote:

> A little more futzing led me to another interesting observation: it  
> seems to
> be related to file size.  A quick test on a few different files only  
> showed
> the coloring issues on files over ~700 lines.  Testing with a big  
> file and a
> small file, it seems that the _initial value for font-lock-keywords  
> depends
> on the file size_!  When I load a small file, the font-lock-keywords
> variable get init-ed to one value (let's call that value "A") in  
> that buffer
> and the coloring is correct.  No amount of reverting of the buffer  
> changes
> the coloring or the value.  But, when I open a large file, the initial
> coloring is wrong, and the value of font-lock-keywords is  
> _different_ (let's
> call that value "B").  when I revert the large file, then the  
> coloring is
> correct, and the font-lock-keywords is now set to "A" (and the  
> coloring
> seems to stay correct through subsequent buffer reverts).
>
> So, anyone have an idea when the font-lock-keywords variable may get  
> setup
> differently (at least initially) depending on buffer size?
>
> -----Original Message-----
> From: jfmcbrayer@... [mailto:jfmcbrayer@...] On Behalf  
> Of Jason
> McBrayer
> Sent: Wednesday, April 27, 2011 10:07 AM
> To: jahlborn@...
> Cc: jdee-users@...
> Subject: Re: [jdee-users] erratic font-lock behavior (emacs 23)
>
> On Tue, Apr 26, 2011 at 11:12 PM,  <jahlborn@...>  
> wrote:
>> I’m not sure I understand what you are asking.  I’ve customized all  
>> my
>> faces.  The issue isn’t the face color, it’s that the wrong faces are
> being
>> applied, seemingly due to the fact that the value of font-lock- 
>> keyworks
>> changes over the lifetime of the buffer.
>
> Could it be that you are accidentally sometimes in java-mode, and
> sometimes in jde-mode?  Could you C-h m and see which mode is active
> when each set of faces is applied? I've tested and seen that java-mode
> and jde-mode do have different sets of faces.
>
> -- 
> Jason F. McBrayer
> http://jfm.carcosa.net/
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> jdee-users mailing list
> jdee-users@...
> https://lists.sourceforge.net/lists/listinfo/jdee-users

This is in.  Will you please update your snapshot and test?

BTW--The version numbers you have here are a little off so I had to do  
this manually.  Please make sure what's in the repo is what you have.

Thanks.


On Apr 24, 2011, at 2:35 AM, Vincent Belaïche wrote:

> Hello all,
>
> I came accross a bug on the way jde-compile-enable-kill-buffer is
> tested. I am proposing the following patch and changelog
>
> ----------------- Changelog  
> -------------------------------------------
> 2011-04-24  Vincent Belaïche  <vincentb1@...>
>
> 	* jde-compile.el (jde-compile-finish-kill-buffer): Test
> 	jde-compile-enable-kill-buffer as non-nil only when it is not a
> 	number to be consistent with its docstring.
> -----------------------------------------------------------------------
>
> VBR,
>   Vincent.
>
> PS: FYI I had to do an update of SVN to be able to get the latest  
> one. I
> am using MSWindows CollabNet, my previous version was 1.6.11, and the
> latest one is 1.6.16.
>
> Index: jde-compile.el
>
> ===================================================================
>
> --- jde-compile.el	(revision 247)
>
> +++ jde-compile.el	(working copy)
>
> @@ -237,9 +237,9 @@
>
>     (if (null (or (string-match ".*exited abnormally.*" msg)
> 		  (string-match ".*BUILD FAILED.*" (buffer-string))))
> 	;;no errors, make the compilation window go away in a few seconds
> -	(if (or (and (numberp jde-compile-enable-kill-buffer)
> -		     (not (minusp jde-compile-enable-kill-buffer)))
> -		jde-compile-enable-kill-buffer)
> +	(if (if (numberp jde-compile-enable-kill-buffer)
> +		(not (minusp jde-compile-enable-kill-buffer))
> +		 jde-compile-enable-kill-buffer)
> 	    (lexical-let ((compile-buffer buf))
> 	      (run-at-time
> 	       (format "%d sec" (if (numberp jde-compile-enable-kill-buffer)
> @@ -611,7 +611,7 @@
>
>
> (defcustom jde-compile-enable-kill-buffer -1
>   "* Time in seconds to display the compilation buffer before
> -'jde-compile-finish-kill-buffer will kill the compilation buffer.
> +`jde-compile-finish-kill-buffer' will kill the compilation buffer.
>
> If less than zero (or nil), do not kill the compilation buffer.
> If t (or other non-nil non-number) then kill in 2 secs."
> ------------------------------------------------------------------------------
> Fulfilling the Lean Software Promise
> Lean software platforms are now widely adopted and the benefits have  
> been
> demonstrated beyond question. Learn why your peers are replacing JEE
> containers with lightweight application servers - and what you can  
> gain
> from the move. http://p.sf.net/sfu/vmware-sfemails_______________________________________________
> jdee-users mailing list
> jdee-users@...
> https://lists.sourceforge.net/lists/listinfo/jdee-users

Hi Paul,

Thank you for taking in my patch. I have just made the download and tested it, everything is OK.

  Vincent.

> CC: jdee-users@...
> From: landes@...
> To: vincent.b.1@...
> Subject: Re: [jdee-users] Bug on testing jde-compile-enable-kill-buffer
> Date: Tue, 26 Apr 2011 21:15:08 -0500
> 
> This is in.  Will you please update your snapshot and test?
> 
> BTW--The version numbers you have here are a little off so I had to do  
> this manually.  Please make sure what's in the repo is what you have.
> 
> Thanks.
> 
> 
> On Apr 24, 2011, at 2:35 AM, Vincent Belaïche wrote:
> 
> > Hello all,
> >
> > I came accross a bug on the way jde-compile-enable-kill-buffer is
> > tested. I am proposing the following patch and changelog
> >
> > ----------------- Changelog  
> > -------------------------------------------
> > 2011-04-24  Vincent Belaïche  <vincentb1@...>
> >
> > 	* jde-compile.el (jde-compile-finish-kill-buffer): Test
> > 	jde-compile-enable-kill-buffer as non-nil only when it is not a
> > 	number to be consistent with its docstring.
> > -----------------------------------------------------------------------
> >
> > VBR,
> >   Vincent.
> >
> > PS: FYI I had to do an update of SVN to be able to get the latest  
> > one. I
> > am using MSWindows CollabNet, my previous version was 1.6.11, and the
> > latest one is 1.6.16.
> >
> > Index: jde-compile.el
> >
> > ===================================================================
> >
> > --- jde-compile.el	(revision 247)
> >
> > +++ jde-compile.el	(working copy)
> >
> > @@ -237,9 +237,9 @@
> >
> >     (if (null (or (string-match ".*exited abnormally.*" msg)
> > 		  (string-match ".*BUILD FAILED.*" (buffer-string))))
> > 	;;no errors, make the compilation window go away in a few seconds
> > -	(if (or (and (numberp jde-compile-enable-kill-buffer)
> > -		     (not (minusp jde-compile-enable-kill-buffer)))
> > -		jde-compile-enable-kill-buffer)
> > +	(if (if (numberp jde-compile-enable-kill-buffer)
> > +		(not (minusp jde-compile-enable-kill-buffer))
> > +		 jde-compile-enable-kill-buffer)
> > 	    (lexical-let ((compile-buffer buf))
> > 	      (run-at-time
> > 	       (format "%d sec" (if (numberp jde-compile-enable-kill-buffer)
> > @@ -611,7 +611,7 @@
> >
> >
> > (defcustom jde-compile-enable-kill-buffer -1
> >   "* Time in seconds to display the compilation buffer before
> > -'jde-compile-finish-kill-buffer will kill the compilation buffer.
> > +`jde-compile-finish-kill-buffer' will kill the compilation buffer.
> >
> > If less than zero (or nil), do not kill the compilation buffer.
> > If t (or other non-nil non-number) then kill in 2 secs."
> > ------------------------------------------------------------------------------
> > Fulfilling the Lean Software Promise
> > Lean software platforms are now widely adopted and the benefits have  
> > been
> > demonstrated beyond question. Learn why your peers are replacing JEE
> > containers with lightweight application servers - and what you can  
> > gain
> > from the move. http://p.sf.net/sfu/vmware-sfemails_______________________________________________
> > jdee-users mailing list
> > jdee-users@...
> > https://lists.sourceforge.net/lists/listinfo/jdee-users
>