From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Properly indenting a defun (sexp tips)
Date: Sun, 15 Oct 2006 17:16:25 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICKEBADJAA.drew.adams@oracle.com> (raw)
In-Reply-To: <slrnej5cdc.ptd.tim@linus.johnson.com>
I have a piece of code that looks like this:
;; code:
(defun mu-modifier-char ()
"Create colorized modifier symbol"
(interactive)
(let (my-char)
(save-excursion
(backward-char 1)
(setq my-char (char-at))
(cond ((member my-char mu-modifiers)
(upcase my-char)
)
)
)))
;; And I want it to look like this
(defun mu-modifier-char ()
"Create colorized modifier symbol"
(interactive)
(let (my-char)
(save-excursion
(backward-char 1)
(setq my-char (char-at))
(cond ((member my-char mu-modifiers)
(upcase my-char))))))
;; that is, properly indented per emacs-lisp-mode
Is there a single command to do this?
If not, being pointed to pertinent documentation
and URLs to discussions on this topic would be
most welcome.
I don't believe so. But if you want to do this in Lisp, then you might make
use of function `fixup-whitespace', calling it at appropriate places.
Another thing you might try if working in Lisp, is using a pretty-print
function on the (uncompiled) function definition. `symbol-function' will
probably do what you want here. Then just substitute the function name for
`lambda'. This will lose any comments, however.
It all depends on how much you need to do this, and whether you are doing it
by program or interactively. If working interactively, and there are only a
few examples and they are all like this one (with just extra whitespace
before right parens), what I would do is get rid of the lines at the end
that have just parens (`C-k'), and then add parens at the end of your
function until a paren matches the opening paren around `defun'.
If you are working interactively and there are lots of such examples, but
all are similar to this one (just extra whitespace), I'd define a command
that calls `fixup-whitespace' at the right places. Or I'd bind
`fixup-whitespace' to a key and then use a keyboard macro that searches for
the extra whitespace.
Here are some things that can help with matching up parentheses, though you
are probably already aware of them:
- Library `paren.el' helps a lot with parenthesis matching. Turn on
parenthesis highlighting with (show-paren-mode 1) in your .emacs. You can
customize variable `show-paren-style' and face `show-paren-match-face'.
- Another parenthesis-highlighting library, which I don't happen to use, is
`mic-paren.el'.
- In addition to paren highlighting, setting variable `blink-matching-paren'
to non-nil causes the matching left parenthesis to flash when you insert a
right parenthesis.
See the Emacs manual, node Matching, for more information on matching
parens.
next prev parent reply other threads:[~2006-10-16 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 22:40 Properly indenting a defun (sexp tips) Tim Johnson
2006-10-16 0:16 ` Drew Adams [this message]
2006-10-16 0:39 ` Dieter Wilhelm
2006-10-16 1:12 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DNEMKBNJBGPAOPIJOOICKEBADJAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).