Search Results

Search found 4 results on 1 pages for 'emacs24'.

Page 1/1 | 1 

  • Emacs24: emacsclient doesn't use global application menu

    - by codethief
    I noticed that Emacs24 makes use of Unity's global application menu. (I'm using Damien Cassou's Emacs24 snapshots.) However, it doesn't do that when emacs, emacsclient or emacsclient.emacs24 are run but just with emacs24. How can I fix that? (Is that a bug? If so, should I file a report in Emacs' or libappmenu's bugtracker?) [EDIT]: As far as I can see this could be related to https://bugs.launchpad.net/ubuntu/+source/appmenu-gtk/+bug/673302 .

    Read the article

  • Low-res emacs24 icon in application switcher 12.10

    - by MTS
    I recently upgraded to Quantal, and also switched up to emacs24 from 23. Everything is great, except for one thing: the icon in the Application Switcher for emacs24 is a horrible, low-resolution eyesore. Compare the two side-by-side: I've seen a couple of questions addressing issues like this, but they're not quite the same. This one says that it is happening with all icons, but that's clearly not the case here. And this one seems more relevant, but it is talking about Gnome, not Unity. In the comments to the one answer for the second question, it says to look at the icons in /usr/share/icons to see if they are low-resolution, and if so to replace them with better ones. There's a ton of emacs icons, in fact. They are in various subfolders of /usr/share/icons/hicolor and they are in sizes ranging from 16x16 to 128x128, and also there are scaleable .svg versions of the icons too. I noticed that there are no 192x192 or 256x256 versions. But it seems like that shouldn't matter, since emacs23 also didn't have icons in those sizes. Any help would be much appreciated!

    Read the article

  • Cannot load viper-mode in Emacs24

    - by Andrew-Dufresne
    Every time I try to load viper-mode in Emacs24 using M-x viper-mode, I get error Wrong type argument: symbolp, (quote 3) I have observed it happens when I try to load viper-mode for the after opening Emacs or after I have issued M-x viper-go-away So once I get this error and run the same command again, viper-mode loads successfully. When I use toggle-viper-mode to turn it off, viper-mode goes away successfully. But when I try to turn it back on using toggle-viper-mode again, I get the above stated error. I have to use viper-go-away and then M-x viper-mode twice to get it back working. How can I get rid of this error?

    Read the article

  • Any tips on switching from bash to zsh if often using shell inside of emacs?

    - by justingordon
    Related to this question: Advantages and disadvantages between zsh and emacs' (e)shell, I've read some great things about zsh, when using M-x shell, my familiar emacs shell seemed like it would need some customizations. I also use evil-mode in shell mode, so that means I use vi keystrokes for shell editing. Took a little while to get accustomed to this, but I really like it. Any advice or tips on going from bash to zsh if one uses emacs? Or better off adding the file completion mentioned in this question: Worth switching to zsh for casual use?.

    Read the article

1