From: Mathias Dahl <mathias.dahl@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Abbrev suggestions - feedback appreciated
Date: Thu, 4 Jun 2020 22:14:08 +0200 [thread overview]
Message-ID: <CABrcCQ6V-SXZe+wa1F5L3yCKVJfnSFLN=1jn7yPeZBK6fhqfkg@mail.gmail.com> (raw)
In-Reply-To: <CABrcCQ5gRg70xapwxazUK8OfG4Fvvd5Mbg1HtvWRLx7ZGQOTcQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
Since there were no more comments on my previous reply I will pick the
option I like best :) The performance is anyway very good regardless
which option I take.
Now for another matter: documentation. I've been thinking about where to
best describe this new feature. It does not need a very length
description I think, but we should mention it in the manual. Here is the
current "menu" for Abbrevs:
* Abbrev Concepts Fundamentals of defined abbrevs.
* Defining Abbrevs Defining an abbrev, so it will expand when typed.
* Expanding Abbrevs Controlling expansion: prefixes, canceling
expansion.
* Editing Abbrevs Viewing or editing the entire list of defined
abbrevs.
* Saving Abbrevs Saving the entire list of abbrevs for another
session.
* Dynamic Abbrevs Abbreviations for words already in the buffer.
* Dabbrev Customization What is a word, for dynamic abbrevs. Case
handling.
Any thoughts on this?
Also, once the documentation is done, what would be the steps, in git,
to get this into Emacs? Are we using feature branches? Do people commit
to master? Or can I send a patch by e-mail? (less risk of me messing
up...)
Thanks!
[-- Attachment #2: Type: text/html, Size: 1408 bytes --]
next prev parent reply other threads:[~2020-06-04 20:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 7:51 Abbrev suggestions - feedback appreciated Mathias Dahl
2017-09-16 8:46 ` Eli Zaretskii
2017-09-17 13:15 ` Mathias Dahl
2017-09-16 13:22 ` Stefan Monnier
2017-09-17 13:22 ` Mathias Dahl
2017-09-17 14:03 ` Mathias Dahl
2017-09-17 21:23 ` Stefan Monnier
2017-09-17 21:56 ` Mathias Dahl
2017-10-03 12:51 ` Kaushal Modi
2017-10-07 15:13 ` Mathias Dahl
2017-10-07 15:29 ` Stefan Monnier
2017-10-07 17:18 ` Mathias Dahl
2017-10-07 18:40 ` Mathias Dahl
2017-10-07 22:29 ` Ian Dunn
2017-10-07 22:44 ` Stefan Monnier
2017-10-08 16:38 ` Ian Dunn
2018-09-17 21:48 ` Mathias Dahl
2018-09-18 2:05 ` Stefan Monnier
2020-05-11 21:37 ` Mathias Dahl
2020-05-11 22:39 ` Mathias Dahl
2020-05-11 22:58 ` Stefan Monnier
2020-05-16 22:10 ` Mathias Dahl
2020-05-16 22:22 ` Mathias Dahl
2020-05-17 3:13 ` Stefan Monnier
2020-05-17 14:59 ` Mathias Dahl
2020-05-17 15:45 ` Eli Zaretskii
2020-05-17 18:43 ` Mathias Dahl
2020-05-17 21:20 ` Stefan Monnier
2020-05-18 22:00 ` Mathias Dahl
2020-06-04 20:14 ` Mathias Dahl [this message]
2017-10-07 22:40 ` Stefan Monnier
2017-10-08 15:28 ` Mathias Dahl
-- strict thread matches above, loose matches on Subject: below --
2017-10-08 8:15 Seweryn Kokot
2017-10-08 15:25 ` Mathias Dahl
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='CABrcCQ6V-SXZe+wa1F5L3yCKVJfnSFLN=1jn7yPeZBK6fhqfkg@mail.gmail.com' \
--to=mathias.dahl@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.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).