comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: IDLWAVE fontlock / fontify weirdness in Xemacs
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: IDLWAVE fontlock / fontify weirdness in Xemacs [message #22307 is a reply to message #22302] Thu, 02 November 2000 00:52 Go to previous message
Martin Schultz is currently offline  Martin Schultz
Messages: 515
Registered: August 1997
Senior Member
jrigler@Colorado.EDU wrote:
>
> I have Xemacs 21.1.12 (default with RH Linux 7.0 Respin), and updated
> all of my packages to the most recent versions as of 10/31/00 (which
> means IDLWAVE 1.22...or a modified version 4.5 I assume).
>
> The problem I'm experiencing is in the fontification. For whatever
> reason, all of a suddent every time I start a new line, or even modify
> an old line for that matter, it all turns green (the color for
> strings). this only really happens after a certain block in the code.
> The possibly offending code (which works, and I see no syntax problems
> with it) follows. Any ideas?
>
> ; Convert MJD to a YYYYMMDD (see - http://bowie.gsfc.nasa.gov/time/)
> caldat,date_beg+2400000.5,month_beg,day_beg,year_beg
> caldat,date_end+2400000.5,month_end,day_end,year_end
>
> month_beg=string(month_beg,format='(i2.2)')
> day_beg=string(day_beg,format='(i2.2)')
> year_beg=string(year_beg,format='(i4.4)')
>
> To clarify a little more, what happens is that I can type anything
> before the line with the first "format" statement, and it works
> perfectly. If I add, or modify anything after the "format" statement,
> the whole line becomes green, as if IDLWAVE thought it were a string.
>
> I really don't like the IDLDE, so I sure hope there is a solution to
> this.
>
> Thanks,
>
> Josh
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.


yes, I have seen a similar thing already in earlier versions of
idlwave (presumably 3.12). I never succeeded in tracking down the part
of the code that caused it but haven't tried to hard either.
Interestingly, it sometimes appeared to work better once I exited
xemacs and restarted again. Then again: sometimes this didn't help
either.

Cheers,
Martin

PS: I know, this was a terrible bug report ;-) But perhaps it helps to
know that it occured in earlier versions...

--
[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[ [[[[[[[
[[ Dr. Martin Schultz Max-Planck-Institut fuer Meteorologie [[
[[ Bundesstr. 55, 20146 Hamburg [[
[[ phone: +49 40 41173-308 [[
[[ fax: +49 40 41173-298 [[
[[ martin.schultz@dkrz.de [[
[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[ [[[[[[[
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: IDL 5.4. Neato. NOT.
Next Topic: Re: Old Timers ??

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 18:03:58 PDT 2025

Total time taken to generate the page: 0.00449 seconds