At 08:14 AM 10/25/00 +0100, you wrote:
>Is it possible in emacs-lisp to set up a kind of threading (perhaps even
>with synchronization) by implementing a library that manages the sharing of
>emacs' single thread?
>I realise that this would be a huge task and am not suggesting it be done
>even - I ask as a someone just starting to become interested in emacs-lisp,
>proughing through the first pages of the O'reilly book
>and finding it a fascinating language - like looking at a fractal.
>
Hi Peter,
Actually, it might be possible to perform parsing in the idle time between
commands. I think this would require changes to semantic such that it could
parse incrementally. Semantic could set up a post-command-idle-hook to
perform parse increments between commands. Commands that modify the buffer
would reset the parser. This would give the effect of continuous background
parsing of the buffer.
- Paul
>
>-----Original Message-----
>From: Paul Kinnucan [mailto:[EMAIL PROTECTED]]
>Sent: 24 October 2000 11:31 PM
>To: Jeff Jensen; [EMAIL PROTECTED]
>Subject: RE: emacs threshing after JDE install
>
>
>At 09:24 PM 10/24/00 -0500, Jeff Jensen wrote:
>>I like the feature because it makes the other buffer/code/class dependent
>>features ready for immediate use. Previously, I tried to use a feature and
>>then had to manually refresh things for it to work correctly.
>>
>>My biggest complaint about it is the frequency. I would like the default
>>interval to be closer to 60 seconds or more instead of 10.
>>
>
>I have increased the default to 3 minutes in the next release.
>
>>Ideally, I would like this to happen "continually" in a background thread
>so
>>it is not intrusive. I have no idea of the feasibility of this in Emacs...
>>
>
>Emacs is single-threaded. AFAIK, there are no plans to make it
>multithreaded.
>
>- Paul
>
>
>>
>>-----Original Message-----
>>From: [EMAIL PROTECTED]
>>[mailto:[EMAIL PROTECTED]]On
>>Behalf Of [EMAIL PROTECTED]
>>Sent: Tuesday, October 24, 2000 5:06 PM
>>To: [EMAIL PROTECTED]
>>Subject: RE: emacs threshing after JDE install
>>
>>
>>Actually, I immediately found this feature to be too intrusive and
>>distracting and was pretty happy to find out it could easily be
>>disabled. I'm wondering if a better choice would be to have it turned
>>off by default - depending on the general consensus, of course. To each
>>his own, as they say. Any other opinions on this subject?
>>
>>Chuck Irvine
>>Sprint / SETS Technical Architecture
>>
>>-----Original Message-----
>>From: paulk [mailto:[EMAIL PROTECTED]]
>>Sent: Tuesday, October 24, 2000 4:52 PM
>>To: Mark.Donaghue; jde
>>Cc: paulk
>>Subject: Re: emacs threshing after JDE install
>>
>>
>>At 05:42 PM 10/24/00 -0400, you wrote:
>>>Dear Paul,
>>>
>>>I was overjoyed to discover you package; it will be a reall windfall.
>>I've
>>>got it up and running. Now that's its up, though, theres a problem.
>>After
>>>every few keystrokes it appears to be doing some kind of an autosave.
>>>(along the bottom I see this:
>>>
>>>"myFile.java <2> [###########################] ....done."
>>>
>>>I've checked the FAQ, and it doesn't seem to be listed there. The
>>System is
>>>sparc-sun-solaris2.7, x toolkit; GNU emacs 20.4.1.
>>>
>>>Please help! It's driving me crazy.
>>>
>>
>>See
>>
>>jde-auto-parse-buffer-interval
>>de-auto-parse-buffer-timer
>>jde-auto-parse-enable
>>
>>- Paul
>>
>>------------------------------------------------------------
>>HOW TO ASK FOR TECH SUPPORT
>>
>>When requesting technical support, please generate a problem report,
>>using
>>the JDE->Help->Submit Problem Report command, and submit this report
>>along
>>with your help request. Please do this even if you think most of the
>>report
>>is irrelevant. If you knew what were relevant, you wouldn't need my
>>help.
>>
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>JDE website: http://sunsite.auc.dk/jde/
>>
>>JDE mailing list archive:
>>http://www.mail-archive.com/[email protected]/maillist.html
>>
>>
>>
>>
>>
>
>
>
>NOTICE AND DISCLAIMER:
>This email (including attachments) is confidential. If you have received
>this email in error please notify the sender immediately and delete this
>email from your system without copying or disseminating it or placing any
>reliance upon its contents. We cannot accept liability for any breaches of
>confidence arising through use of email. Any opinions expressed in this
>email (including attachments) are those of the author and do not necessarily
>reflect our opinions. We will not accept responsibility for any commitments
>made by our employees outside the scope of our business. We do not warrant
>the accuracy or completeness of such information.
>
>
>
