From: Lars Ingebrigtsen <larsi@gnus.org>
To: David Casperson <casper@unbc.ca>
Cc: David Casperson <David.Casperson@unbc.ca>, 26089@debbugs.gnu.org
Subject: bug#26089: 25.1; Faulty documentation for skeleton-end-newline
Date: Fri, 26 Jul 2019 14:09:08 +0200 [thread overview]
Message-ID: <87ftmtm1zv.fsf@mouse.gnus.org> (raw)
In-Reply-To: <alpine.OSX.2.00.1703131209100.78394@pg4460-a38900.local> (David Casperson's message of "Mon, 13 Mar 2017 12:11:32 -0700 (PDT)")
David Casperson <casper@unbc.ca> writes:
> The documentation for skeleton-end-newline says:
>
> "...This just influences the way the default `skeleton-end-hook' behaves."
>
> but in fact skeleton-end-newline is used in
> (or (eolp) (not skeleton-end-newline) (newline-and-indent))
> in the function `skeleton-insert’ OUTSIDE of skeleton-end-hook (which
> is, by default nil).
>
> To witness behaviour contrary to the documentation, run latex-mode and
> call M-x latex-insert-block itemize with the cursor at the beginning of
> a non empty line. There will be a blank line after the \end{itemize}.
> This differs from previous emacs versions.
Looks like this was fixed for Emacs 26:
commit 88cdf14b37a7344bb266e94512485e3cc738c23d
Author: Noam Postavsky <npostavs@gmail.com>
Date: Mon Dec 19 19:49:47 2016 -0500
Improve skeleton docstrings
* lisp/skeleton.el (skeleton-end-newline): Remove mention of
`skeleton-end-hook', its default code was moved into `skeleton-insert'.
(skeleton-insert): Mention `skeleton-end-newline' and move reference to
`skeleton-end-hook' above the explanation of skeleton syntax.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-07-26 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 19:11 bug#26089: 25.1; Faulty documentation for skeleton-end-newline David Casperson
2019-07-26 12:09 ` Lars Ingebrigtsen [this message]
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=87ftmtm1zv.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=26089@debbugs.gnu.org \
--cc=David.Casperson@unbc.ca \
--cc=casper@unbc.ca \
/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).