I use cscope with emacs, and it works well, but it creates cscope.out and cscope.files in the root directory.
My project is configure so that only the "/private" directory is ignored by SVN.
How can I tell cscope to put its files in "/myproject/private" rather than "/myproject"?
According to the documentation there is no such setting (or at least I cannot find it). If SVN is what concerns you can just ignore the cscope files on their own.
Related
I want to use the same clang-format file for all my project since I have multiple. But I don't want to have them in every workspace and i already have a clang-format file in my home directory, how can I make this work?
Or is this impossible?
I have already seen this question:
How can i configure clang format without .clang-format file in every workspace?
but my clang-format file is like 80 lines long and I just want to edit the stuff locally on my home without having to change it in vscode as well.
Maybe this will help.
The clang-format -style=file is somewhat misleading.
file is not the path to the file you want but rather tells clang-format to use the .clang-format file it can find within the project folders - going all the way up.
And as VSCode is the case, the C++ extension is using by default the clang-format in the VSCode extensions folder.
Which should make the clang-format to go cd .. until it finds .clang-format in your workspace folder
Set "clang-format.style": "file" property to fix it.
I am a Emacs user, and have a long configuration file (.emacs) by default. But now I need to add some extra configuration for some specific project. I wonder how I could archive it.
To be more specific:
I have a default .emacs file in the ~/ folder. Now for a specific project under ~/project/, I have a specific Makefile under the project folder, I hope I could press one a default compile key to make it.
I prefer to write another small configuration file in the project folder, and manually load it when I am working in this project. But I don't know how to make it work.
Thanks!
I want setup the projectile project for project that has no local git, hg, bzr, etc. directories so I cannot use their repositories as source of project files. Is it enough to just create the .projectile file in the root directory and use the C-u C-c p f to refresh the cache. I've tried this and in my case it is not working (my .projectile is empty - shall I fill it with some rules?). What I would expect is the emacs/projectile to automatically index all my project, i.e. directory-by-directory, file-by-file, so I can make later quick search for the files.
Could you please give me some step-by-step hints ?
Thanks!
[--Update--]
This is an excerpt from my .emacs config file:
(require 'projectile)
(projectile-global-mode)
(setq projectile-indexing-method 'native)
(setq projectile-enable-caching t)
After the C-c p f sequence I'm asked by the "Find file:" prompt but the only file in the list is the .projectile file itself - none of the project files are displayed.
Currently, I have found out that after you have created a .projectile file in the directory of your choice, projectile will only use it after you restart emacs from that directory.
The caching is working well.
I am trying learn how to work with CEDET. I don't have any project to mess around so I want to shoot Emacs itself.
It seems CEDET automatically detects Emacs as a project when I open Emacs repository in dir. But when I do M-x ede-find-file there is no file to open.
Question is, How can I exactly setup Emacs as a project in CEDET to make use of EDE and other goodies of CEDET.?
Seems the documentation for this hasn't been completed yet.
The command ede-find-file doesn't provide completion. If you are visiting some file in the Emacs source (like INSTALL) and do this:
M-x ede-find-file RET emacs.c RET
it should pop up emacs.c.
Different CEDET features all have different kinds of dependencies so it's hard to answer the question specifically, but generically, all you have to do is visit a file in your Emacs project, and the other features should be enabled.
I think, that it should be added the same way as other EDE projects, with something like:
(setq emacs-project
(ede-emacs-project "emacs-head"
:file "/home/ott/work/emacs-head/README"))
At least this works for me...
So list-load-path-shadows tells which .el files shadow other files. Most of the times the native files found in my emacs distribution shadow newer files I downloaded which I preload in my init file.
For example I have cloned the cedet repository and have that always up to date but the cedet files inside my Emacs 23.4 shadow the newer cedet files i load in my init file.
I can't clone cedet over the directory in /lisp/cedet since packages like eieio or speedbar would still not get overwritten since they are in a different folder.
The temporary solution now is to delete the older packages that came bundled with emacs in order to give priority over the ones I load via my init file.
Is there a way to prioritize the load of my init file over the load of the default emacs packages?
If you use CEDET 1.0 or 1.1, the basic install instructions work fine, since many names are different. If you use CEDET from bzr trunk which uses the new naming scheme, you need to use:
(load-file "/home/user/cedet/cedet-devel-load.el")
which will perform the necessary magic to remove the built-in CEDET from the load path, and install the new CEDET onto your load path.
See the INSTALL file in CEDET bzr trunk for more.
Put the cedet repository directory at the front of your load-path and Emacs will pick it up from the cedet area...