The new advice system has the following advantages:
add-function: This is brand new functionality that simply was not part of defadvice. It is a kind of hybrid between add-hook and defadvice. In the future, expect more foo-function variables (modified via add-function) and less foo-functions (modified via add-hook). This functionality was the main ...
For #2, first you'll want to add a couple of keybindings to your init file (these are the suggested keys in the Org manual) -
(global-set-key (kbd "C-c l") 'org-store-link)
(global-set-key (kbd "C-c C-l") 'org-insert-link)
then you can hit C-c l somewhere in or on the item you want to link to, then C-c C-l where you want to place the link. It'll ask you to ...
If you provide the universal argument to replace-string, that is by pressing C-u before M-x replace-string, it only replaces matches that are surrounded by word boundaries.
So, for example, a buffer containing
would be become after C-u M-x replace-string RET mod RET off_mod
You can find this information by looking in the ...
One of the clear benefits of advice being normal functions is that you can visit a definition with find-function.
At present, when viewing the help for a (new-style) advised function, it provides a link to the help for the advice function, and from there a link to the source (as usual for function help).
The old system provided the advice docstring inline, ...
From the file header:
;; This package lets you add behavior (which we call "piece of advice") to
;; existing functions, like the old `advice.el' package, but with much fewer
;; bells and whistles.
As I read it, the primary goal is to be simpler than the old advice system, not to have more capabilities. Reading the docs, it seems that ...
The trunk of Emacs' git repository will be released as Emacs 25.1, whenever it is ready. But there is also a branch in git called emacs-24, which gets bug solutions. This might (or might not, who knows) end up in Emacs 24.5. Commits to emacs-24 are merged to trunk from time to time.
It is possible to split the frame's root window which encompasses both of your windows, thereby allowing you to add a third window at any side. There is no built-in command to do that though, so here's some example code to define commands for this particular task:
(defun my-split-root-window (size direction)
you can reference this topic http://orgmode.org/manual/External-links.html#External-links
file:projects.org::some words text search in Org file
file:projects.org::*task title heading search in Org file
sorry, I don't know your means.
May well be due to you're using the wrong emacsclient. I had the same (i.e.,
can't find socket and/or -error Unknown&_command:&_THEFILENAME
Turned out I used /usr/bin/emacsclient, whereas my emacs is actually ~/Applications/MacPorts/Emacs.app/Contents/MacOS/Emacs . Creating a symlink from ~/Applications/Emacs.app/Contents/MacOS/bin/emacsclient to a ...
Perhaps the prerelease versions you were building had the version number 24.4.50? That means that they're actually prerelease versions of 24.5, which was later renamed to 25.1 (but still not released at the time of this writing).
If so, you actually downgraded to the release version of 24.4, and thus lost this feature. I'm currently running 25.0.50, and ...
Since around Emacs-24, the vc-log buffer supports/expects an RFC822-style format, with some headers handled specially (e.g. Author:, Fixes:, and Summary:). In Emacs-24.4, the default message content was changed to make this more clear.
Package.el is a builtin package manager that can be used to install emacs packages.
Cask is an Emacs Lisp project management tool, similar to Maven or Leiningen. It aims to control and automate the entire life cycle of an Emacs Lisp package, including dependency management, packaging, distribution and testing. You can use Cask to manage your emacs your ...
Use ;; (or more) instead of ; and this won't happen.
What you're seeing is (in conjunction with electric-indent-mode) expected behaviour, as by convention
Comments that start with a single semicolon, ‘;’, should all be aligned to the same column on the right of the source code. Such comments usually explain how the code on that line does its job.
I suffered from the same situation.
Investigating in the configure.ac file reveals that the configure script in my case got the -lpng15 from the invocation of the libpng-config utility:
dnl Some systems, eg NetBSD 6, only provide eg "libpng16", not "libpng".
lpng=`libpng-config --libs 2> /dev/null`
case $lpng in
-l*) : ;;
*) lpng="-lpng" ;;
How to Debug?
It's tough to spot until you know what you're looking for, but in the middle of the stacktrace you see that the byte-compiled functions are calling python-shell-completion-get-completions.
You can step through this function with edebug to see what's happening, or you can appeal to divine inspiration to conclude that it ultimately sends the ...
I think I've found the problem and a work-around.
If you look at the python.el file, you will find this function to determine the path to the python executable:
(defun python-shell-parse-command () ;FIXME: why name it "parse"?
"Calculate the string used to execute the inferior Python process."
;; FIXME: process-environment doesn't seem to be used ...
The problem lies in the self compiled libjpeg-9.dll. It is solved by downloading dll files from ezwinports as recommended:
Emacs can also support some other image formats with appropriate
libraries. These libraries are all available on the following sites:
-- leaner, more up-to-date builds, only for ...
You have two choices:
Place all the associated libraries within the emacs\bin folder. This will allow them to be linked as needed
Place all associated libraries in a folder found on you %PATH%. I prefer doing it this way because it ensures that I keep the libraries in place following upgrades.
+- emacs\ (directory softlink to desired emacs ...
Might be that the package "s" was removed from emacs default packages or that you had it somehow installed on the previous version.
The package is available on the melpa repository.
Try this in your init.el (.emacs)
'("melpa" . "http://melpa.org/packages/") t)
Then use M-x ...
Many installations of emacs 24 have the AUCTeX package activated in the default set-up. The keybindings you are seeing come from that package, and you should look at its manual instead to find descriptions of them.
If you don't wish to use AUCTeX, then may be you can uninstall it by running list-packages and deleting the package. If not then may be https:...
To add to what @Malabarba said, I think the problem here is that smartparens should provide an API that does not rely on a macro.
The "normal" way this works with usual packages is that the major mode can just do something like:
(when (boundp 'smartparens-thingies)
(push mythingies smartparens-thingies))
(setq smartparens-extra-thingies ...
You'll notice that you're using a variable called auto-save-file-name-transforms. Since *scratch* has no filename, it falls back to autosaving in default-directory.
For the *scratch* buffer, or any other buffers like this with no filename, you can use:
(setq-local default-directory "~/.emacs.d/data/autosave")
Edit: I see that you don't really care about ...
It's surprising that there is no way to configure this. You can choose whether the Author: header should appear, but Summary: is jammed in by default no matter what.
I had to redefine a function:
(defun log-edit-insert-message-template ()
"Insert the default template."
(when (or (called-interactively-p 'interactive)
The easiest way to do this is to just manually update the colors for what you need. I suggest:
a. taking a look at all the helm faces: M-xcustomize-groupRET helm.
There you can browse to the one you want to customize, and just do it. (Read the description to find what every one is about.)
b. If you already know what you want to customize:
Is there a way to include this kind of "maybe evaluation" in a byte-compiled file, without confusing the byte-compiler? For example, is it possible to tell the compiler "do not compile this form"?
Yes, you can quote it and then eval it: (eval '(sp-whatever ...)). This will not be seen by the compiler and will only be expanded at runtime.
Or what would be ...
Found help on GitHub, here is what should be done when attempting at removing a property:
(set-face-attribute 'helm-selection nil :underline 'unspecified)
See the GitHub issue: https://github.com/emacs-helm/helm/issues/697#issuecomment-62362671.