So I do have Emacs 24.3.1 installed, and from 24 onwards it comes with CEDET. I installed ECB through list-packages and everything seems to work - except methods window refreshing.
When I open a file, all methods are displayed and I can jump to them no problem. But the issue is that they never refresh without restarting Emacs. I have experimented with almost every related variable I could find and nothing works.
I am desperately looking for solution, sice it pretty much nullifies methods window usability when I'm expanding the project.
I have these variables added, no Emacs errors, but it still won't refresh - neither after saving, nor after some idle time.
(setq auto-update-methods-after-save 1)
(global-semantic-idle-scheduler-mode 1)
(global-semanticdb-minor-mode 1)
I am new to this, so I may be missing some obvious solution. Could anyone help me? I can provide any configuration file or info you'll need.
EDIT: Of course tried C-c . r , no results.
I've just had same problem. The methods list got updated after I do:
1) revert-buffer
2) ecb-rebuild-methods-buffer (C-c . r)
The fact that just p.2 is not enough seems to be a bug though.
Related
I'm trying to get familiar with emacs and Clojure and its working out pretty well..
It's just that everytime I get a Clojure error, it will close any emacs-window except the one where the error occured and instead show me a giant empty window of "popwin-dummy".
I can't quite see how that's supposed to help me fixing any bug... Can you tell me how to disable this behaviour?
Have a nice day!
As a general protection against "Emacs messed up my window configuration" occurrences, add the following to your init file:
(winner-mode 1)
You can also toggle it for the current session with M-x winner-mode
Then whenever your window configuration is unexpectedly changed, use C-c<left> to call winner-undo (which you can do repeatedly if necessary).
C-c<right> takes you back to the most recent configuration (immediately, rather than step-by-step).
Sometimes Emacs stops to respond to key bindings, for example:
it's impossible to C-x C-s save buffer
it's impossible to C y yank killed text
when mark activated it's invisible
and many other disadvantages.
The only way to return normal behaviour is to relaunch Emacs, though such odd behaviour can occur again very soon. Also, switching buffer to and fro could help a bit, at least it is possible to write buffer.
What is possible reason of this breakage?
Remark: Please review. I've tried to simplify question, but if this still is not good enough, let me know and I'll delete it.
In my particular case the issue was introduced by conflict between git-gutter-fringe plugin and FlyCheck when both of them try to place fringe marks at the same place. To spot this kind of conflicts it is helpful to open * Messages * buffer (by default C-h e), where all kind of errors logged
To resolve problem, I simply rejected git-gutter-fringe plugin.
Hope, this will be helpful for somebody.
Each time I scroll top down / top up a buffer the Backtrace buffer pops-up and takes half the size of my window, this is quit annoying.
Especially as I don't use at all this buffer, so does anyone know how to prevent Bracktrace to pop-up?
I would be grateful. :)
lawlist is correct; this is certainly a consequence of the debug-on-error variable being set.
If you're not setting it yourself, then it must be a third-party library. You could use M-x rgrep RET debug-on-error RET (or maybe debug-on-error t) on your site-lisp and custom lisp directories, to help track down which library is responsible.
If you happen to use nxhtml, then it's likely to be that at fault (I'm don't think it's been updated anytime recently, and the last version I saw still had this issue in the code). Look in nxhtml-base.el and comment out the offending line (or look in autostart.el if you don't have the nxhtml-base.el file).
I used emacs23 this past few years, but multiples updates packages (especially Python-for-Emacs) have bound me this morning to upgrade to 24.
I have no problems now.
Thanks you for your time and your answers.
I'm developing a mode for Emacs, and everytime I switch to its buffer, viper gets turned on. I've modified viper-mode to trace where viper-mode is being called, and surprisingly set-viper-state-in-major-mode is called by running the viper-post-command-hooks, set to nil. Any idea of what is going on?
Thanks!
EDIT: For the benefit of all beings, here is what I found out: as instructed by Trey, I started emacs with -Q and manually loaded both viper and my package. As I could reproduce the bug, the problem was on one of these packages. After line-by-line filtering, I discovered that the innoquous-looking (kill-all-local-variables) was causing the problem.
There's something in initialization that's causing it.
First try starting without your .emacs emacs -q. If the problem persists, then the trigger is in the site-start.el. So, talk to whomever installed Emacs and get them to remove the customizations there. You can also always use the -Q startup option to avoid loading the site-start.el.
If the problem isn't in site-start.el, and you don't think it's in your .emacs, it might be in a custom default.el file, which you can prevent from being loaded by adding:
(setq inhibit-default-init t)
to your .emacs.
If you still have a problem, then I'm 99% sure it's in your .emacs.
To be 100% sure, try emacs -Q, which runs Emacs with no customizations. If the problem persists, download and install your own Emacs b/c you surely can't trust the installation you're using.
So, now if you're convinced it's in your .emacs, start cutting out parts of your .emacs, or introduce an error in your .emacs with (error "frog"), and progressively rule out which portions of your .emacs are causing the problem.
g'luck
The function kill-all-local-variables will run all functions added to change-major-mode-hook, this is a common way for global minor modes to initialize themselves. For example, global font lock and global cwarn mode use this.
I haven't used viper myself, but chances are that it use this mechanism. Of course, you still would have had to enable it in your init file, somehow, so if you simply would stop doing this, it would solve your problem as well.
Try commenting out any references to viper mode in your .emacs. I don't get sent into viper mode, unless I start playing around with viper mode before I eval your new mode.
Maybe there's more being done with this statement than you think:
(use-local-map ecoli-map)
Try to change some of your binds in your map. eg. j to C-j and k to C-k.
Maybe emacs is getting confused?
Try removing your ~/.viper config file, and also check your .custom.el for settings that might kick viper into action in your major mode (or globally).
I'm pretty old school sometimes and I like working with Emacs in my terminal. (I work with IDEs all the time. But sometimes, when in the privacy of my own home, I just like a text editor a terminal and a beer)
However, the default Emacs that comes with OS X does not seem to highlight the comments in font-lock-mode. I've seen this behavior in both Python and C mode.
I've already searched some forums and I found one post where the person was having the same problem as me:
http://forums.macosxhints.com/showthread.php?p=512361
Is is there any way to fix this problem?
I had this exact same problem. The solution is to change the color used for the comment face as follows:
(set-face-foreground 'font-lock-comment-face "red")
Or, if you only want to do this for certain modes:
;;; Only do this for the common C mode (C, C++, Objective-C)
(add-hook 'c-mode-common-hook #'(lambda () (set-face-foreground 'font-lock-comment-face "red")))
For more information on faces, see http://www.gnu.org/software/emacs/manual/html_node/emacs/Faces.html.
I'm not sure exactly how to fix it, but I'm fairly certain there's something you can put in the .emacs file. In fact, I think I've done that before. I'll look for my file and let you know what I can find.
I'll try and get you my .emacs file when I get home from work tonight.
[edit] I've looked and looked, and can't find a .emacs file on either system that I use, and on my OS X install (Leopard default), it looks like it does it correctly by default. I did some research here, and it looks like the default installations no longer use .emacs files, because there's folks like me that mess around with them and break things, and they got tired of having to help us fix it. But, there is a set of menus that will let you tweak things. Start by typing "M-x customize RET", where M is the meta character (on my OSX install, this is the esc key. Don't hold it down, just type it like a regular character. That'll get you into a menu of stuff you can change. I didn't poke around too much, so I'm not sure where in the menu you'll find what you're looking for. Sorry I couldn't be more help.
In my experience this is usually related to a unpaired quote (single-, double-, or otherwise) somewhere in an existing comment.
Hunt those occurences down and eradicate them in your source code (or if you are more ambitious, see if you can update the fontlock code in your major modes' emacs source code)
When I have encountered this in editting Perl in emacs, I often switch major modes to cperl-mode as it typically handles parsing the perl better than the default perl-mode.