unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Mendler via "Emacs development discussions." <emacs-devel@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Arash Esbati <arash@gnu.org>,  Eli Zaretskii <eliz@gnu.org>,
	 Stefan Kangas <stefankangas@gmail.com>,
	 jb@jeremybryant.net, emacs-devel@gnu.org,
	 monnier@iro.umontreal.ca
Subject: Re: Why not include all ELPA packages in an Emacs release?
Date: Thu, 30 May 2024 08:33:30 +0200	[thread overview]
Message-ID: <87r0djlsg5.fsf@daniel-mendler.de> (raw)
In-Reply-To: <878qzrx1cd.fsf@posteo.net> (Philip Kaludercic's message of "Thu,  30 May 2024 06:25:54 +0000")

Philip Kaludercic <philipk@posteo.net> writes:

> Arash Esbati <arash@gnu.org> writes:
>
>> Philip Kaludercic <philipk@posteo.net> writes:
>>
>>> I am not familiar with cape,
>>
>> Cape offers CAPFs, but I think one great featuzre is that you can switch
>> the CAPF function during completion with something like this in your
>> init file:
>>
>> (use-package cape
>>   :bind (:map corfu-map
>>               ("C-c p d" . cape-dabbrev)
>>               ("C-c p f" . cape-file)
>>               ("C-c p s" . cape-elisp-symbol)
>>               ("C-c p w" . ispell-completion-at-point)
>>               ("C-c p :" . cape-emoji)))
>
> I tried it out, and it doesn't seem to work that well without something
> like corfu or vertico.  Generally it seems like an example where
> "completion" is misinterpreted to mean "selection".

This is not correct. Please stop spreading misinformation like this.
Capfs like the ones from Cape can be used to complete in a stepwise
manner. Simple examples are cape-dict, cape-dabbrev or cape-file.
cape-dabbrev for example predates the builtin dabbrev-capf and works in
the same way.

Daniel



  reply	other threads:[~2024-05-30  6:33 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28  8:48 Why not include all ELPA packages in an Emacs release? Jeremy Bryant
2024-05-28 23:15 ` Stefan Kangas
2024-05-28 23:56   ` Stefan Monnier
2024-05-29  5:59   ` Philip Kaludercic
2024-05-29 11:44   ` Eli Zaretskii
2024-05-29 15:27     ` Arash Esbati
2024-05-29 15:40       ` Eli Zaretskii
2024-05-29 16:06       ` Philip Kaludercic
2024-05-29 19:33         ` Andrea Corallo
2024-05-30 19:25           ` Adding AUCTeX to core " Jeremy Bryant
2024-05-30 19:33             ` Philip Kaludercic
2024-05-31 18:58               ` Jeremy Bryant
2024-06-07 22:00                 ` Jeremy Bryant
2024-06-08  6:56                   ` Philip Kaludercic
2024-06-08  9:40                   ` Arash Esbati
2024-06-08 15:25                   ` Stefan Monnier
2024-06-08 15:49                     ` Po Lu
2024-06-09  3:54                       ` Stefan Monnier
2024-06-09 19:39                         ` Stefan Kangas
2024-05-29 22:16         ` Arash Esbati
2024-05-29 22:19           ` Dmitry Gutov
2024-05-30  6:25           ` Philip Kaludercic
2024-05-30  6:33             ` Daniel Mendler via Emacs development discussions. [this message]
2024-05-30  7:28               ` Philip Kaludercic
2024-05-30  8:15                 ` Daniel Mendler via Emacs development discussions.
2024-05-30 15:20                   ` Philip Kaludercic
2024-05-29 20:35       ` Tassilo Horn
2024-05-29 22:04         ` Arash Esbati
2024-05-30  5:51           ` Eli Zaretskii
2024-05-30 10:52             ` Arash Esbati
2024-05-30  5:49         ` Eli Zaretskii
2024-05-30  7:55         ` Po Lu
2024-05-30 11:20           ` Eli Zaretskii
2024-05-30 11:53             ` Po Lu
2024-05-30 12:19               ` Eli Zaretskii
2024-05-30 12:58                 ` Po Lu
2024-05-30 14:11                   ` Stefan Monnier
2024-05-30 14:26                     ` Po Lu
2024-05-30 13:53           ` Stefan Monnier
2024-05-30 14:05             ` Po Lu
2024-05-30 15:02               ` Stefan Monnier
2024-05-30  8:00         ` Philip Kaludercic
2024-05-29 20:44     ` Stefan Kangas
2024-05-30  5:09       ` Eli Zaretskii
2024-06-07 21:48         ` Moving core packages to ELPA [Was: Re: Why not include all ELPA packages in an Emacs release?] Jeremy Bryant
2024-06-08  6:14           ` Eli Zaretskii
2024-06-08  8:10             ` Michael Albinus
2024-06-08  8:38               ` Eli Zaretskii
2024-06-08 15:55                 ` Michael Albinus
2024-06-08 16:47                   ` Eli Zaretskii
2024-06-08 16:59                     ` Michael Albinus
2024-06-07 21:55       ` Candidate packages for ELPA bundling " Jeremy Bryant
2024-06-08  1:44         ` Po Lu
2024-06-08  2:11           ` Dmitry Gutov
2024-06-08  2:46             ` Po Lu
2024-06-08  6:41               ` Philip Kaludercic
2024-06-08  6:54                 ` Po Lu
2024-06-08  7:47                   ` Philip Kaludercic
2024-06-08 15:06                     ` Stefan Monnier
2024-06-08 16:24                       ` Philip Kaludercic
2024-06-08 15:09             ` Stefan Monnier
2024-06-08  6:25           ` Eli Zaretskii
2024-06-08  6:48             ` Po Lu
2024-06-08 15:18           ` Stefan Monnier
2024-06-08 15:37             ` Po Lu
2024-06-08 15:53               ` Stefan Monnier
2024-06-09  0:06                 ` Po Lu
2024-06-09  3:55                   ` Stefan Monnier
2024-06-08  6:55         ` Philip Kaludercic

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=87r0djlsg5.fsf@daniel-mendler.de \
    --to=emacs-devel@gnu.org \
    --cc=arash@gnu.org \
    --cc=eliz@gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=mail@daniel-mendler.de \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    --cc=stefankangas@gmail.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 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).