[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

backward-sexp and insert-parentheses are lacking for Common Lisp

From: Hannu Koivisto
Subject: backward-sexp and insert-parentheses are lacking for Common Lisp
Date: Tue, 03 Dec 2002 16:59:42 +0200
User-agent: Gnus/5.090007 (Oort Gnus v0.07) Emacs/21.2 (i686-pc-linux-gnu)

This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.

In GNU Emacs 21.2.2 (i686-pc-linux-gnu, X toolkit)
 of 2002-03-26 on lynx
configured using `configure  --prefix=/usr/local/emacs-21 --with-xpm 
--with-jpeg --with-tiff --with-gif'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: fi_FI@euro
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: nil
  locale-coding-system: iso-latin-9
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

Assuming that point is right after the closing paren of #(1 2), for
example, backward-sexp moves the point right before the #
character.  It does not, however, move the point before the first
character of the following example Common Lisp forms in a buffer in
lisp-mode: #c(1 2) #2(1 2) #1a(1 2).  It should do that, in my
opinion.  Full description of the syntax pertaining to those
examples can be found at

Also, when parens-require-spaces is non-nil, insert-parentheses
should not insert space after #c, #2 and #1a in the given examples.

Considering that lisp-mode may be used to edit something else than
Common Lisp, it would be sufficient at least for me if the proper
behaviour could be achieved with a configuration toggle of some
sort.  Or maybe it would be best to introduce common-lisp-mode?
This way people wouldn't need to always set lisp-indent-function to
common-lisp-indent-function and they could do CL-specific
customizations in that mode's hook, for example.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]