From: "João Távora" <joaotavora@gmail.com>
To: Alexander Adolf <alexander.adolf@condition-alpha.com>
Cc: Eshel Yaron <me@eshelyaron.com>, Juri Linkov <juri@linkov.net>,
Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Inline completion preview
Date: Mon, 30 Oct 2023 13:01:12 +0000 [thread overview]
Message-ID: <CALDnm51Vb6fRYq1Hr5Wc=pXX3P_o1om2GHgKaXyW_fEer9GhoQ@mail.gmail.com> (raw)
In-Reply-To: <b944e43d3beee25a28cdda7878c0e386@condition-alpha.com>
On Mon, Oct 30, 2023 at 12:42 PM Alexander Adolf
<alexander.adolf@condition-alpha.com> wrote:
>
> João Távora <joaotavora@gmail.com> writes:
>
> > On Sun, Oct 29, 2023 at 4:25 PM Alexander Adolf
> > <alexander.adolf@condition-alpha.com> wrote:
> >>
> >> Company provides an ecosystem of its own, and that can make one’s setup more complicated.
> >
> > I agree it provides more abstractions then are essential, but you don't
> > have to use them. Eglot-managed buffers prefer the company-capf backend
> > by default and it works fine just fine.
> >
> > So the "complicated setup" you're looking for might just be one line:
> >
> > (setq company-backends '(company-capf))
>
> Indeed. But the complexity I was intending to refer to came with
> integrating company with other 3rd party packages. Because of comapny's
> age (it predates some of Emacs's current completion infrastructure),
> many 3rd party packages have specific company adaptation code. As
> packages and Emacs evolve, an adaptation or two tend to break with each
> update. This kept my company config growing and growing.
But you don't _have_ to use that integrations and third party packages,
do you? You used it because you wanted to.
As far as I understand if you replaced all your complicated
setup with that one line I gave you, Company works with exactly
the same things Corfu does (CAPF completion backends, acronym for
completion-at-point-functions).
We should not compare apples to oranges and make decisions
based on that.
João
next prev parent reply other threads:[~2023-10-30 13:01 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 18:11 Inline completion preview Eshel Yaron
2023-10-26 18:38 ` Eli Zaretskii
2023-10-26 19:39 ` Eshel Yaron
2023-10-27 5:52 ` Eli Zaretskii
2023-10-27 15:43 ` Eshel Yaron
2023-10-27 17:12 ` Eli Zaretskii
2023-10-27 18:13 ` Eshel Yaron
2023-10-27 20:25 ` chad
2023-10-28 16:47 ` Juri Linkov
2023-10-28 19:01 ` Eshel Yaron
2023-10-29 16:24 ` Alexander Adolf
2023-10-29 23:29 ` João Távora
2023-10-30 9:25 ` Juergen Fenn
2023-10-30 9:36 ` João Távora
2023-10-30 11:04 ` Dmitry Gutov
2023-10-30 12:42 ` Alexander Adolf
2023-10-30 13:01 ` João Távora [this message]
2023-10-30 17:32 ` Alexander Adolf
2023-10-30 17:52 ` João Távora
2023-10-30 13:20 ` Dmitry Gutov
2023-10-30 17:43 ` Alexander Adolf
2023-10-30 22:49 ` Dmitry Gutov
2023-10-31 6:50 ` Eshel Yaron
2023-10-31 17:31 ` Alexander Adolf
2023-10-31 17:43 ` Eshel Yaron
2023-10-31 23:29 ` Dmitry Gutov
2023-11-01 8:30 ` Eshel Yaron
2023-11-01 10:11 ` João Távora
2023-11-01 10:44 ` Eshel Yaron
2023-11-01 11:07 ` João Távora
2023-11-01 12:17 ` Eshel Yaron
2023-11-01 12:23 ` Dmitry Gutov
2023-11-01 14:07 ` Juergen Fenn
2023-11-01 19:57 ` Dmitry Gutov
2023-11-01 12:08 ` Dmitry Gutov
2023-11-01 12:14 ` Dmitry Gutov
2023-11-01 12:24 ` Dmitry Gutov
2023-11-01 12:29 ` Eshel Yaron
2023-11-01 12:32 ` Dmitry Gutov
2023-11-01 12:34 ` Eli Zaretskii
2023-11-01 12:36 ` Dmitry Gutov
2023-11-01 13:28 ` Po Lu
2023-11-01 19:49 ` Dmitry Gutov
2023-10-27 8:58 ` Ihor Radchenko
2023-10-27 15:53 ` Eshel Yaron
2023-10-27 11:49 ` João Távora
2023-10-27 11:52 ` João Távora
2023-10-27 12:18 ` Eli Zaretskii
2023-10-27 12:55 ` João Távora
2023-10-27 12:58 ` Eli Zaretskii
2023-10-27 13:05 ` Dmitry Gutov
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='CALDnm51Vb6fRYq1Hr5Wc=pXX3P_o1om2GHgKaXyW_fEer9GhoQ@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=alexander.adolf@condition-alpha.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=me@eshelyaron.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.