emacs-diffs
[Top][All Lists]
Advanced

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

[Emacs-diffs] emacs-24 r117285: More tweaks of skeleton documentation wr


From: Eli Zaretskii
Subject: [Emacs-diffs] emacs-24 r117285: More tweaks of skeleton documentation wrt \n behavior at bol/eol.
Date: Sun, 22 Jun 2014 17:01:08 +0000
User-agent: Bazaar (2.6b2)

------------------------------------------------------------
revno: 117285
revision-id: address@hidden
parent: address@hidden
committer: Eli Zaretskii <address@hidden>
branch nick: emacs-24
timestamp: Sun 2014-06-22 19:59:30 +0300
message:
  More tweaks of skeleton documentation wrt \n behavior at bol/eol.
  
   lisp/skeleton.el (skeleton-insert): Yet another fix of the doc string
   wrt behavior of \n as the first/last element of a skeleton.
  
   doc/misc/autotype.texi (Skeleton Language): Document the \n feature
   better.
modified:
  doc/misc/ChangeLog             changelog-20091113204419-o5vbwnq5f7feedwu-6331
  doc/misc/autotype.texi         
autotype.texi-20091113204419-o5vbwnq5f7feedwu-6289
  lisp/ChangeLog                 changelog-20091113204419-o5vbwnq5f7feedwu-1432
  lisp/skeleton.el               skeleton.el-20091113204419-o5vbwnq5f7feedwu-728
=== modified file 'doc/misc/ChangeLog'
--- a/doc/misc/ChangeLog        2014-06-21 08:05:39 +0000
+++ b/doc/misc/ChangeLog        2014-06-22 16:59:30 +0000
@@ -1,3 +1,8 @@
+2014-06-22  Eli Zaretskii  <address@hidden>
+
+       * autotype.texi (Skeleton Language): Document the \n feature
+       better.
+
 2014-06-21  Eli Zaretskii  <address@hidden>
 
        * autotype.texi (Skeleton Language): Document the feature of \n

=== modified file 'doc/misc/autotype.texi'
--- a/doc/misc/autotype.texi    2014-06-21 15:08:18 +0000
+++ b/doc/misc/autotype.texi    2014-06-22 16:59:30 +0000
@@ -234,9 +234,10 @@
 @c ??? something seems very wrong here.
 Insert a newline and align under current line, but not if this is the
 last element of a skeleton and the newline would be inserted at end of
-line.  Use newline character @code{?\n} to prevent alignment.  Use
address@hidden"\n"} as the last string element of a skeleton to insert a
-newline after the skeleton unconditionally.
+line, or this is the first element and the newline would be inserted
+at beginning of line.  Use newline character @code{?\n} to prevent
+alignment.  Use @code{"\n"} as the first or last string element of a
+skeleton to insert a newline unconditionally.
 @item @code{_}
 Interesting point.  When wrapping skeletons around successive regions, they are
 put at these places.  Point is left at first @code{_} where nothing is wrapped.

=== modified file 'lisp/ChangeLog'
--- a/lisp/ChangeLog    2014-06-22 09:20:38 +0000
+++ b/lisp/ChangeLog    2014-06-22 16:59:30 +0000
@@ -1,3 +1,8 @@
+2014-06-22  Eli Zaretskii  <address@hidden>
+
+       * skeleton.el (skeleton-insert): Yet another fix of the doc string
+       wrt behavior of \n as the first/last element of a skeleton.
+
 2014-06-22  Michael Albinus  <address@hidden>
 
        * net/tramp-adb.el (tramp-adb-handle-process-file):

=== modified file 'lisp/skeleton.el'
--- a/lisp/skeleton.el  2014-06-21 13:41:44 +0000
+++ b/lisp/skeleton.el  2014-06-22 16:59:30 +0000
@@ -200,8 +200,9 @@
 If ELEMENT is a string or a character it gets inserted (see also
 `skeleton-transformation-function').  Other possibilities are:
 
-       \\n     if not the last element of the skeleton, or not at eol,
-                go to next line and indent according to mode
+       \\n     go to next line and indent according to mode, unless
+                this is the first/last element of a skeleton and point
+                is at bol/eol
        _       interesting point, interregion here
        -       interesting point, no interregion interaction, overrides
                interesting point set by _
@@ -218,7 +219,8 @@
 
 Note that \\n as the last element of the skeleton only inserts a
 newline if not at eol.  If you want to unconditionally insert a newline
-at the end of the skeleton, use \"\\n\" instead.
+at the end of the skeleton, use \"\\n\" instead.  Likewise with \\n
+as the first element when at bol.
 
 Further elements can be defined via `skeleton-further-elements'.
 ELEMENT may itself be a SKELETON with an INTERACTOR.  The user is prompted


reply via email to

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