From: Joe Kelsey <joe@zircon.seattle.wa.us>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: skeleton.el _ versus @, a new patch
Date: 24 Apr 2003 08:59:53 -0700 [thread overview]
Message-ID: <1051199987.572.9.camel@zircon> (raw)
In-Reply-To: <E198Vsa-0000lJ-00@fencepost.gnu.org>
On Wed, 2003-04-23 at 18:50, Richard Stallman wrote:
> The behavior I propose adds a new character whose only purpose is to
> provide an alternate method to set skeleton-point without interacting
> with regions at all. Therefore, the proposal I have made will set
> skeleton-point to the first occurrence of either - or _ while preserving
> the original semantics of both @ and _ otherwise.
>
> It seems logical. Are there skeletons that use - that might break
> with this change? (Is it meaningful to use - in a skeleton now? Is
> that an error?)
A skeleton is basically a list. Each element of the list is either a
string, a piece of lisp code, a sub-skeleton list or something to be
reinterpreted by skeleton-internal-1, basically anything that lisp
allows as a list member. The only reason a bare - would occur in an
existing skeleton is if someone was using it as a variable name for some
obscure purpoose. It is quite unlikely that any existing skeleton has
any bare -'s, the only use would be as parts of strings or character
constants using the usual lisp syntax for such.
/Joe
next prev parent reply other threads:[~2003-04-24 15:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 19:27 [joe@zircon.seattle.wa.us: skeleton.el _ versus @] Richard Stallman
2003-03-24 20:05 ` skeleton.el _ versus @ Stefan Monnier
2003-03-25 1:00 ` Joe Kelsey
2003-03-30 18:51 ` Joe Kelsey
2003-03-31 17:40 ` Stefan Monnier
2003-04-01 1:58 ` Joe Kelsey
2003-04-01 7:25 ` Miles Bader
2003-04-01 18:41 ` Stefan Monnier
2003-04-02 0:08 ` Joe Kelsey
2003-04-02 0:20 ` Stefan Monnier
2003-04-02 1:03 ` Joe Kelsey
2003-04-02 1:17 ` Thien-Thi Nguyen
2003-04-02 1:33 ` Stefan Monnier
2003-04-03 0:16 ` Joe Kelsey
2003-04-03 0:28 ` Miles Bader
2003-04-03 6:45 ` Daniel Pfeiffer
2003-04-09 16:26 ` Stefan Monnier
2003-04-10 0:00 ` Joe Kelsey
2003-04-10 22:47 ` Richard Stallman
2003-04-11 0:25 ` Joe Kelsey
2003-04-11 23:45 ` Richard Stallman
2003-04-11 23:59 ` Stefan Monnier
2003-04-12 0:11 ` Joe Kelsey
2003-04-12 8:51 ` Kai Großjohann
2003-04-13 11:23 ` Richard Stallman
2003-04-13 16:41 ` Stefan Monnier
2003-04-13 18:54 ` Kai Großjohann
2003-04-13 19:11 ` Joe Kelsey
2003-04-20 22:50 ` skeleton.el _ versus @, a new patch Joe Kelsey
2003-04-21 13:11 ` Stefan Monnier
2003-04-22 0:32 ` Joe Kelsey
2003-04-22 13:31 ` Stefan Monnier
2003-04-23 0:27 ` Joe Kelsey
2003-04-22 0:45 ` Richard Stallman
2003-04-22 1:30 ` Joe Kelsey
2003-04-24 1:50 ` Richard Stallman
2003-04-24 15:59 ` Joe Kelsey [this message]
2003-04-26 2:31 ` Richard Stallman
2003-04-28 21:51 ` Stefan Monnier
2003-04-29 19:29 ` Richard Stallman
2003-05-18 1:31 ` Joe Kelsey
2003-04-02 19:26 ` skeleton.el _ versus @ Richard Stallman
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=1051199987.572.9.camel@zircon \
--to=joe@zircon.seattle.wa.us \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
/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).