elisp

Why does byte-compiling the the following produce a warning? (defmacro foomacro (shiftcode) `(defun foo (&optional arg) (interactive ,(concat shiftcode "p")) (message "arg is %i" arg)) `(defun bar (&optional arg) (interactive ,(concat shiftcode "Nenter a number: ")) (message "arg is %i" arg))) ;; provide backward compatibility for Emacs 22 (if (fboundp 'handle-shift-selection) (foomacro "^") (foomacro "")) This is the warning I get: $ emacs -Q --batch --eval '(byte-compile-file "foo.el")' In foomacro: foo.el:1:21:Warning: value returned from (concat shiftcode "p") is unused If I get rid of bar

I'm using (global-linum-mode t) to present line numbers in Emacs. This works just fine up-until I use the ctrl + up / down commands ( forward-paragraph and backward-paragraph ) to navigate a buffer, at which point some line numbers are rendered incorrectly (see attached image). This occurs only when I use said commands to skip entire segments of code, and the issue immediately disappears (the line numbers are rendered correctly, that is) if I start navigating the buffer by other means. The issue is present in both C and C++ modes (visualized), and I'm using Emacs 24.3.1 on x86-64 Fedora 19.

I was just typing in this sort of code for Nth time: menu.add_item(spamspamspam, "spamspamspam"); And I'm wondering if there's a faster way to do it. I'd like a behavior similar to yasnippet's mirrors, except I don't want to create a snippet: the argument order varies from project to project and from language to language. The only thing that's constant is the variable name that needs to be repeated several times on the same line. I'd like to type in menu.add_item($,"") and with the point between the quotes, call the shortcut and start typing, and finally exit with C-e . This seems advantageous

I'd like to create additional regular expressions for use with etags, but I'd like them to be based upon what's already there (in particular, I'd like to add [ \t]* to the current set of regular expressions that etags uses). What are the default set of regular expressions that etags uses for .lisp files? etags doesn't generally use regular expressions to implement the languages that are built-in. Instead, it has custom parser code for each built-in language. That said, it seems for Lisp to look for just a few forms, that could be handled by regular expressions: It looks for "(" in the first

For my global TODO list, I am showing breadcrumbs as suggested here : (concat \"[ \"(org-format-outline-path (org-get-outline-path)) \" ]\") ") to produce following: I would like to show only the second level of project breadcrumb. So in this case, I would only display [Project A] . I think if I can make a function that can extract the second level, I just need to prepend with %? so that [Tasks] does not appear for Tasks, but only project names would appear for Projects. What would be an ideal way of extracting the second level? All you have to do to get the second element of (org-get-outline

I am trying to find a package/function in emacs where it would have both files opened side by side to be at same line location mirroring the movement of whichever buffer is moving. Meaning, for two buffers opened side by side, moving in one of the buffers (page up/down, moving cursor.,..etc) would have the same movements in the other buffer. More specifically, when opening a buffer (and while activating this mode) the opened buffer should already be at the line position of the one that is already opened in the other buffer window. You could try scroll-all-mode . This switches on parallel