I emailed Darryl Okahata with the patch but I do not know if he is still reachable. Here is a patch created from revision 1.14 of contrib/xcscope/xcscope.el in the official cscope CVS repository on SourceForge that fixes a bug causing databases to be skipped over when using ‘cscope-database-regexps’ if they are contained in the same directory. IF %verbose%=1 echo cscope-indexer args: %param% REM those windows version can be installed via MSYS package () REM sed and grep should be installed and in PATH REM Not responsible for any loss resulting from the use of this script Place cscope-indexer.bat in your PATH and it should be working with xcscope.Ĭscope-indexer.bat: off & setlocal enableextensions This is the cscope-indexer.bat I came up with. Not finding a windows compatible version, I decided to come up with my own port. Unfortunately xcscope.el uses a bash script (cscope-indexer) to generate the cscope database. I found this native win32 version of cscope ( ). Change/Add key-bindings Add function cscope-history-clear Fix bug of can’t call history related functions except in cscope buffer.Ĭhris: I have been looking to get xcscope.el and emacs to cooperate under windows XP without cygwin. Latest changes are: Change behavior of history ring to (which i think is) a more reasonable flavor. To view previous search result, call cscope-history-backward (’C-c s v’ or just ‘v’ in cscope buffer) or cscope-history-forward (’V’). USAGE: For basic usage refer to original comments. The other benifit is that, for large projects, cscope-ing sometimes could be time-consuming. I used to ask myself “how I get into function?” since the code I’m reading has really deep call stacks and I can’t keep them all in my mind. I think the primary benifit of this feature is to give us a clue how we gotten into current position. However, despite much convenience it provides there are still some guys, including me □, asking for certain new feature now and then on news groups: going back and forth the search history. Thank Darryl for bringing us such an amazing tool. And try google bscope, you will find a new cscope interface faster than xscope. Just touch the file cscope.po.out and cscope.in.out after finishing index. Does anyone have suggestion on how I should make xcscope.el work with the “-q” option? GP: I unsuccessfully tried modifying xcscope.el so that it uses the “cscope -b -q -k” options, I want the -q option on my large code base, so that symbol search becomes quicker. ( if (minibuffer-window-active-p old-buffer-window) Don't present the new buffer (file) inside minibuffer! I have made this fix: ( defun cscope-process-sentinel (process event) Mmc: I have this problem with xcscope.el: When i invoke a long time lasting search, and go into minibuffer (think M-x), when cscope finishes its job, xcsope will present the found file inside the minibuffer. I don’t know cscope.el, but I discovered xcscope.el recently – and this is really practical! Don’t use M-x grep anymore! I’ll review (and possibly absort) the patches mentioned here shortly. Following comments are about Darryl’s original xcscope.el. This xcscope.el package is currently available on MELPA and in Debian and in Ubuntu (package name is “xcscope-el”). The full change log is available in the README at the above link. This makes management of multiple searches dramatically better. Most significantly, multiple results are now displayed in the cscope buffer at a time. This tree fixes various bugs and adds various features. This package is stable, and development is continuing in its own tree ( ). xcscope.elĭarryl Okahata’s xcscope.el comes with the cscope package. It does not compile using MSYS on MS Windows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |