Commits

Vasil Vangelovski  committed 62f012c

something completely different

  • Participants
  • Parent commits 49d9807

Comments (0)

Files changed (1023)

 # use glob syntax.
 syntax: glob
 
-#*.elc
+*.elc
 *.pyc
 *~
+elpa/*
+auto-save-list/*
 
 
 # switch to regexp syntax.

File ac-comphist.dat

+((("global-linum-mode" .
+   [0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0])
+  ("append" .
+   [0 0 0 0 1 0])
+  ("number" .
+   [1 0 0 0 0 0])
+  ("to" .
+   [1 0])
+  ("add-to-list" .
+   [0 0 0 0 0 0 1 0 0 0 1])
+  ("load-path" .
+   [2 0 0 0 0 0 0 0 0])
+  ("load-file" .
+   [0 0 0 0 0 0 0 1 0])
+  ("require" .
+   [0 0 0 0 1 0 1])
+  ("ecb-autoloads" .
+   [0 0 0 0 0 0 0 0 0 0 1 0 0])))

File cedet/INSTALL

+CEDET: Collection of Emacs Development Enviromnent Tools
+
+CEDET is a top-level project containing several individual package for Emacs,
+includeing:
+
+   EIEIO -    CLOS layer for Emacs Lisp
+   Semantic - Parser Infrastructure for Emacs
+   Speedbar - Everything browser
+   EDE -      File manager/ Makefile generator
+   SRecode -  Templte manager/ code generator
+   COGRE -    Connected Graph Editor
+
+REQUIREMENTS:
+
+   The full CEDET suite requires Emacs 22.1 or newer.
+   CEDET works well with either Emacs 21.3 or XEmacs 21.3.
+   Older versions of either will also work with fewer CEDET
+   features being available.
+
+   If you use a binary install of Emacs, you may need the .el
+   files for Emacs available for some aspects of the build.
+
+   CEDET is always developed on a recent CVS build of Emacs, and often
+   takes advantage of such new features.
+
+INSTALL:
+
+You can install all these packagees at once with the CEDET build and
+install scripts:
+
+1) Copy source files somewhere.
+
+2) Byte compile
+
+   There are several ways to get CEDET compiled:
+
+   a) make
+
+   b) make EMACS=<your favorite emacs>
+
+    You might also have trouble with makeinfo.  If you need to upgrade
+    makeinfo, you can do this:
+
+  c) make MAKEINFO=/usr/local/bin/makeinfo
+
+    Note: For speedbar, and older versions of Emacs, you may also need
+          to byte-compile the version of INFO and RMAIL that come with
+          your version of emacs.
+
+  d) make MAKEINFO=echo
+
+    To skip making the doc.
+
+
+  e) cedet-build.el
+
+    If you do not have "make", are on Windows, or otherwise cannot use
+    the Makefiles, you can build CEDET from within Emacs.  See the
+    commentary in cedet-build.el
+
+
+2.1) Build Issues
+
+  If running MAKE fails due to other issues such as bad loaddef
+  files, custom-autoload, incomprehensible run time errors during a byte
+  compilation, try these steps, then go back to step 2.
+
+  a) make clean-autoloads
+  b) make clean-all
+
+2.2) Make Issues
+
+  If the version of Make you are using doesn't work with the CEDET
+  Makefiles, (such as the version on AIX) you will need to download and
+  install GNU Make to use with these Makefiles.  Alternately, 
+  see cedet-build.el
+
+3) Install load hooks into your .emacs file.  For more detail on
+   any topic, see the info file common/cedet.info for more details on
+   installaiton.
+
+-----------
+;; Load CEDET.
+;; See cedet/common/cedet.info for configuration details.
+(load-file "~/cedet-VERSION/common/cedet.el")
+
+
+;; Enable EDE (Project Management) features
+(global-ede-mode 1)
+
+;; Enable EDE for a pre-existing C++ project
+;; (ede-cpp-root-project "NAME" :file "~/myproject/Makefile")
+
+
+;; Enabling Semantic (code-parsing, smart completion) features
+;; Select one of the following:
+
+;; * This enables the database and idle reparse engines
+(semantic-load-enable-minimum-features)
+
+;; * This enables some tools useful for coding, such as summary mode
+;;   imenu support, and the semantic navigator
+(semantic-load-enable-code-helpers)
+
+;; * This enables even more coding tools such as intellisense mode
+;;   decoration mode, and stickyfunc mode (plus regular code helpers)
+;; (semantic-load-enable-gaudy-code-helpers)
+
+;; * This enables the use of Exuberent ctags if you have it installed.
+;;   If you use C++ templates or boost, you should NOT enable it.
+;; (semantic-load-enable-all-exuberent-ctags-support)
+;;   Or, use one of these two types of support.
+;;   Add support for new languges only via ctags.
+;; (semantic-load-enable-primary-exuberent-ctags-support)
+;;   Add support for using ctags as a backup parser.
+;; (semantic-load-enable-secondary-exuberent-ctags-support)
+
+;; Enable SRecode (Template management) minor-mode.
+;; (global-srecode-minor-mode 1)
+
+-----------
+
+  Some items in the contrib directory may need additional study or
+  installation.  Read contrib/INSTALL for specifics on those extra
+  packages.
+
+3.1) CODE COMPLETION
+
+  If you are installing CEDET to get code completion, see the info
+  manual in common/cedet.info for more specifically about code
+  completion.
+
+3.2) INSTALL INFO
+
+   Installing the info files can be done with:
+
+     make install-info
+
+   or, if you need to specify:
+
+     make PREFIX=/prefix/to/install/to install-info
+
+4) CONFIGURE:
+
+   You can configure how the individual packages loaded in the above
+   example by adding settings in the comment section.  Please read
+   individual info manuals for each package for details on configuring
+   them.  See the texinfo manuals for details on more specific
+   configurations.
+
+   To dive right into configuring CEDET for a particular purpose, many
+   common purposes are enumerated in the CEDET installation info file.
+
+   C-u C-h i common/cedet.info
+
+
+5) BUGS/COMMENTS
+
+   To send bug reports, or participate in discussions on these
+   packages, choose a mailing list:
+
+   For Semantic use the mailing list cedet-semantic@sourceforge.net
+   via the URL:
+
+   http://lists.sourceforge.net/lists/listinfo/cedet-semantic
+
+   For EIEIO use the mailing list cedet-eieio@sourceforge.net
+   via the URL:
+
+   http://lists.sourceforge.net/lists/listinfo/cedet-eieio
+
+   For general discussions on development of these tools, and get learn
+   when minor updates are added to CVS, use the mailing list
+   cedet-devel@sourceforge.net via the URL:
+
+   http://lists.sourceforge.net/lists/listinfo/cedet-devel
+
+OTHER REQUIREMENTS:
+
+   You may also need to download some of the following files for more
+   obscure features.
+
+   To use the JavaScript parser:
+   javascript-mode.el : http://www.emacswiki.org/cgi-bin/wiki/JavaScriptMode
+   
+   To use Exuberent CTags to parse files:
+   http://ctags.sourceforge.net/
+
+   To use GNU Global integration:
+   http://www.gnu.org/software/global
+
+   To use ID Utils integration:
+   http://www.gnu.org/software/idutils/
+
+   To use CScope integration:
+   http://cscope.sourceforge.net/
+
+   To use COGRE with Graphviz Dot integration:
+   http://www.graphviz.org/
+
+   And a major mode for dot (not required):
+   http://users.skynet.be/ppareit/projects/graphviz-dot-mode/graphviz-dot-mode.html

File cedet/Makefile

+## Makefile --- Definition file for building CEDET
+##
+## Copyright (C) 2005, 2007, 2008, 2009, 2010 by Eric M. Ludlam
+## Copyright (C) 2003, 2004  by David Ponce
+##
+## Author: David Ponce <david@dponce.com>
+## Maintainer: CEDET developers <http://sf.net/projects/cedet>
+## Created: 12 Sep 2003
+## X-RCS: $Id: Makefile,v 1.27 2010/04/23 00:04:39 zappo Exp $
+##
+## This program is free software; you can redistribute it and/or
+## modify it under the terms of the GNU General Public License as
+## published by the Free Software Foundation; either version 2, or
+## (at your option) any later version.
+##
+## This program is distributed in the hope that it will be useful, but
+## WITHOUT ANY WARRANTY; without even the implied warranty of
+## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+## GNU General Public License for more details.
+##
+## You should have received a copy of the GNU General Public License
+## along with GNU Emacs; see the file COPYING.  If not, write to the
+## Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
+## Boston, MA 02110-1301, USA.
+
+######## You can customize this part of the Makefile ########
+
+## The directory where CEDET is installed
+CEDET_HOME="$(CURDIR)"
+
+## The CEDET's packages installed
+CEDET_ELISP_PACKAGES=\
+common \
+speedbar \
+eieio \
+semantic \
+srecode \
+ede \
+cogre \
+contrib
+
+CEDET_PACKAGES=\
+$(CEDET_ELISP_PACKAGES) \
+tests
+
+## Path to your Emacs
+EMACS?=emacs
+EMACSFLAGS=-batch --no-site-file
+
+## Your shell (On Windows/Cygwin I recommend to use bash)
+#SHELL=bash
+
+## Path to your find and rm commands
+FIND=find
+#RM = rm -f
+
+## INSTALL PATHS
+PREFIX=/usr/local
+
+INFO_DIR=$(PREFIX)/share/info
+
+INSTALL_INFO=ginstall-info
+
+############### Internal part of the Makefile ###############
+CEDET_VERSION=$(shell grep "defconst cedet-version" common/cedet.el | cut -d " " -f 3)
+
+CEDET_FILES=Makefile INSTALL cedet-build.el cedet-update-version.el PRERELEASE_CHECKLIST USING_CEDET_FROM_CVS
+DIST_ROOT=cedet-$(CEDET_VERSION)
+DIST_DIR=$(CEDET_HOME)/$(DIST_ROOT)
+DIST_FILE=$(DIST_DIR).tar.gz
+
+__BUILD_AUTOLOADS=$(patsubst %,%-autoloads,$(CEDET_ELISP_PACKAGES))
+__CLEAN_AUTOLOADS=$(patsubst %,clean-%,$(__BUILD_AUTOLOADS))
+__DOMAKE=$(MAKE) $(MFLAGS) EMACS="$(EMACS)" EMACSFLAGS="$(EMACSFLAGS)" SHELL="$(SHELL)"
+
+## Build
+##
+
+all: clean-autoloads packages
+
+bootstrap: clean-all packages
+
+packages: $(CEDET_PACKAGES)
+
+.PHONY: $(CEDET_PACKAGES)
+$(CEDET_PACKAGES):
+	cd $(CEDET_HOME)/$@ && $(__DOMAKE)
+
+.PHONY: ebuild
+ebuild:
+	$(EMACS) -q -batch --no-site-file -l cedet-build.el -f cedet-build
+
+## Update
+##
+
+autoloads: $(__BUILD_AUTOLOADS)
+
+.PHONY: $(__BUILD_AUTOLOADS)
+$(__BUILD_AUTOLOADS):
+	cd $(CEDET_HOME)/$(firstword $(subst -, ,$@)) && \
+	$(__DOMAKE) autoloads
+
+recompile: autoloads
+	cd $(CEDET_HOME) && \
+	"$(EMACS)" $(EMACSFLAGS) -l common/cedet.el \
+	-f batch-byte-recompile-directory $(CEDET_PACKAGES)
+
+## Cleanup
+##
+
+clean-autoloads: $(__CLEAN_AUTOLOADS)
+
+.PHONY: $(__CLEAN_AUTOLOADS)
+$(__CLEAN_AUTOLOADS):
+	$(FIND) $(CEDET_HOME)/$(word 2,$(subst -, ,$@)) -type f \
+	-name "*-loaddefs.el" \
+	-print -exec $(RM) {} \;
+
+.PHONY: clean-grammars
+clean-grammars:
+	$(FIND) $(CEDET_HOME) -type f -name "*-[bw]y.el" \
+	! -name "semantic-grammar-wy.el" \
+	-print -exec $(RM) {} \;
+
+.PHONY: clean-info
+clean-info:
+	$(FIND) $(CEDET_HOME) -type f -name "*.info*" \
+	-print -exec $(RM) {} \;
+
+.PHONY: clean-elc
+clean-elc:
+	$(FIND) $(CEDET_HOME) -type f -name "*.elc" \
+	-print -exec $(RM) {} \;
+
+.PHONY: clean
+clean:
+	$(FIND) $(CEDET_HOME) -type f \( -name "*-script" -o -name "*~" \) \
+	-print -exec $(RM) {} \;
+
+clean-all: clean clean-elc clean-info clean-grammars clean-autoloads
+
+### UNIT TEST Harness
+## Run the master CEDET unit-test suite.
+.PHONY: utest itest
+utest:
+	$(EMACS) $(EMACSFLAGS) -l "common/cedet.el" -f cedet-utest-batch
+
+itest:
+	cd tests; ./cit-test.sh Make
+	cd tests; ./cit-test.sh Automake
+	cd tests; ./cit-test.sh GNUStep
+
+### Install info files
+## Thanks Stefano Sabatini for the info install patch.
+INFO_FILES=$(shell $(FIND) $(CEDET_HOME) -type f -name '*.info')
+
+.PHONY: install-info
+install-info:
+	for file in $(INFO_FILES); do \
+	    cp $$file $(INFO_DIR); \
+	    $(INSTALL_INFO) $$file $(INFO_DIR)/dir ;\
+	done 
+
+## Uninstall info files 
+INSTALLED_INFO_FILES=$(shell find . -name *.info | sed -e 's|.*/\(.*\.info$$\)|$(INFO_DIR)/\1|')
+
+.PHONY: uninstall-info
+uninstall-info:
+	for file in $(INSTALLED_INFO_FILES); do \
+	    $(INSTALL_INFO) --delete $$file $(INFO_DIR)/dir ;\
+	    rm -f $$file;\
+	done
+
+
+## Build a distribution file.
+dist: # $(CEDET_PACKAGES)
+	rm -rf $(DIST_DIR)
+	mkdir $(DIST_DIR)
+	cp $(CEDET_FILES) $(DIST_DIR)
+	for package in ${CEDET_PACKAGES}; do \
+	   make -C $$package $(MFLAGS) DISTDIR=$(DIST_DIR)/$$package dist; \
+	done;
+	tar -cvzf $(DIST_FILE) $(DIST_ROOT)
+	rm -rf $(DIST_DIR)
+
+testvar:
+	@echo "$(TESTVAR)=$($(TESTVAR))"
+
+# Makefile ends here

File cedet/PRERELEASE_CHECKLIST

+Prerelease Checklist:
+--------------------
+
+  This is a list of things to do/try before posting a release to make sure
+  the release will work as well as can be expected:
+
+Before a dist is made:
+---------------------
+
+Update all version numbers
+
+  * M-x load-file RET ~/cedet/cedet-update-version.el
+  * M-x cuv-update
+    - Answer all questions, updating verion numbers as needed.
+
+Add a CVS tag
+
+  * Create a new copy of CVS TRUNK
+    - mkdir <some dir>
+    - cvs -d <username>@cedet.cvs.sourceforge.net:/cvsroot/cedet co cedet
+    - mv cedet cedet-<branchname>  # (such as cedet-1p0beta3)
+    - cd cedet-branchname
+    - touch `find . -name Makefile`
+    - make dist
+    - ./testdist.sh # Test out that basic stuff is working before tagging.
+    - cvs tag -b <branchname>     
+
+  * update new sandbox to branch
+    - cvs update -r <branchname>
+
+  * Apply patches to above while resolving other issues.
+
+  * Build the new area:
+    - touch `find . -name Makefile`
+    - make EMACS=semacs
+
+Update Changelogs
+
+  * Use a fresh emacs
+    - emacs -q
+    - M-x load-file RET common/cedet.el RET
+  * Update the Log from CVS
+    - M-x load-file RET cedet-update-changelog.el RET
+    - M-x cuc-update-all-changelogs RET
+
+Build a DIST file
+
+  * touch `find . -name Makefile`
+  * make
+  * make dist
+
+After a dist is made:
+--------------------
+
+CEDET Unit tests
+  * From a CVS area:
+  * make utest
+
+CEDET integration test
+  * From a CVS area:
+  * make itest
+
+CEDET Full distribution testing
+  * From a CVS area:
+  * make dist
+  * ./testdist.sh EMACS
+    - where EMACS is the version of emacs you want to test with
+
+CEDET & Common area
+
+  * Uncompress/Untar release archive.
+  * Compile with Makefile:
+     make
+     make EMACS=xemacs
+  * Build on multiple platforms
+     - Linux
+     - Windows
+     - Other
+
+  * Check version numbers of different tools.
+
+     - Verify output of:
+       M-x cedet-version RET
+       - Check the declared version numbers.
+       - Make sure that if changes were made to those modules, the version
+         is updated.
+
+  * Start in a clean Emacs:
+    - Start emacs this way:
+
+      emacs -q
+      -or- 
+      xemacs -q
+
+      M-x load-file RET cedet/common/cedet.el RET
+      M-x semantic-load-enable-minimum-features RET
+
+  * All individual CEDET unit test
+
+      M-x cedet-utest RET
+      - Note: Runs all automated unit tests.  These tests are repeated below.
+      - Note: This runs a couple more tests than the MAKE command above.
+
+  * Test ezimage
+
+      M-x ezimage-image-association-dump RET
+      - Verify some common images for Emacs and XEmacs.
+      M-x ezimage-image-dump RET
+      - Verify the default registered images for Emacs and XEmacs.
+
+      NOTE: These are in cedet-utest, but pictures need verification.
+
+  * Test pulse
+      M-x pulse-test RET
+      - Verify pulse does what messages say.
+      - Try in Emacs 22, and older Emacs, or XEmacs.  (different behaviors)
+
+    NOTE: This is in cedet-utest.  Needs additional x-platform care.
+
+EIEIO
+
+  * M-x eieio-browse RET
+
+    This will list the currently loaded class hierarcies.  After using
+    the test harness, and loading semantic, this should be a long list.
+
+  * Running tests for semantic/semanticdb, and EDE both test
+    other basic EIEIO features.
+
+Semantic
+
+  * Make sure the semanticdb inversion check against persistent file loading
+    is updated if the file-format has changed.
+
+  * In a clean Emacs  
+
+    Visit files for different modes.  Include:
+      All files in cedet/semantic/tests.
+      .html file of your choice.
+      .texi files from the doc directory.
+      A lisp file, such as semantic.el.
+      C# file
+      .js javascript file
+      Makefile
+
+    Start with:
+      M-x toggle-debug-on-error RET - Enable debugging within the
+          parser and incremental parser.  (Usually hidden.)
+
+    For each supported mode:
+      M-x bovinate RET - verify tags are accurate.
+      M-x speedbar RET - Open the file and verify tags.
+      - Check the TAGS menu for tags in that file.
+      
+      M-x global-semantic-highlight-edits-mode RET
+      - Edit a file.  See the highlight of newly inserted text.
+      - Customize `semantic-edits-verbose-flag' to be non-nil.
+      - Wait for the idle scheduler, it should clean up the edits.
+        - observe messages from incremental parser.  Do they relate
+	  to the edits?
+      - M-x bovinate RET - verify your changes are reflected.
+
+      Visit the menu Senator->Modes
+      - Enable that mode (if not already enabled) and verify the
+        advertised behavior.
+
+      - Test aspects of the Senator navigation menu.
+
+      M-x semantic-analyze-current-context RET
+       - Do this in different contexts in your language
+         files.   Verify that reasonable results are returned
+         such as identification of assignments, function arguments, etc.
+
+       - Optionally, use `semantic-speedbar-analysis' instead of
+         'semantic-analyze-current-context'.
+
+       - At a location with incomplete syntax (a list of arguments
+         with no close paren for instance: repeat previous step. 
+
+      M-x semanticdb-find-test-translate-path RET
+       - Verify the list matches the include files.
+         You may need to check the value of
+         `semanticdb-find-default-throttle' to determine what should, or
+ 	 should not be on the list.
+
+      - With cursor on different types of declarations:
+      M-x semantic-test-all-format-tag-functions RET
+        - Verify all formats work.
+
+      - Use your favorite semantic-enabled tool.
+
+  * Try semantic-regtest.el (from CVS).
+
+Speedbar
+
+  * In a clean Emacs
+
+    M-x speedbar RET
+
+    - browse through directories, expand tags in some files.
+    - Special support files to try:
+      - texinfo files (speedbar.texi)
+      - html files
+      - rmail files (RMAIL)
+
+    M-x Info-speedbar-browser RET
+
+    - browse through the manuals
+
+EDE
+
+   * In a clean Emacs
+
+     - Examine files in the ede directory, such as:
+       ede.el
+       ede.texi
+       NEWS
+
+     - For files in these project, verify the Project menu
+     - Try builds for these files
+     - Try some other menu items
+
+COGRE
+
+   * In a clean Emacs
+
+     M-x cogre RET mygraph RET
+
+     Create a block diagram.
+
+   * In a clean Emacs
+
+     from cogre.el, put cursor on `cogre-graph-element'
+
+     M-x cogre-uml-quick-class RET RET
+
+     - Verify the grpah.  (on parent, some direct children.)
+     - Move some blocks around (M-f, M-b, M-n, M-p)
+
+SRecode
+
+   * Verify menu working in SRT, C++, and Emacs Lisp.
+     * Make sure srecode-mode is on.
+
+   * Try inserting file:empty in some modes, and then a function
+     to make sure prompts work.
+
+   * Check the maps:
+     M-x srecode-get-maps RET
+
+     Note: In cedet-utest, but make sure the output contains the known
+           templates.
+
+GENERAL
+
+   * Run `checkdoc' against various source files to make sure
+     doc strings are conforming.
+
+DEPENDANT TOOLS
+---------------
+
+   * Test this new release against dependent tools, including:
+     - JDEE
+     - ECB
+
+After patches are applied:
+-------------------------
+
+After patches are applied to the release branch, merge them back into
+TRUNK.
+
+  In a sandbox with TRUNK/HEAD active.
+  * cvs update -j <branchname> filename
+
+    - This merges changes from the branch into the trunk.
+    - Use emacs to check these branch merges in.

File cedet/USING_CEDET_FROM_CVS

+Using CEDET from CVS:
+====================
+
+If you have loaded CEDET from CVS, you will find that the basic
+installation is almost the same as for the regular distribution.
+
+All EDE Project files for CEDET are checked into CVS along with the
+corresponding Makefiles.  Since "Project.ede" comes after "Makefile"
+alphabetically, your CVS checkout command will always leave timestamps
+that indicates that the Makefiles are out of date.
+
+Thus, the first compilation step is:
+
+-----
+touch `find . -name Makefile`