all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 33443-done@debbugs.gnu.org
Subject: bug#33443: 26; Doc of Edit Abbrevs mode
Date: Fri, 23 Nov 2018 12:20:59 +0200	[thread overview]
Message-ID: <83y39kf62c.fsf@gnu.org> (raw)
In-Reply-To: <ad7a45e6-d8ff-4ff1-8efa-25d7ffc524e9@default> (message from Drew Adams on Tue, 20 Nov 2018 08:54:08 -0800 (PST))

> Date: Tue, 20 Nov 2018 08:54:08 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> 
>  Edit-Abbrevs mode defined in `abbrev.el' (`edit-abbrevs-mode'):
>  Major mode for editing the list of abbrev definitions.
> 
>  This mode runs the hook `edit-abbrevs-mode-hook', as the final or penultimate step
>  during initialization.
> 
>  key             binding
>  ---             -------
> 
>  C-c             Prefix Command
>  C-x             Prefix Command
> 
>  C-c C-c         edit-abbrevs-redefine
> 
>  C-x C-s         abbrev-edit-save-buffer
>  C-x C-w         abbrev-edit-save-to-file
> 
> [One of those help lines is 82 chars long, BTW.]

Yes.

> You have to roam around in the source file a bit to find out what you're
> looking at and what you can do with it.  In particular, the doc of
> `edit-abbrevs' tells you what you're looking at and what you can do with
> what you're looking at. It is...

I added to the doc string of 'edit-abbrevs-mode' a reference to
'edit-abbrevs', where this stuff is described.  This mode is
specifically designed for editing in such a buffer, so I see no need
to repeat the documentation there, as users are unlikely to turn that
mode by themselves.

> ("Current buffer" is wrong here, BTW, as what is meant
> by it is not the buffer of buffer *Abbrevs* but the
> buffer that you came from to create buffer *Abbrevs*.)

No, "current buffer" is not wrong, since the editing buffer is
prepared for editing abbrevs of the buffer that is current when the
function is invoked.

> Similarly, the doc in the Emacs manual (node `Abbrev Concepts' is not
> very helpful.  It tells you how you can use (expand) an existing abbrev,
> but it says nothing about how to create an abbrev, for instance.

"Abbrev Concepts" is not where this is described.  Please read the
following sections.

Thanks.





      reply	other threads:[~2018-11-23 10:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 16:54 bug#33443: 26; Doc of Edit Abbrevs mode Drew Adams
2018-11-23 10:20 ` Eli Zaretskii [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83y39kf62c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33443-done@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.