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. NET application.It does not compile using MSYS on MS Windows. Thanks to Scott McCain for his contribution for a modern UI remake of the. Thanks to Murray Lindeblom for his contribution on the WINUSB drivers. This application is open source, so that anyone can port it to another OS, or perhaps just use the source for a similar project. Trust me, the driver is just WINUSB with my own. I currently don't have a digital signature from a certificate authority, so you will get a big red warning when installing the driver. Connect the USB device and install the USB Driver.Update the the device with the latest firmware.USB capable device, such as the Xminilab HW 2.0, or Xprotolab HW 1.7.This application is open source, so everyone is encouraged to improve it.įor Windows, you will need to install the WinUSB drivers using the ZADIG tool. This is the FIRST RELEASE of the software, meaning that it may have many bugs. The PC interface has been rewritten in the Qt framefork so it can be multiplatform. This software is used to interface to Gabotronics' line of oscilloscopes (Xprotolab / Xminilab).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |