<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.emacs.cedet">
    <title>gmane.emacs.cedet</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5795"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5794"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5793"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5792"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5791"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5790"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5789"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5788"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5787"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5786"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5785"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5784"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5783"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5781"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5780"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5779"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5778"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5776"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5775"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5774"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5795">
    <title>Re: semantic cache errors (invalid escape charactersyntax)</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5795</link>
    <description>&lt;pre&gt;

Hey, Mitchel:
   I am facing the same problem here, after digging into those caches files that 
you suggested, I couldn't find any escaped characters that were in you case. So 
how did you fix your problem in the end, I didn't quite get it from the 
conversation. Thanks, also, how did you solve this? 

It seems like it never "remembers" things it has already parsed (I have to re-
parse includes each time I open emacs), which makes it a bit sluggish.

I am bothered by this too. Thank you a ton


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Clint Hui</dc:creator>
    <dc:date>2012-05-22T01:16:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5794">
    <title>Re: status of cedet-build.el after the merge ofnewtrunk</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5794</link>
    <description>&lt;pre&gt;
Yes, because 'package' uses 'url' which uses 'auth-source' which uses
'eieio'. :-)


Hmm. I admit I don't really understand what that implies. Does that mean
that CEDET will be compiled using the built-in EIEIO, but later be using
the one from CEDET? While that will probably work since we try to keep
the macros compatible between versions, it's still asking for trouble...


That's great!


Whether you need papers from your employer or not is a difficult
issue. Maybe copyright-clerk&amp;lt; at &amp;gt;fsf.org can help you here.

Since the top-level Makefile does not get merged to Emacs, you could
apply changes there without papers. However, I would strongly advise to
*not* host the resulting ELPA package at the official GNU ELPA
repository, since AFAIK everything there must be fully covered by
papers, and there are many files in CEDET upstream which are not yet in
Emacs. Those files have to be checked first by the maintainers.

Other ELPA repositories should be fine, though.

-David

-------------------------------------------&lt;/pre&gt;</description>
    <dc:creator>David Engster</dc:creator>
    <dc:date>2012-05-13T17:41:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5793">
    <title>Fitting EDE on top of an existing build framework</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5793</link>
    <description>&lt;pre&gt;The company I work for has a high-level build system that's intended to cover multiple underlying build systems (make vs. ant vs whatever).  Let's call it "confoogure".  The confoogure build system deals in terms of packages, defined by Config files.  If your current directory---or any of your parent directories---has a Config file for the "Frobulator" package, you are "in" the "Frobulator" package, and so are your files.  You can do various build tasks by running "confoogure-build" in the top-level package directory: "confoogure-build release", "confoogure-build test", etc.

Right now, I have Emacs set up to do the following when loading a file:

(a) Check whether there is a Config file in a parent directory
(b) If there is, set the compile-command to be "cd ../..; confoogure-build" (where I go up enough directories to reach the Config file).

I would like to get EDE to understand confoogure.  If I can get Emacs to recognize that a given file or directory is managed by confoogure, then I should be able to b&lt;/pre&gt;</description>
    <dc:creator>sand&lt; at &gt;blarg.net</dc:creator>
    <dc:date>2012-05-11T04:20:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5792">
    <title>Problems activating ede minor modes</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5792</link>
    <description>&lt;pre&gt;Hello all,

I am having problems activating EDE minor modes. Both ede-minor-mode and ede-dired-minor-mode. If I add

    (ede-dired-minor-mode 1)

into my dired-mode-hook I get a "Not in DIRED mode" message. I also have a place where I added

    (ede-minor-mode -1)

to another hook and it did not take effect. In both cases if I wrap it in

    (run-at-time "1 sec" nil (lambda () ... ))

it works but this is a horrible hack. I tested it just now using

    GNU Emacs 23.3.1 (i386-pc-solaris2.11, GTK+ Version 2.20.0) of 2011-11-18 on sfebuildb.uk.openindiana.org

but I know I've had the (ede-minor-mode -1) issue on Linux and other builds of emacs as well.

Thanks,

&lt;/pre&gt;</description>
    <dc:creator>Ronald Parker Jr</dc:creator>
    <dc:date>2012-05-10T15:18:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5791">
    <title>Re: status of cedet-build.el after the merge ofnewtrunk</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5791</link>
    <description>&lt;pre&gt;David,

I tinkered with cedet-build.el at first, but we may not need it to
create ELPA package of cedet.  Following is a patch of the top level
makefile.  With this applied if you type

    cd bzr_root_of_cedet_trunk
    make elpa

cedet-20120506.tar and cedet-readme.txt files will be created.
I believe these are valid ELPA packge of cedet although there are some
issues to be sorted out.  The thorny issue has to do with eieio and that
it is one of the packages that cedet-remove-builtin.el tries to remove.
If I start emacs24 with -q option, then (featurep 'eieio) evaluates to
nil.  However after executing list-packages command, (featurep 'eieio)
evalautes to t.  Thus attempting to install cedet package fails with
this error message

    eieio is already loaded.  Removing CEDET now would be unwise.

To get around this I simply removed eieio from
cedet-remove-builtin-package-list list before creating the ELPA package.
I put it back after package-install complets successfully.

I could provide much more details &lt;/pre&gt;</description>
    <dc:creator>Richard Kim</dc:creator>
    <dc:date>2012-05-07T04:17:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5790">
    <title>semanticdb-javap configuration</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5790</link>
    <description>&lt;pre&gt;Hi all,

Is there any documentation on how to configure semanticdb-javap to extract
tags from jars?

For now I have configured Emacs&amp;amp;CEDET so that it auto-completes the tags
from the imported java-files. Now I'm trying to get autocompletion for the
classes from jar's and couldn't find any piece of text describing how to
get this done...

Dmitry
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Cedet-devel mailing list
Cedet-devel&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cedet-devel
&lt;/pre&gt;</description>
    <dc:creator>Дмитрий Бушенко</dc:creator>
    <dc:date>2012-05-04T15:22:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5789">
    <title>Re: Making listing buffers (data-debug and symref) read-only</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5789</link>
    <description>&lt;pre&gt;
I haven't gotten anywhere on pretty much anything in a few weeks as my 
hacking machine is currently in my livingroom as a mythtv experiment.  
Hacking code on the TV is kind of sucky, even if the couch is comfy.  
I'm hoping to remedy this soon, but it may be a couple weeks.

Eric

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Eric Ludlam</dc:creator>
    <dc:date>2012-05-04T11:02:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5788">
    <title>Re: Making listing buffers (data-debug and symref)read-only</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5788</link>
    <description>&lt;pre&gt;
Any progress on this? Once again, the bzr URL is:

  http://bazaar.launchpad.net/~haxney/%2Bjunk/listing-buffers-read-only/

Consider this a friendly, gentle poke :)

--
Daniel M. Hackney

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Daniel Hackney</dc:creator>
    <dc:date>2012-05-04T05:02:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5787">
    <title>New mozrepl backend for Semantic</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5787</link>
    <description>&lt;pre&gt;For you Javascript coders out there this should be fairly interesting. I
added a semanticdb omniscience database using mozrepl, which is a
Firefox extension providing access to a running session. I've written
more about it here, also covering installation and the different
completion solutions that are currently available:

http://www.randomsample.de/dru5/node/147

Cheers,
David

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>David Engster</dc:creator>
    <dc:date>2012-05-03T20:06:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5786">
    <title>Re: Merge of 'newtrunk' branch</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5786</link>
    <description>&lt;pre&gt;[...]

All the semantic-ia functions were meant as examples, showing how to 
write a simple function using the semantic backend to do the heavy 
lifting.  The point being to help folks writing a nice completion ui 
something to try out.

That took a long time though, so enhancements went in making them not so 
simple. ;)


The primary complexity in the semantic-complete function is performance, 
recycling as much data as possible between requests within a particular 
completion edit session.  ie. handling multiple completion requests on a 
single bit of text as you expand it.   Later performance improvements 
have made the simplified versions to be of similar speed, so it doesn't 
have much of a win anymore.


I find the idea of a standard completion interface on multiple backends 
appealing.  That makes the semantic configuration very straight forward.

For example, semantic-ia-complete-symbol could locally bind a 
configuration for, and then call completion-at-point.

Eric

--------------------------------&lt;/pre&gt;</description>
    <dc:creator>Eric M. Ludlam</dc:creator>
    <dc:date>2012-05-02T22:32:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5785">
    <title>Re: Merge of 'newtrunk' branch</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5785</link>
    <description>&lt;pre&gt;
Yes, I would recommend to use

(setq-default ac-sources '(ac-source-semantic-raw))

to really only get Semantic completions. I would also recommend to
choose a longer delay until auto-complete triggers, otherwise it can
easily become quite annoying.

-David

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>David Engster</dc:creator>
    <dc:date>2012-05-02T19:58:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5784">
    <title>Re: Merge of 'newtrunk' branch</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5784</link>
    <description>&lt;pre&gt;Thank you David

I also installed autocomplete and trying to use it together with
Semantic, although maybe I'll need to experiment with semantic-only
backend, etc.

On Wed, May 2, 2012 at 9:49 PM, David Engster &amp;lt;deng&amp;lt; at &amp;gt;randomsample.de&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Alex Ott</dc:creator>
    <dc:date>2012-05-02T19:53:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5783">
    <title>Re: Merge of 'newtrunk' branch</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5783</link>
    <description>&lt;pre&gt;
OK, I've brought the function back with a 'do not merge' notice.

The different completion tools in CEDET are... confusing. We have the
semantic-ia-complete-symbol/menu/tip functions, which (I'm guessing)
predate semantic-complete-analyze-inline, which is configured through
`semantic-complete-inline-analyzer-displayor-class' (phew...). The
semantic-complete package is more powerful but doesn't have that neat
menu-style completion from the semantic-ia package. Instead, it has this
'ghosting' style and tooltips. I guess the semantic-ia-complete
functions should be deprecated some day and moved to semantic-complete?

None of those functions is as streamlined as company-mode or
auto-complete. But the Emacs guys really want to use
`completion-at-point' for everything, which for Semantic currently
points to `semantic-ia-complete-symbol'.

Well, as I've said, it's all pretty confusing...

-David

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusi&lt;/pre&gt;</description>
    <dc:creator>David Engster</dc:creator>
    <dc:date>2012-05-02T19:49:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5781">
    <title>Re: Merge of 'newtrunk' branch</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5781</link>
    <description>&lt;pre&gt;Thank you David!

On Tue, May 1, 2012 at 2:11 PM, David Engster &amp;lt;deng&amp;lt; at &amp;gt;randomsample.de&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Alex Ott</dc:creator>
    <dc:date>2012-05-01T13:29:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5780">
    <title>Re: Merge of 'newtrunk' branch</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5780</link>
    <description>&lt;pre&gt;
Yes, ones has to override `generated-autoload-load-name' in the local
variables section of the file, which I forgot to do. This is now fixed
in trunk.


That require in there shouldn't be necessary. If you see that you need
to require packages to call end-user functions, please report this as a
bug.

Thanks,
David

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>David Engster</dc:creator>
    <dc:date>2012-05-01T12:11:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5779">
    <title>Re: Merge of 'newtrunk' branch</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5779</link>
    <description>&lt;pre&gt;Hello David

I found one error with autoloads, and not sure how to fix it - can you
look onto it?

I have code in my cedet config in following form:

(when (cedet-ectag-version-check t)
  (require 'semantic/ectags/db)
  (semantic-load-enable-primary-ectags-support))

When I start Emacs, I get following error:

Debugger entered--Lisp error: (file-error "Cannot open load file" "ectags/util")
  (cedet-ectag-version-check t)
  (if (cedet-ectag-version-check t) (progn (require (quote
semantic/ectags/db)) (semantic-load-enable-primary-ectags-support)))
  (when (cedet-ectag-version-check t) (require (quote
semantic/ectags/db)) (semantic-load-enable-primary-ectags-support))
  eval-buffer(#&amp;lt;buffer  *load*&amp;lt;2&amp;gt;&amp;gt; nil
"/Users/ott/emacs/rc/emacs-rc-cedet.el" nil t)  ; Reading at buffer
position 2885
  load-with-code-conversion("/Users/ott/emacs/rc/emacs-rc-cedet.el"
"/Users/ott/emacs/rc/emacs-rc-cedet.el" nil nil)
  load("~/emacs/rc/emacs-rc-cedet.el")
  eval-buffer(#&amp;lt;buffer  *load*&amp;gt; nil "/Users/ott/.emacs" nil t)  ;
Readi&lt;/pre&gt;</description>
    <dc:creator>Alex Ott</dc:creator>
    <dc:date>2012-05-01T08:47:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5778">
    <title>Re: Making listing buffers (data-debug and symref)read-only</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5778</link>
    <description>&lt;pre&gt;
Sorry, Launchpad only showed me the "lp:" urls. After a little digging,
you should be able to access it at:

http://bazaar.launchpad.net/~haxney/%2Bjunk/listing-buffers-read-only/


I'll let you decide whether the patch crosses the "threshold of
substantiality;" it consists of a ~200 line diff in which most of the
changes are fairly mechanical additions of changing `inhibit-read-only'
and `set-buffer-modified-p'. I have already signed papers with the FSF
for committing to Emacs core, but I'd be happy to sign any other release
you may need.

--
Daniel M. Hackney

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Daniel Hackney</dc:creator>
    <dc:date>2012-04-28T23:58:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5776">
    <title>Re: status of cedet-build.el after the merge ofnewtrunk</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5776</link>
    <description>&lt;pre&gt;
BTW, I think it would be great to have CEDET-snapshot in GNU ELPA,
i.e. the ELPA that is built-in. Would cedet-build.el need to be part of
such a package? Because then I think we would need papers...?

-David

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>David Engster</dc:creator>
    <dc:date>2012-04-30T05:59:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5775">
    <title>Re: status of cedet-build.el after the merge ofnewtrunk</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5775</link>
    <description>&lt;pre&gt;
cedet-build.el is not obsolete, I just didn't have time to update it.

cedet-autogen.el however *is* obsolete. It is important for
compatibility with the Emacs build process that we rely on the usual
`batch-update-autoloads'. We're also not allowed to autoload EIEIO
classes and methods anymore, so there's really no reason to keep
using cedet-autogen.


I would not only consider it but happily accept them. :-)

-David

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>David Engster</dc:creator>
    <dc:date>2012-04-30T05:51:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5774">
    <title>status of cedet-build.el after the merge of newtrunk</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5774</link>
    <description>&lt;pre&gt;cedet-build.el defines cedet-build-in-default-emacs command which I have
relied on before to create ELPA package of cedet.  I would like to
continue to to use this so that I can create a new cedet package once in
a while which then can be installed onto emacs 23 or 24.

It appears to me that cedet-build.el is obsolete or at least on the way
to being obsolete.  I say this based on (a) the fact that all mention of it
has been removed from INSTALL file (b) cedet-autogen.el has been moved to
obsolete directory which defines cedet-update-autoloads which is
a key function needed in cedet-build.el (c) cedet-build.el has not been
updated to reflect the change in subdirectory names.

Is there an alternative to cedet-build.el which I can leverage for
creating ELPA pacakge out of bzr snapshot of cedet?  If not, would you
consider accepting patches to keep cedet-build.el alive a little bit
longer?

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive l&lt;/pre&gt;</description>
    <dc:creator>emacs18&lt; at &gt;gmail.com</dc:creator>
    <dc:date>2012-04-29T21:37:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5773">
    <title>Re: semantic-lex-c-preprocessor-symbol-file to searchfor file from project root</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5773</link>
    <description>&lt;pre&gt;

Most of the projects would have .h that defines the project specific
#define. But these .h files would be project specific. Hence I was
wondering whether  semantic-lex-c-preprocessor-symbol-file should be a
project specific variable rather than mode-local. If there is nothing
like project specific I guess it should be buffer local. Making it
global to c-mode may not be the right thing. because c-mode would cover
different projects. I my case i have different directories of linux
kernel source each building kernel for different archs. 


Also if the file defined in  semantic-lex-c-preprocessor-symbol-file
contain a #include, will that also get parsed ? If so how do we get
full path of included .h file  ? Do we look at system-include-path ?
I guess that variable also need to be project specific/buffer local ?

-aneesh


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat lands&lt;/pre&gt;</description>
    <dc:creator>Aneesh Kumar K.V</dc:creator>
    <dc:date>2012-04-29T10:41:36</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.emacs.cedet">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.emacs.cedet</link>
  </textinput>
</rdf:RDF>

