From: Lars Ingebrigtsen <larsi@gnus.org>
To: Nicolas Richard <youngfrog@members.fsf.org>
Cc: 20780@debbugs.gnu.org
Subject: bug#20780: 25.0.50; explain where to find skeletons in autotype info manual
Date: Wed, 09 Oct 2019 05:46:29 +0200 [thread overview]
Message-ID: <878spuvawa.fsf@gnus.org> (raw)
In-Reply-To: <86eglkvlc8.fsf@members.fsf.org> (Nicolas Richard's message of "Tue, 09 Jun 2015 19:32:39 +0200")
Nicolas Richard <youngfrog@members.fsf.org> writes:
> I was trying to find a template/skeleton mechanism, and that leads to
> (info "(emacs) Text") :
>> The “automatic typing” features may be useful when writing text.
>> *note The Autotype Manual: (autotype)Top.
>
> Following through to the autotype info page, I'm a bit disappointed
> because the manual explains how skeletons can:
> - accept input in section 1,
> - be modified with prefix arguments in section 2,
> - be called as abbrevs in section 3,
> and we have to wait section 4 to read about a (quite scary,
> IMO) way to define skeletons. I'm now convinced that it is in fact not
> expected that the *user* writes her own skeletons. Is that right ?
I think that's right.
> If that is the case, I suggest to mention that fact right from the
> beginning, and maybe explicitly list a few places where skeletons are
> actually availables (which key). C-mode is mentionned but from "emacs -Q
> -f c-mode" I couldn't find anything in the menu.
I wonder why the autotype manual is linked from the Emacs manual at
all. It's a very low-level (lispref-like) manual, and doesn't really
seem to be something we should steer users towards?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-09 3:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 17:32 bug#20780: 25.0.50; explain where to find skeletons in autotype info manual Nicolas Richard
2019-10-09 3:46 ` Lars Ingebrigtsen [this message]
2019-10-09 17:11 ` Eli Zaretskii
2019-10-09 17:44 ` Lars Ingebrigtsen
2019-10-09 18:05 ` Eli Zaretskii
2019-10-09 18:08 ` Lars Ingebrigtsen
2019-10-09 22:07 ` Nicolas Richard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-10-11 7:44 ` Lars Ingebrigtsen
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=878spuvawa.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=20780@debbugs.gnu.org \
--cc=youngfrog@members.fsf.org \
/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).