<?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://blog.gmane.org/gmane.emacs.cedet">
    <title>gmane.emacs.cedet</title>
    <link>http://blog.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/5799"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5798"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5797"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.emacs.cedet/5796"/>
        <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: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/5799">
    <title>Re: semanticdb-javap configuration</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5799</link>
    <description>&lt;pre&gt;
Indeed, this is not well documented.  The configuration was wrapped up 
for android, but for other Java projects, I (personally) haven't tried 
it so have nothing to write doc from.

For android, the config is like this:

   (let ((aj (cedet-android-sdk-jar)))
     (add-to-list 'cedet-java-classpath-extension aj t)))

where aj is the android jar file.

You could also use M-x customize on that variable.

the code for getting semanticdb-javap setup is automatic when you start 
parsing java files.

Earlier in the mailing list someone had identified some shortfalls in 
the current libraries, but had gotten a bunch of good stuff working. 
Hopefully you will find things work ok for you also.

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/
_______________________________________________
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>Eric M. Ludlam</dc:creator>
    <dc:date>2012-05-25T02:22:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5798">
    <title>Re: Problems activating ede minor modes</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5798</link>
    <description>&lt;pre&gt;Hi,

If you use (global-ede-mode 1) it will activate EDE in those modes for 
you.  As it turns out, you can't init EDE until after user hooks run. 
EDE uses find-file-hook, which runs after misc modes are setup.

If you want to control which buffers get EDE treatment, you should 
instead just configure which kinds of projects you want to use, and EDE 
will only activate for those matching those project types.

Good Luck
Eric

On 05/10/2012 11:18 AM, Ronald Parker Jr wrote:

------------------------------------------------------------------------------
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 M. Ludlam</dc:creator>
    <dc:date>2012-05-25T01:57:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5797">
    <title>Re: Fitting EDE on top of an existing build framework</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5797</link>
    <description>&lt;pre&gt;Hi,

Sounds like you have a good start on your EDE project.

Unfortunately, the generic EDE project assumes projects where every 
subdir has a config file in it, and it then assembles the toplevel 
project from all the subprojects.  This would be a typical Make style 
project where you might call make -C from your toplevel Makefile.

There are other projects that have only one config file at the top, and 
all subdirs are assumed to be part of that project.  This includes the 
android, arduino, emacs, and Linux project types.

The problem with this kind of project, is you need to open a file at the 
top-level to get it detected before opening files from subdirectories. 
Easy to forget.

Anyway, the logic for doing that is in the load-type of the project 
autoloader.  You didn't create one since you used 
ede-generic-new-autoloader.  That doesn't return the new autoloader for 
modification.  You can, however, just copy that function and tweak it to 
use your own load-type function.

Anyway, if you have some lisp skills, you can just splice in some 
directory matching code against previously loaded projects of your type. 
  You can find examples in the android project type.  I don't think 
that's part of Emacs yet though, so you'd need to find it from the bzr 
version.

There were a bunch of changes in the EDE project loading since CEDET as 
found in Emacs.  The trick I describe should work, but I'm not 100% sure 
if the symbols are exactly the same.  The emacs project type should have 
some similar logic to use, though it uses tricks related to directory 
names too.

Good Luck
Eric

On 05/11/2012 12:20 AM, sand&amp;lt; at &amp;gt;blarg.net wrote:

------------------------------------------------------------------------------
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 M. Ludlam</dc:creator>
    <dc:date>2012-05-25T01:53:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.emacs.cedet/5796">
    <title>Re: semantic cache errors (invalid escape character syntax)</title>
    <link>http://permalink.gmane.org/gmane.emacs.cedet/5796</link>
    <description>&lt;pre&gt;
Hi,

There are a couple possibilities for semanticdb not loading in old 
semanticdb save files.

One is if the security for the save file is somehow getting in the way. 
  If that is the case, check your *Messages* buffer after you think the 
database should have been loaded to see what it says.  The messages 
would be explicit about a 'corrupt' file.

If it were corrupt, or if the version numbers were broken (and it thinks 
your save files are too old) it should save over the old file when it 
reparses your headers and you exit emacs.  You can configure it to not 
save, and if you did that, use the semanticdb-save-add-db command to 
force it.

Since the saved databases are just lisp code, you can open them up, and 
use: C-M-f to do a quick check for unbalanced parenthesis (or escape 
characters)

Lastly, if your headers are on some path accessible via tramp or one of 
the network prototcols in Emacs, it won't save those.

If you are using the default setup, then it is likely you have something 
in your headers causing the save file to go bad.  If just scanning with 
C-M-f doesn't work, you could use edebug (just load it) and then use 
eval-buffer to see if anything goes wrong, and that could point at the 
problem area.

Good Luck
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 M. Ludlam</dc:creator>
    <dc:date>2012-05-25T01:12:51</dc:date>
  </item>
  <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

------------------------------------------------------------------------------
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-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 build without going through the compile-command hack.  Further down the line, I should be able to mine the Config file for metadata on what flymake should invoke, and where GNU Global should put its output files.  But I'm having a hard time.  What I have so far is:

  (require 'ede/generic)

  (defclass ede-generic-confoogure-package-project
       (ede-generic-project)
     ((buildfile :initform "Config"))
     "Generic Project for Confoogure packages.")

  (defmethod ede-generic-setup-configuration
       ((proj ede-generic-confoogure-package-project) config)
     "Setup a configuration for Confoogure package."
     (oset config build-command "confoogure-build ")
     (oset config debug-command "confoogure-build "))

  (defmethod project-compile-project
      ((proj ede-generic-confoogure-package-project) &amp;amp;optional command)
    (require 'compile)
    (let ((default-directory (oref proj :directory)))
      (compile (oref (oref proj config) :build-command))))

  (ede-generic-new-autoloader "edeproject-confoogure-package"
                              "Confoogure Package" "Config" 
                              'ede-generic-confoogure-package-project)

As you can see from the require statement, I'm using the CEDET shipped with the Emacs24 pre-release.  There are non-technical issues that make it easier to use the as-shipped files.

The problem seems to be that EDE requires subprojects to function properly.  Assume we have the following layout...

   MyPackage/
      Config
      bar.c
      src/
        foo.c

If I load "src/foo.c", the "Development" menu is missing the entire "Build Project" submenu, and the two entries in the "Project Options" menu are greyed out.  If I load "bar.c" in the same directory as the Config file, the "Development" menu has a lot more options, and most of them available for selecting.  Similarly, calling (ede-current-project) returns what I would expect for "bar.c", but returns nil for "src/foo.c".  For whatever reason, calling `C-c . C' directly in "src/foo.c" does seem to do the right thing.

So is there something I'm missing that will let EDE recognize descendant files as part of a top-level project?  And is there a way to recognize Dired buffers as being part of a top-level project, so EDE commands will work in those as well?

Thanks,

Derek

&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 on how ELPA itself works as well as
why I did the things I did, and also how to create your own ELPA
repository, etc.  Let me know if that would be helpful.

I'll now be creating ELPA package of cedet once every few days and use it
to see what else needs to be changed.

I am always glad to sign over all my emacs related work to FSF.
However I do not know how to get my employer to sign papers as well.
I am willing to sign papers that say that my emacs work has nothing to do
with my primary job.


--------------------------------------------------------------------------------
=== modified file 'Makefile'
--- Makefile    2012-05-04 10:28:00 +0000
+++ Makefile    2012-05-07 03:51:10 +0000
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -36,6 +36,9 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 INFO_FILES=$(shell $(FIND) $(CURDIR)/doc/texi -type f -name '*.info')
 INFODIR=$(CURDIR)/doc/info

+# Date of today such as "20110731".  This is used as ELPA package version.
+DATE = $(shell date +%Y%m%d)
+
 all: clean-autoloads autoloads touch-makefiles compile info install-info

 compile:
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -66,6 +69,46 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
     &amp;lt; at &amp;gt;mkdir -p $(INFODIR)
     &amp;lt; at &amp;gt;$(foreach infofile,$(INFO_FILES),cp $(infofile)
$(INFODIR);$(INSTALL-INFO) --info-dir=$(INFODIR) $(infofile);)

+# Create ELPA package of cedet and use today's date as version.
+elpa: autoloads info cedet-$(DATE).tar cedet-readme.txt
+
+cedet-$(DATE).tar : cedet-$(DATE)
+    tar cf $&amp;lt; at &amp;gt; $&amp;lt;
+
+# Because 'autoloads' and 'info' targets were already made, all *.el
+# files such as c-by.el should have been generated.
+# So create a directory and copy all *.el and *.info files along with
+# the 'dir' file to that directory.  Other files are not needed, but
+# may be needed to satisfy GPL requirements.
+# Also create _cedet_autoloads.el just to have one line with autoload
+# cookie.  When `package-install' is executed, this will be used to
+# create cedet-autoloads.el file with the one line.
+# Also create cedet-readme.txt with some blurb about cedet.
+cedet-$(DATE):
+    mkdir -p $&amp;lt; at &amp;gt;
+    find lisp \( -name '*.el' -o -name '*.wy' -o -name '*.by' \) -exec cp
--parents {} $&amp;lt; at &amp;gt; \;
+    cp -p *.el $&amp;lt; at &amp;gt;
+    cp -p doc/info/* $&amp;lt; at &amp;gt;
+    echo ';;;###autoload' &amp;gt; $&amp;lt; at &amp;gt;/_cedet_autoloads.el
+    echo '(load-library "cedet-devel-load.el")' &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;/_cedet_autoloads.el
+    echo "(define-package \"cedet\" \"$(DATE)\" \"CEDET\")" &amp;gt;
$&amp;lt; at &amp;gt;/cedet-pkg.el
+
+cedet-readme.txt:
+    echo "CEDET is a Collection of Emacs Development Environment Tools
including"    &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+    echo "core libraries such as EIEIO, and semantic, and user interface
tools"    &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+    echo "such as Speedbar, EDE, and COGRE."                    &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+    echo ""                                        &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+    echo "While these tools are independent, and all have their own
manuals,"    &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+    echo "they are also all co-dependent within CEDET, and are dependent
on the"    &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+    echo "CEDET common libraries such as inversion and ezimage."
    &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+    echo ""                                        &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+    echo "This manual describes how to configure the tools as a whole
to"        &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+    echo "accomplish some tasks."                            &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+    echo ""                                        &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+    echo "To send bug reports, or participate in discussions about CEDET,
use"    &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+    echo "the mailing list cedet-devel.net via the URL:"                &amp;gt;&amp;gt;
$&amp;lt; at &amp;gt;
+    echo "http://lists.sourceforge.net/lists/listinfo/cedet-devel"
    &amp;gt;&amp;gt; $&amp;lt; at &amp;gt;
+
 clean-autoloads:
     &amp;lt; at &amp;gt;echo Removing loaddefs.el files from subprojects.
     &amp;lt; at &amp;gt;$(foreach proj,$(PROJECTS_AUTOLOADS),cd $(CURDIR)/$(proj) &amp;amp;&amp;amp; if [ -f
$(LOADDEFS) ];then $(RM) -f $(LOADDEFS);fi;)
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -73,6 +116,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 clean-all: clean-autoloads
     &amp;lt; at &amp;gt;echo Calling \"$(MAKE) clean\" in all projects.
     &amp;lt; at &amp;gt;$(foreach proj,$(PROJECTS),echo "  &amp;gt; $(proj)";cd $(CURDIR)/$(proj) &amp;amp;&amp;amp;
$(MAKE) clean;)
+    rm -rf cedet-$(DATE) cedet-$(DATE).tar cedet-readme.txt

 utest:
     $(EMACS) -Q -l cedet-devel-load.el --eval '$(UTEST)' -f cedet-utest


On 29 April 2012 22:59, David Engster &amp;lt;deng&amp;lt; at &amp;gt;randomsample.de&amp;gt; wrote:

------------------------------------------------------------------------------
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>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

------------------------------------------------------------------------------
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 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
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: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)  ;
Reading at buffer position 784
  load-with-code-conversion("/Users/ott/.emacs" "/Users/ott/.emacs" t t)
  load("~/.emacs" t t)
....

It looks like loaddefs aren't correctly generated. I checked
semantic/loaddefs.el, and `cedet-ectag-version-check' function exists
there, but it marked as

(autoload 'cedet-ectag-version-check "ectags/util" ...)

instead of correct value (autoload 'cedet-ectag-version-check
"semantic/ectags/util" ...) - I changed it manually, and everything is
working correctly now, but I don't know how to fix it so it will have
semantic prefix before each package...

load-path is a variable defined in `C source code'.
Its value is
("~/projects/cedet-git/contrib/"
"/Users/ott/projects/cedet-git/lisp/speedbar"
"/Users/ott/projects/cedet-git/lisp/common"
"/Users/ott/projects/cedet-git/lisp/eieio"
"/Users/ott/projects/cedet-git/lisp/cedet"
"/Users/ott/projects/cedet-git/"
"/Applications/Emacs.app/Contents/Resources/site-lisp"
"/Applications/Emacs.app/Contents/Resources/lisp"
"/Applications/Emacs.app/Contents/Resources/lisp/vc"
"/Applications/Emacs.app/Contents/Resources/lisp/url"
"/Applications/Emacs.app/Contents/Resources/lisp/textmodes"
"/Applications/Emacs.app/Contents/Resources/lisp/progmodes"
"/Applications/Emacs.app/Contents/Resources/lisp/play"
"/Applications/Emacs.app/Contents/Resources/lisp/org"
"/Applications/Emacs.app/Contents/Resources/lisp/nxml"
"/Applications/Emacs.app/Contents/Resources/lisp/net"
"/Applications/Emacs.app/Contents/Resources/lisp/mh-e"
"/Applications/Emacs.app/Contents/Resources/lisp/mail"
"/Applications/Emacs.app/Contents/Resources/lisp/language"
"/Applications/Emacs.app/Contents/Resources/lisp/international"
"/Applications/Emacs.app/Contents/Resources/lisp/gnus"
"/Applications/Emacs.app/Contents/Resources/lisp/eshell"
"/Applications/Emacs.app/Contents/Resources/lisp/erc"
"/Applications/Emacs.app/Contents/Resources/lisp/emulation"
"/Applications/Emacs.app/Contents/Resources/lisp/emacs-lisp"
"/Applications/Emacs.app/Contents/Resources/lisp/calendar"
"/Applications/Emacs.app/Contents/Resources/lisp/calc"
"/Applications/Emacs.app/Contents/Resources/lisp/obsolete"
"/Applications/Emacs.app/Contents/Resources/leim")


On Sat, Apr 28, 2012 at 4:28 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-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>
  <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>

