Thread: [CEDET-devel] CEDET and Java
Brought to you by:
zappo
From: Francesco M. <f...@ma...> - 2012-12-04 01:30:32
|
Hi list, I’m resorting to list after a day of frustration. My situation: I have various Java projects building with `ant' that I want to use with emacs. What I’d like to have, in order of importance: 1. Jumping to definitions easily 2. Flymake or anyway something that builds and highlights errors 3. Context sensitive completion 4. Indentation and syntax highlighting for modern day Java (generics, foreach, etc) Now, I understand that 4 is not available anywhere right now. 3 is kinda hard to do. But 1 and 2 should be achievable. I first tried to use JDEE but that was a disaster, so I turned to a CEDET-only solution. Focusing on 1: I read the following article: <http://alexott.net/en/writings/emacs-devenv/EmacsCedet.html>, which seems to provide for what I need. I pulled a fresh copy of CEDET bzr, and copied the example config in that article. I then created a new Java project using `ede-java-root-project': (ede-java-root-project "SRTool" :name "SRTool" :file "~/path/to/build.xml" :srcroot '("src") :localclasspath '("./bin" "./antlr-3.4-complete.jar" "./junit-4.10.jar" "./jcommander.jar") :classpath '("~/path/to/bin" "~/path/to/antlr-3.4-complete.jar" "~/path/to/junit-4.10.jar" "~/path/to/jcommander.jar")) CEDET does recognise the project. I can also jump to definitions - but only the ones in the buffers I have already visited. “Rescan project files” complains that `ede-java-root-project' does not support that operation. “Find file in project” works but only if I include every single subdirectory of `src' explicitly. How should I proceed? Once problem 1 is done, how do I go onto investigating 2 and 3? Is it possible to simply have CEDET to use `ant' targets to build code? Where can I find more information on context sensitive information? I think that the bit I’m missing is if it’s possible to easily use CEDET with ant/make/whatever target, or do I *have* to use CEDET own targets? I’m using emacs 23.4.1 as provided by debian testing. Thanks, Francesco |
From: Francesco M. <f...@ma...> - 2012-12-10 21:43:13
|
Hi, Sorry to bump this, but I’m seeing most questions being answered. Maybe I asked an easy question and nobody wants to bother explaining, in which case I’d be glad to be redirected to documentation. Francesco |
From: Rajanikanth J. <raj...@gm...> - 2012-12-11 00:23:50
|
On Dec 10, 2012 6:14 PM, "Francesco Mazzoli" <f...@ma...> wrote: > > Hi, > > Sorry to bump this, but I’m seeing most questions being answered. Maybe I asked > an easy question and nobody wants to bother explaining, in which case I’d be > glad to be redirected to documentation. > > Francesco > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Cedet-devel mailing list > Ced...@li... > https://lists.sourceforge.net/lists/listinfo/cedet-devel Ccing Alex as I saw some threads stating that he was working on extending java support. Alex: could you answer Francesco's questions. Thanks Raj |
From: Eric M. L. <er...@si...> - 2012-12-11 03:27:13
|
On 12/03/2012 08:30 PM, Francesco Mazzoli wrote: > Hi list, > > I’m resorting to list after a day of frustration. > > My situation: I have various Java projects building with `ant' that I want to > use with emacs. > > What I’d like to have, in order of importance: > > 1. Jumping to definitions easily Hi Francesco, Semantic can only jump to definitions for files it has already parsed. You can get around this problem by using the GNU Global or idutils integration. There are some basic instructions in the cedet.info file on setting this up. That should make your whole project available for being able to move around. > 2. Flymake or anyway something that builds and highlights errors CEDET does not have anything special to do with flymake, or this sort of feature. > 3. Context sensitive completion Getting this to work depends on good integration with the javap custom back-end that will extract symbols from your jar files, or elsewhere. > 4. Indentation and syntax highlighting for modern day Java (generics, > foreach, etc) CEDET will use the java mode, but isn't really involved in making it better. > Focusing on 1: I read the following article: > <http://alexott.net/en/writings/emacs-devenv/EmacsCedet.html>, which seems to > provide for what I need. I pulled a fresh copy of CEDET bzr, and copied the > example config in that article. I then created a new Java project using > `ede-java-root-project': > > (ede-java-root-project > "SRTool" > :name "SRTool" > :file "~/path/to/build.xml" > :srcroot '("src") > :localclasspath '("./bin" > "./antlr-3.4-complete.jar" > "./junit-4.10.jar" > "./jcommander.jar") > :classpath '("~/path/to/bin" > "~/path/to/antlr-3.4-complete.jar" > "~/path/to/junit-4.10.jar" > "~/path/to/jcommander.jar")) This is a good start. Alex (who someone else suggested reply to this thread) has some other extensions that might also help. [...] “Find file in > project” works but only if I include every single subdirectory of `src' > explicitly. How should I proceed? the two 'root' project types aren't good at finding files because they don't have a built in cache. Integrating GNU Global or idutils in with EDE however will fix that. In the cedet.info manual about GNU Global (which I had the best luck with) explains both this setup, and the database setup for finding definitions. > Once problem 1 is done, how do I go onto investigating 2 and 3? Is it possible > to simply have CEDET to use `ant' targets to build code? Where can I find more > information on context sensitive information? Alex can help with this more than I. Good Luck Eric |
From: Alex O. <al...@gm...> - 2012-12-11 09:58:04
|
I'm currently trying to commit fix for this, otherwise you need to specify also :directory slot... On Tue, Dec 11, 2012 at 10:44 AM, Francesco Mazzoli <f...@ma...> wrote: > Thanks a lot to both for the answers! > > At Tue, 11 Dec 2012 08:10:05 +0100, > Alex Ott wrote: >> It's btter to switch to Ant project type (ede-ant-project), that was >> added last week. Implementation has a number of heuristics, for >> example, it will setup srcroot automatically for you config. Besides >> this, I see, that you're using both localclasspath & classpath - this >> is not necessary in your case, it's enough to use only one of them. To >> generate list of jar files you can use the >> 'cedet-files-list-recursively' function from 'cedet-files' package, >> like this >> >> :classpath (cons "~/path/to/bin" (cedet-files-list-recursively >> "~/path/to" ".*.jar")) >> >> Ant projects could be also detected automatically, but in this case it >> won't setup classpath automatically - current heuristics are working >> only if libraries are in lib directory > > I tried this first, adding this > > (ede-ant-project > "SRTool" > :name "SRTool" > :file "~/path/to/build.xml" > :classpath (cons "~/path/to/bin" > (cedet-files-list-recursively > "~/path/to/" ".*.jar"))) > > to my config. > > However, when I open a java file in that project, I get > > eieio-default-superclass: Unbound slot: "#<class ede-ant-project>", "#<ede-ant-project SRTool>", :directory, oref > > I’m not sure what this indicates - I’m not familiar with CLOS or eieio. I want > to get the ant project working before trying the rest. > > Francesco -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |
From: Francesco M. <f...@ma...> - 2012-12-11 10:37:57
|
At Tue, 11 Dec 2012 10:54:39 +0100, Alex Ott wrote: > I'm currently trying to commit fix for this, otherwise you need to specify > also :directory slot... OK, thanks. Now the project works, but for example it seems that the srcroot is not set correctly, since it still does not correctly find files. Is there something that I have to do in particular, apart from specifying the build file? For example specifying the target. Otherwise I can’t imagine how it can automatically extract the source directory. Thanks, Francesco |
From: Alex O. <al...@gm...> - 2012-12-11 10:09:35
|
Re On Tue, Dec 11, 2012 at 4:27 AM, Eric M. Ludlam <er...@si...> wrote: >> 2. Flymake or anyway something that builds and highlights errors > > CEDET does not have anything special to do with flymake, or this sort of > feature. I think, that potentially Flymake could be extended to use information from EDE projects, but we need to think on how it can be implemented >> 3. Context sensitive completion > > Getting this to work depends on good integration with the javap custom > back-end that will extract symbols from your jar files, or elsewhere. Right now, name completion works relatively well, but it need to have information from jar files. For some project types, it's possible to extract this information automatically, but for some, like java-root & ant, it's not always possible >> 4. Indentation and syntax highlighting for modern day Java (generics, >> foreach, etc) > > CEDET will use the java mode, but isn't really involved in making it better. > >> Focusing on 1: I read the following article: >> <http://alexott.net/en/writings/emacs-devenv/EmacsCedet.html>, which seems to >> provide for what I need. I pulled a fresh copy of CEDET bzr, and copied the >> example config in that article. I then created a new Java project using >> `ede-java-root-project': >> >> (ede-java-root-project >> "SRTool" >> :name "SRTool" >> :file "~/path/to/build.xml" >> :srcroot '("src") >> :localclasspath '("./bin" >> "./antlr-3.4-complete.jar" >> "./junit-4.10.jar" >> "./jcommander.jar") >> :classpath '("~/path/to/bin" >> "~/path/to/antlr-3.4-complete.jar" >> "~/path/to/junit-4.10.jar" >> "~/path/to/jcommander.jar")) > > This is a good start. Alex (who someone else suggested reply to this > thread) has some other extensions that might also help. It's btter to switch to Ant project type (ede-ant-project), that was added last week. Implementation has a number of heuristics, for example, it will setup srcroot automatically for you config. Besides this, I see, that you're using both localclasspath & classpath - this is not necessary in your case, it's enough to use only one of them. To generate list of jar files you can use the 'cedet-files-list-recursively' function from 'cedet-files' package, like this :classpath (cons "~/path/to/bin" (cedet-files-list-recursively "~/path/to" ".*.jar")) Ant projects could be also detected automatically, but in this case it won't setup classpath automatically - current heuristics are working only if libraries are in lib directory > [...] “Find file in >> project” works but only if I include every single subdirectory of `src' >> explicitly. How should I proceed? > > the two 'root' project types aren't good at finding files because they > don't have a built in cache. Integrating GNU Global or idutils in with > EDE however will fix that. In the cedet.info manual about GNU Global > (which I had the best luck with) explains both this setup, and the > database setup for finding definitions. > >> Once problem 1 is done, how do I go onto investigating 2 and 3? Is it possible >> to simply have CEDET to use `ant' targets to build code? Where can I find more >> information on context sensitive information? Ant project can compile current project using standard 'C-c . c' & 'C-c . C' commands for compilation of target & projects - you can set "current target" using the :current-target slot of project, it will be used when Ant is invoked. I'm still thinking on how implement compilation of arbitrary Ant target (I understand how to extract all available targets), but need to think how to switch between them. -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |
From: Francesco M. <f...@ma...> - 2012-12-11 09:58:10
|
Thanks a lot to both for the answers! At Tue, 11 Dec 2012 08:10:05 +0100, Alex Ott wrote: > It's btter to switch to Ant project type (ede-ant-project), that was > added last week. Implementation has a number of heuristics, for > example, it will setup srcroot automatically for you config. Besides > this, I see, that you're using both localclasspath & classpath - this > is not necessary in your case, it's enough to use only one of them. To > generate list of jar files you can use the > 'cedet-files-list-recursively' function from 'cedet-files' package, > like this > > :classpath (cons "~/path/to/bin" (cedet-files-list-recursively > "~/path/to" ".*.jar")) > > Ant projects could be also detected automatically, but in this case it > won't setup classpath automatically - current heuristics are working > only if libraries are in lib directory I tried this first, adding this (ede-ant-project "SRTool" :name "SRTool" :file "~/path/to/build.xml" :classpath (cons "~/path/to/bin" (cedet-files-list-recursively "~/path/to/" ".*.jar"))) to my config. However, when I open a java file in that project, I get eieio-default-superclass: Unbound slot: "#<class ede-ant-project>", "#<ede-ant-project SRTool>", :directory, oref I’m not sure what this indicates - I’m not familiar with CLOS or eieio. I want to get the ant project working before trying the rest. Francesco |
From: Alex O. <al...@gm...> - 2012-12-11 10:40:42
|
you can specify your default Ant target with :current-target option (as string). You can also populate :srcroot with list of directories, that contain source code, for example, if you have: src/ org/ apache/ ... test/ org/ apache/ ... then you can set it to :srcroot '("src" "test") On Tue, Dec 11, 2012 at 11:37 AM, Francesco Mazzoli <f...@ma...> wrote: > At Tue, 11 Dec 2012 10:54:39 +0100, > Alex Ott wrote: >> I'm currently trying to commit fix for this, otherwise you need to specify >> also :directory slot... > > OK, thanks. Now the project works, but for example it seems that the srcroot is > not set correctly, since it still does not correctly find files. Is there > something that I have to do in particular, apart from specifying the build file? > For example specifying the target. Otherwise I can’t imagine how it can > automatically extract the source directory. > > Thanks, > Francesco -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |
From: Francesco M. <f...@ma...> - 2012-12-11 11:34:32
|
At Tue, 11 Dec 2012 11:40:34 +0100, Alex Ott wrote: > you can specify your default Ant target with :current-target option > (as string). You can also populate :srcroot with list of directories, > that contain source code, for example, if you have: > > src/ > org/ > apache/ > ... > test/ > org/ > apache/ > ... > > then you can set it to :srcroot '("src" "test") > Thanks, now building works! However, it still seems that EDE can’t find files. I have tried without `srcroot', and with '("src"), which is where my code resides, to no avail. The message is ede-find-file: Could not find SRTool.java in /home/bitonic/docs/courses/440/cw2/SRTool/ Curiously it doesn’t work even if I set the specific folders manually, which worked with the java-root project. Francesco |
From: Alex O. <al...@gm...> - 2012-12-11 11:38:21
|
please, try to update from repo & re-create project... On Tue, Dec 11, 2012 at 12:34 PM, Francesco Mazzoli <f...@ma...> wrote: > >> test/ -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |
From: Francesco M. <f...@ma...> - 2012-12-11 11:48:56
|
At Tue, 11 Dec 2012 12:38:13 +0100, Alex Ott wrote: > please, try to update from repo & re-create project... Does not seem to make a difference (I did get the relevant update). Just to clarify, this is what I have: (ede-ant-project "SRTool" :name "SRTool" :file "~/docs/courses/440/cw2/SRTool/build.xml" :directory "~/docs/courses/440/cw2/SRTool/" :classpath (cons "~/docs/courses/440/cw2/SRTool/bin" (cedet-files-list-recursively "~/docs/courses/440/cw2/SRTool/" ".*.jar")) :current-target "build") I then open the file `~/docs/courses/440/cw2/SRTool/src/srt/tool/SRTool.java', eand the project is loaded (I can build and the menu shows relevant options). I then try `C-c . f SRTool.java' and I get ede-find-file: Could not find SRTool.java in /home/bitonic/docs/courses/440/cw2/SRTool/ I also tried setting `:srctool' manually as indicated in the previous post. Thanks, Francesco |
From: Alex O. <al...@gm...> - 2012-12-11 12:02:12
|
as workaround, you can copy the function (defmethod ede-expand-filename-impl ((proj ede-java-root-project) name) from lisp/cedet/ede/java-root.el to lisp/cedet/ede/ant.el and change line (defmethod ede-expand-filename-impl ((proj ede-java-root-project) name) to (defmethod ede-expand-filename-impl ((proj ede-ant-project) name) and execute M-x eval-current-buffer staying in ant.el On Tue, Dec 11, 2012 at 12:57 PM, Francesco Mazzoli <f...@ma...> wrote: > At Tue, 11 Dec 2012 12:55:30 +0100, > Alex Ott wrote: >> Ah, ok, I see. The java-root project has implementation of >> ede-expand-filename-impl, while Ant project doesn't I'll think how to >> implement it for all Java projects (or maybe for all project types). But I'll >> have free time this evening > > Thanks a lot for taking the time to look into this. If you have a temporary > workaround to specify the directories manually I’ll be happy with that for the > time being. > > Francesco -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |
From: Eric M. L. <er...@si...> - 2012-12-12 00:04:16
|
On 12/11/2012 06:55 AM, Alex Ott wrote: > Ah, ok, I see. The java-root project has implementation of > ede-expand-filename-impl, while Ant project doesn't I'll think how to > implement it for all Java projects (or maybe for all project types). > But I'll have free time this evening Hi Alex, A quick word of caution on that implementation. It calls (call-next-method), then also implements something with the ede locate-fcn. The ede-project baseclass also implements something with the locate-fcn. I don't think either cpp-root or java-root need to do anything with that locate fcn, but I haven't gotten around to testing what happens if I remove it. If you have the time to test it, please see if you can tidy up this area in your new objects instead of propagating the problem. Also, will it be possible to make the ant project type auto-detect, instead of being declared in a .emacs file? Lastly, setting up GNU Global with EDE and running it on your project will make jumping to files/symbols more reliable with the regular techniques used in EDE or Semantic can't find the file or symbol in question. Eric |
From: Alex O. <al...@gm...> - 2012-12-12 06:59:13
|
HI On Wed, Dec 12, 2012 at 1:04 AM, Eric M. Ludlam <er...@si...> wrote: > On 12/11/2012 06:55 AM, Alex Ott wrote: >> >> Ah, ok, I see. The java-root project has implementation of >> ede-expand-filename-impl, while Ant project doesn't I'll think how to >> implement it for all Java projects (or maybe for all project types). >> But I'll have free time this evening > > A quick word of caution on that implementation. It calls > (call-next-method), then also implements something with the ede locate-fcn. > The ede-project baseclass also implements something with the locate-fcn. > > I don't think either cpp-root or java-root need to do anything with that > locate fcn, but I haven't gotten around to testing what happens if I remove > it. If you have the time to test it, please see if you can tidy up this > area in your new objects instead of propagating the problem. Yes, I noticed this. I'm currently trying to write short note/description on how projects could be refactored and will post it over weekend. > Also, will it be possible to make the ant project type auto-detect, > instead of being declared in a .emacs file? The Ant project is declared as autoload, and it works most of time. The main problem is with declaration of classpath in it - not all projects put libraries into specified place, and I haven't found a way to extract classpath information from Ant projects (in contrast with Maven & Lein). -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |
From: Francesco M. <f...@ma...> - 2012-12-14 11:41:45
|
Hi Alex & list, Are there any news regarding this? In general what should I look for in the log? Also, I take it that the config I posted here: <http://sourceforge.net/mailarchive/message.php?msg_id=30213328> should work, right? Thanks again, Francesco |
From: Alex O. <al...@gm...> - 2012-12-15 09:25:57
|
Sorry Francesco, I had no time this week for more hacking. I hope that I'll find some time tomorrow On Fri, Dec 14, 2012 at 12:41 PM, Francesco Mazzoli <f...@ma...> wrote: > Hi Alex & list, > > Are there any news regarding this? In general what should I look for in the > log? > > Also, I take it that the config I posted here: > <http://sourceforge.net/mailarchive/message.php?msg_id=30213328> should work, > right? > > Thanks again, > Francesco > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Cedet-devel mailing list > Ced...@li... > https://lists.sourceforge.net/lists/listinfo/cedet-devel -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |
From: Francesco M. <f...@ma...> - 2012-12-15 21:46:01
|
At Sat, 15 Dec 2012 10:25:51 +0100, Alex Ott wrote: > Sorry Francesco, I had no time this week for more hacking. I hope that I'll > find some time tomorrow Oh don’t worry, I just wasn’t sure on how to check if progress was being made or not. Thanks, Francesco |
From: Alex O. <al...@gm...> - 2012-12-17 12:36:07
|
Hi can you try new version in repository? On Sat, Dec 15, 2012 at 10:45 PM, Francesco Mazzoli <f...@ma...> wrote: > At Sat, 15 Dec 2012 10:25:51 +0100, > Alex Ott wrote: >> Sorry Francesco, I had no time this week for more hacking. I hope that I'll >> find some time tomorrow > > Oh don’t worry, I just wasn’t sure on how to check if progress was being made or > not. > > Thanks, > Francesco -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |
From: Francesco M. <f...@ma...> - 2012-12-17 13:29:15
|
At Mon, 17 Dec 2012 13:35:57 +0100, Alex Ott wrote: > Hi > > can you try new version in repository? The last change I get in the repo is on the 11th of December, maybe it’s another branch or you didn’t push? Thanks, Francesco |
From: Alex O. <al...@gm...> - 2012-12-17 13:31:10
|
Very strange - I see commits in buildbot & even on ohloh.net On Mon, Dec 17, 2012 at 2:29 PM, Francesco Mazzoli <f...@ma...> wrote: > At Mon, 17 Dec 2012 13:35:57 +0100, > Alex Ott wrote: >> Hi >> >> can you try new version in repository? > > The last change I get in the repo is on the 11th of December, maybe it’s another > branch or you didn’t push? > > Thanks, > Francesco -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |
From: Francesco M. <f...@ma...> - 2012-12-17 13:47:48
|
At Mon, 17 Dec 2012 14:31:01 +0100, Alex Ott wrote: > Very strange - I see commits in buildbot & even on ohloh.net Seems to be fine now, probably my bad! Anyhow, I tried with the fresh pulled repo, and I still can’t find files in my project (my configuration is described here <http://sourceforge.net/mailarchive/message.php?msg_id=30213328>). Francesco |
From: Alex O. <al...@gm...> - 2012-12-17 13:51:35
|
do you restarted emacs after update? It maybe because the project was already created? This also can happen if you have some files from this project open before explicit creation of project - in this case, project may be loaded automatically, so no :srcroot will be set. On Mon, Dec 17, 2012 at 2:47 PM, Francesco Mazzoli <f...@ma...> wrote: > At Mon, 17 Dec 2012 14:31:01 +0100, > Alex Ott wrote: >> Very strange - I see commits in buildbot & even on ohloh.net > > Seems to be fine now, probably my bad! > > Anyhow, I tried with the fresh pulled repo, and I still can’t find files in my > project (my configuration is described here > <http://sourceforge.net/mailarchive/message.php?msg_id=30213328>). > > Francesco -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |
From: Alex O. <al...@gm...> - 2012-12-17 13:54:45
|
Ah, I see - you have no "srcroot" slot in your configuration. I committed small change, so it will use top level directory as a base, if there is no :srcroot slot On Mon, Dec 17, 2012 at 2:51 PM, Alex Ott <al...@gm...> wrote: > do you restarted emacs after update? It maybe because the project was > already created? This also can happen if you have some files from this > project open before explicit creation of project - in this case, > project may be loaded automatically, so no :srcroot will be set. > > On Mon, Dec 17, 2012 at 2:47 PM, Francesco Mazzoli <f...@ma...> wrote: >> At Mon, 17 Dec 2012 14:31:01 +0100, >> Alex Ott wrote: >>> Very strange - I see commits in buildbot & even on ohloh.net >> >> Seems to be fine now, probably my bad! >> >> Anyhow, I tried with the fresh pulled repo, and I still can’t find files in my >> project (my configuration is described here >> <http://sourceforge.net/mailarchive/message.php?msg_id=30213328>). >> >> Francesco > > > > -- > With best wishes, Alex Ott > http://alexott.net/ > Twitter: alexott_en (English), alexott (Russian) > Skype: alex.ott -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |
From: Francesco M. <f...@ma...> - 2012-12-17 13:59:13
|
At Mon, 17 Dec 2012 14:51:26 +0100, Alex Ott wrote: > do you restarted emacs after update? It maybe because the project was > already created? This also can happen if you have some files from this > project open before explicit creation of project - in this case, > project may be loaded automatically, so no :srcroot will be set. I did restart emacs. One thing: I don’t think the problem here is setting the :srcroot: even if I set it manually the files can’t be found. Francesco |