So like other Agda enthusiasts, with the release of the new version of Agda, I quickly cabal-force-installed the latest and greatest. However, after compiling and setting-up agda-mode (the new one), my emacs is giving me some strange settings.
I no longer have an include dirs menu when I attempt to customize agda, I've circumvented this by using the program args menu and adding --include-dir=<stuff>. However, the colour scheme is bothersome. In a literate agda file, everything outside of \begin{code} and \end{code} is coloured salmon-red and I want it to be black as was in older versions.
I've played around with the highlight settings, but just could not get this to change. Any advice would be most appreciated!
Thank-you!
Edit : the removal of the include-dirs is no error, the change log under the emacs section mentions this and more.
Related
Where did my VSCode indent guides go?
As best as I can recall, indent guides were working as advertised in VSCode 1.17.2 on my MacBook Pro (macOS Sierra 10.12.6 (16G29)) a few hours ago. Now, with no change to any settings and without closing/reopening the editor, I notice that they're no longer rendering. I checked multiple file formats and none of them work.
I checked editor.renderIndentGuides. It's defaulted to true, and isn't being forced to false anywhere, confirmed by noting that vscode.workspace.getConfiguration("editor")["renderIndentGuides"] evaluates to true).
One minor oddity I noticed was that the settings editor itself was correctly showing indent guides until I restarted VSCode and now it's broken too.
After noticing the problem, I briefly installed the Guides extension to see if it would make things any better. It worked, but I found its appearance slightly too in-your-face and didn't need any of the special bits (in which case the Guides README recommends not to use it) so I removed it, after which guides are again not rendering. If nothing else works, I'll reinstall Guides and see if I can tweak it to suit, but I'd rather just have VSCode work as intended.
I narrowed the problem down slightly to the MBP's built-in retina display. When I run on a non-retina external screen, I see the guides. However, even there, I noticed that playing with indentation level settings causes the guides to break up a little and I have to close and reopen the file to restore order.
I figured out the proximate cause. Setting the font too small (< 12pt) produces aliasing on thin (presumably 1-pixel) lines.
A non-retina external screen exhibits similar behaviour, though it requires smaller fonts. Also, while both screens have trouble with rulers, only the retina screen loses the guides.
I've just tried IntelliJ IDEA 12 with the Scala plugin, but it doesn't find and highlight errors in my code. I can for example write arbitrary code in a method and it looks like everything is fine. Is IDEA not able to do this? Or do I have to configure something special?
IDEA's Scala plug-in is not equivalent to the compiler in type-checking your source code, but it does pretty well. The one thing you'll want to do (unless, perhaps, your hardware is not fairly current and high-performance) is turn on "Type-Aware Highlighting."
If you look in the lower-right-hand corner of the IDEA window (when you're editing a project with Scala enabled) you'll see one of two icons, both of which take the form of a square-bracketed bit of text. That text is either blank on a yellow background or the letter T on a green background. Clicking it toggles between those two states. When the green T is displayed, Type-Aware highlighting is on.
Give that a try.
Simply updating the plugin version could fix the problem. Old or install/initial plugins may not contain relevant support.
Determining Scala plugin version in Settings:
I have an issue after switching to running Ubuntu when developing instead of Windows.
When I ran Eclipse in Windows, I could find the software market thing and get good and easy-to-use color themes from there to install. Since I couldn't find anything of this on my Ubuntu version, I decided to edit it all manually.
Here is my issue: I was able to adjust the color of the 'mark occurrences'-function that highlights all the all the places where a code piece occurs, but my program does something else to the place where variables are first declared. I took a simple screen shot that displays the problem:
http://www.freeimagehosting.net/19e90
When I disable 'mark occurrences', the super-bright highlighting on variable declarations do not go away, so it's not part of the same setting. I also can't find where I change the color of this, because it's quite annoying not to be able to read what's written due to the coloring of that highlight.
Do you know how I can disable this extra-marking of declarations? Or at least change the color of it? I can't find anything when googling it, but maybe I'm just searching for the wrong things.
Thanks in advance and sorry for this very long post!
I would recommend installing a new version of Eclipse on Ubuntu.
I'm developing on Kubuntu and have no issues. Make sure you delete all previous settings before reinstalling. Default settings should have them enabled.
I have used succesfully used for some time
GNU Emacs 23.1.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.0)
on Ubuntu 9.10. With all kinds of plugins and additions.
Now I have installed a completely new Ubuntu, that's 11.04, and I installed most of the emacs and related emacs plugins with apt-get.
This is what I have installed.
i A emacs23 - The GNU Emacs editor (with GTK+ user interface)
i A emacs23-bin-common - The GNU Emacs editor's shared, architecture dependent files
i A emacs23-common - The GNU Emacs editor's shared, architecture independent infrastructure
v emacs23-gtk -
i A emacsen-common
And my version now is:
GNU Emacs 23.2.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.4)
of 2011-04-04 on crested, modified by Debian
The problem is, that on when I enter any mode (css, sgml, org, sql, c, text, etc), whatever menus I have between Tools and Help do not show. So the main menu item shows (like SQL in sql mode), but when I mouseover it, it does not contain any items.
First, I thought is one of the *.el files I have in my .emacs.d or I blame it on pymacs rope ropemode ropemacs etc. But then I deleted all from my .emacs file and my .emacs.d folder and I have the same strange thing.
What is extremely weird, is that sometimes, I don't know how, when I start emacs, the problem is gone. This is like one in 50 tries. I first thought I did something (like when I uninstalled magit), and blame it on that. But then I closed and opened my emacs again, without modifying anything and the menus were broken again.
No that I installed back my .emacs .emacs.d and my plugins, since it's not their fault, I have for example on scratch buffer a Lisp-Interaction menu beginning with "Complete Lisp symbol" and then a YASnippet empty menu.
If I switch to a .py file, the first menu after the Tools menu is IM-Python, which in fact has the sub-menu items that Lisp-Interaction menu has. So when I hover on IM-Python I get "Complete Lisp Symbol", "Indent-or-Pretty print", etc. and then the rest of menus Python, Yasnippet, Rope are empty. And the last menu, Help, is good again.
I really don't know what should I try more, or how to go further and debug, I've been fighting with it for hours.
PS: oh yeah, so now I discovered an answer on stackoverflow for a similar issue, so when I hit F10 (menu-bar-open) the menu fixes, the submenu items appear correctly.
But when I open a new file and want to use the menu again, it's broken and have to hit F10 again and it works. So it's not so bad after all :) but anyway, if you have a clue please let me know.
Thanks,
Stefan
Try and duplicate the issue with a plain-vanilla emacs. To do that, startup emacs like this:
$ emacs -q --no-site-init
It should work as expected. If it does, then make a copy of your .emacs file and in the copy, delete half of it, then restart emacs normally. If the problem is there, then cut down your .emacs by half again; if it's not there, startup with the other half of the original .emacs file. Lather, rinse, repeat until you find the offending code that mucks everything up.
If it does not work when emacs -q --no-site-init is called, then there's something wonky going on in the interaction between your emacs binary and the window manager, which will be a lot tougher to track down.
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.