From: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Is that OK the way expand-abbrev moves point ?
Date: Sat, 25 Jul 2009 13:15:38 +0200 [thread overview]
Message-ID: <BLU104-W23A6EFF8687670F10ACDD784160@phx.gbl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
Dear EMACS experts
I am currently writing some VBScript code with http://www.emacswiki.org/cgi-bin/wiki/visual-basic-mode.el
I noticed that function visual-basic-newline-and-indent (mapped to <RET>) has a strange behaviour sometimes and this is due to the way expand-abbrev works. Here is the code:
(defun visual-basic-newline-and-indent (&optional count)
"Insert a newline, updating indentation."
(interactive)
(expand-abbrev)
(save-excursion
(visual-basic-indent-line))
(call-interactively 'newline-and-indent))
If for instance I type <RET> after (--!-- showing point when I type <RET>):
MyVar = MyFun(1,True)--!--
Then just after (expand-abbrev), point will be moved as follows:
MyVar = MyFun(1,True--!--)
because `True' is one abbreviation, so as a result I get this:
MyVar = MyFun(1,True
)
Which is unwanted.
I can solve this very easilly locally to visual-basic-mode.el, by pushing the (expand-abbrev) into the (save-excursion ...) but I was wondering whether this is an issue or not that expand-abbrev behave this way.
My emacs version 23.0.60.1 (i386-mingw-nt5.0.2195)
Best regards,
Vincent.
_________________________________________________________________
Téléphonez gratuitement à tous vos proches avec Windows Live Messenger ! Téléchargez-le maintenant !
http://www.windowslive.fr/messenger/1.asp
[-- Attachment #2: Type: text/html, Size: 1592 bytes --]
next reply other threads:[~2009-07-25 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 11:15 Vincent Belaïche [this message]
2009-07-26 14:09 ` Is that OK the way expand-abbrev moves point ? Stefan Monnier
2009-07-27 6:20 ` Vincent Belaïche
2009-07-27 6:23 ` Vincent Belaïche
2009-08-26 0:12 ` Vincent Belaïche
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BLU104-W23A6EFF8687670F10ACDD784160@phx.gbl \
--to=vincent.b.1@hotmail.fr \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.