From: Joe Kelsey <joe@zircon.seattle.wa.us>
Cc: mmm-mode-discuss@lists.sourceforge.net
Subject: skeleton.el _ versus @
Date: 23 Mar 2003 23:55:35 -0000 [thread overview]
Message-ID: <20030323235535.31292.qmail@zircon.seattle.wa.us> (raw)
In GNU Emacs 21.2.1 (i386--freebsd, X toolkit, Xaw3d scroll bars)
of 2002-11-08 on zircon.zircon.seattle.wa.us
skeleton.el confuses the roles of _ and @.
_ serves two purposes: mark the "interesting" skeleton-point, and mark
region-skip points, depending on whether or not the skeleton is being
inserted in a plain context, or in a "region" context.
@ serves as a "back-up" setting for skeleton-point and also to mark the
skeleton-positions.
My contention is that the use of @ as a backup to _ in setting
skeleton-point is incorrect. When a skeleton contains both @ and _
markers, obviously the _ should be used to set the skeleton-point and
the @ should be used to set skeleton-positions when the skeleton is used
in simple insertion mode.
When the skeleton is used in region-list-context mode, there must be
multiple occurrences of _ to mark where the insertion code is supposed
to skip to the end of the next region. In this case, there probably
aren't any @ markers. The first _ can serve as skeleton-point.
If a simple skeleton is used without any _ markers, then the user hasn't
thought about where they want point to end up and it doesn't really
matter where it ends up.
I propose the following modification to skeleton.el:
--- lisp/skeleton.el.orig Sat Jul 14 04:21:08 2001
+++ lisp/skeleton.el Sun Mar 23 15:28:03 2003
@@ -453,8 +453,7 @@
((eq element '|)
(unless skeleton-modified (pop skeleton)))
((eq element '@)
- (push (point) skeleton-positions)
- (unless skeleton-point (setq skeleton-point (point))))
+ (push (point) skeleton-positions))
((eq 'quote (car-safe element))
(eval (nth 1 element)))
((or (stringp (car-safe element))
Basically, this removes the setting of skeleton-point from the @
actions.
/Joe
reply other threads:[~2003-03-23 23:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030323235535.31292.qmail@zircon.seattle.wa.us \
--to=joe@zircon.seattle.wa.us \
--cc=mmm-mode-discuss@lists.sourceforge.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).