10:04 a.m.
Hi,
I am writing a minor mode for having "holes" in your buffer that you can
fill by different means. I would like to interface it with skeletons, and I
am not able to get interesting positions after a skeleton has been
inserted. In Emacs there is this variable 'skeleton-position which is made
for this (added recently it seems). Moreover one can define in the skeleton
what are the positions which should be added to this variable.
My question is: is it possible to have such a variable also in XEmacs
please?
Sorry if this is not the right list for this kind of question.
Pierre Courtieu
12:04 p.m.
Pierre Courtieu <Pierre.Courtieu(a)univ-orleans.fr> writes:
Hi,
I am writing a minor mode for having "holes" in your buffer that you can
fill by different means. I would like to interface it with skeletons, and I
am not able to get interesting positions after a skeleton has been
inserted. In Emacs there is this variable 'skeleton-position which is made
for this (added recently it seems). Moreover one can define in the skeleton
what are the positions which should be added to this variable.
My question is: is it possible to have such a variable also in XEmacs
please?
Take a look at mcskels.el package, and how it defines/jumps to
interesting positions. Basically there is only one interesting
position after skeleton is inserted - and point jumps to it. However
mcskels.el has functionality which allows you to jump over numerous
interesting positions. As an example, suppose you want to insert
if-else C statement:
M-x mc-insert-stat-complete RET if-else RET
It will insert:
if ( [0] ) {
[1]
} else {
[2]
}
And write to minibuffer - 'Marks set: 3, use C-u C-SPC to jump next.'
[0], [1] and [2] - are not text - they are interesting point position
- [0] is default interesting position where point jump after skeleton
is insreted.
Once you've have entered some text at [0] and pressed C-u C-SPC - it
will jump to [1] position, once you've finished with [1] and pressed
C-u C-SPC - it will jump to [2] position.
Hope this is what you are looking for.
--
lg
12:08 p.m.
On 24 fév 2005, Zajcev Evgeny wrote:
Take a look at mcskels.el package, and how it defines/jumps to
...
It will insert:
if ( [0] ) {
[1]
} else {
[2]
}
And write to minibuffer - 'Marks set: 3, use C-u C-SPC to jump next.'
Hope this is what you are looking for.
This is exactly what I was looking for. Thanks a lot!
--
Pierre Courtieu
1:02 p.m.
On 24 fév 2005, Pierre Courtieu wrote:
> It will insert:
>
> if ( [0] ) {
> [1]
> } else {
> [2]
> }
>
> And write to minibuffer - 'Marks set: 3, use C-u C-SPC to jump next.'
> Hope this is what you are looking for.
This is exactly what I was looking for. Thanks a lot!
Well, after looking at it, specially to this kind of definition:
(defvar mc-if-skel
'(nil
"if (" _ ") {" \n
'(progn (mc-push-mark) nil) \n
"}" '(progn (indent-according-to-mode) nil) \n
'(progn (mc-push-mark) nil)
nil)
"*Skeleton for if statement")
I still think that adding the '＠' as a special marker telling "store this
position into skeleton-position" is a good idea. For example the above
statement becomes.:
(defvar mc-if-skel
'(nil
"if (" _ ") {" \n > ＠ \n > "}"
'(progn (indent-according-to-mode) nil) \n > ＠
nil)
"*Skeleton for if statement")
Then you can use add a hook skeleton-end-hook to store those positions in
mark-stack if you want (I plan to make another hook building a "hole" at
each position).
Moreover why do you need indent-according-to-mode? replacing it by >
wouldn't be the same?
Anyway thanks for the quick answer.
--
Pierre Courtieu
1:38 p.m.
Pierre Courtieu <Pierre.Courtieu(a)univ-orleans.fr> writes:
On 24 fИv 2005, Pierre Courtieu wrote:
> > It will insert:
> >
> > if ( [0] ) {
> > [1]
> > } else {
> > [2]
> > }
> >
> > And write to minibuffer - 'Marks set: 3, use C-u C-SPC to jump next.'
> > Hope this is what you are looking for.
>
> This is exactly what I was looking for. Thanks a lot!
Well, after looking at it, specially to this kind of definition:
(defvar mc-if-skel
'(nil
> "if (" _ ") {" \n
> '(progn (mc-push-mark) nil) \n
> "}" '(progn (indent-according-to-mode) nil) \n
> '(progn (mc-push-mark) nil)
nil)
"*Skeleton for if statement")
I still think that adding the '＠' as a special marker telling "store this
position into skeleton-position" is a good idea. For example the above
statement becomes.:
(defvar mc-if-skel
'(nil
> "if (" _ ") {" \n > ＠ \n > "}" '(progn
(indent-according-to-mode) nil) \n > ＠
nil)
"*Skeleton for if statement")
Then you can use add a hook skeleton-end-hook to store those positions in
mark-stack if you want (I plan to make another hook building a "hole" at
each position).
Definitely! Tottally agree that skeleton must have builtin support
for saving interesting points. However mcskels just shows how to
workarond when skeleton have no such support.
Moreover why do you need indent-according-to-mode? replacing it by >
wouldn't be the same?
For some reason > won't work for indenting empty lines, it might be a
xemacs specific issue - or might be skeleton bug/feature. So
inserting skeleton like this:
'(nil
"if (" _ ") {" \n > ＠ \n > "}" \n
> ＠
nil)
I'm having something like:
if ( [0] ) {
[1]
}
[2]
i.e. [1] is placed incorectly. I have not actually looked deeply why
this happening. If you will find something regarding this issue -
please let me know.
Thanks!
--
lg
6:08 p.m.
>>>> "Zajcev" == Zajcev Evgeny
<zevlg(a)yandex.ru> writes:
Zajcev> Pierre Courtieu <Pierre.Courtieu(a)univ-orleans.fr> writes:
> On 24 fév 2005, Pierre Courtieu wrote:
...
> (defvar mc-if-skel
> '(nil
> > "if (" _ ") {" \n > ＠ \n > "}" '(progn
(indent-according-to-mode) nil) \n > ＠
> nil)
> "*Skeleton for if statement")
>
> Then you can use add a hook skeleton-end-hook to store those positions in
> mark-stack if you want (I plan to make another hook building a "hole" at
> each position).
Zajcev> Definitely! Tottally agree that skeleton must have builtin support
Zajcev> for saving interesting points. However mcskels just shows how to
Zajcev> workarond when skeleton have no such support.
I believe that tempo mode provides this functionality.
Chuck
--
Charles K. Hines <ckh(a)requesttech.com> <chuck.hines(a)baesystems.com>
Principal Scientist at ReQuest Technologies Inc. (http://www.ReQuestTech.com/)
"When things don't sound evil enough on their own I like to toss in
a BU-WHA-HA-HA-HA". - Catbert (from Dilbert)
10:58 a.m.
On 24 fév 2005, Charles Hines wrote:
I believe that tempo mode provides this functionality.
Interesting, is it distributed in standard (X)Emacsen? I am trying to write
a minor mode only using standard fetaure of (X)emacsen.
Actually this mode is really redundant with skeletons (but maybe it is
better?).
--
Pierre Courtieu
3:06 p.m.
>>>> "Pierre" == Pierre Courtieu
<Pierre.Courtieu(a)univ-orleans.fr> writes:
Pierre> On 24 fév 2005, Charles Hines wrote:
> I believe that tempo mode provides this functionality.
Pierre> Interesting, is it distributed in standard (X)Emacsen? I am trying to
Pierre> write a minor mode only using standard fetaure of (X)emacsen.
It's almost as standard as skeleton.el, I guess, since they are both in
packages. It looks like you can find tempo as part of the edit-utils package
while skeleton is part of xemacs-base.
Let me check Emacs 21.3...yup, it appears to be there too.
Pierre> Actually this mode is really redundant with skeletons (but maybe it is
Pierre> better?).
Maybe. I heard of tempo first (html-helper-mode uses it) and was a little
confused when I heard of skeleton mode later since they did seem to be
somewhat redundant (at least at the high level). But the comments in tempo
lead one to believe that it might be more powerful.
Chuck
--
Charles K. Hines <ckh(a)requesttech.com> <chuck.hines(a)baesystems.com>
Principal Scientist at ReQuest Technologies Inc. (http://www.ReQuestTech.com/)
"When things don't sound evil enough on their own I like to toss in
a BU-WHA-HA-HA-HA". - Catbert (from Dilbert)
7239
days inactive
7240
days old
7 comments
3 participants
participants (3)
-
Charles Hines -
Pierre Courtieu -
Zajcev Evgeny