From: martin-kemp@brusseler.com
To: martin-kemp@brusseler.com, "Dmitry Gutov" <dgutov@yandex.ru>,
help-gnu-emacs@gnu.org
Subject: complete from words in all opened buffers, not just code parts.
Date: Thu, 10 Jun 2021 01:13:29 +0200 (CEST) [thread overview]
Message-ID: <ea-mime-60c14b19-52c2-625a6e67@www-7.mailo.com> (raw)
In-Reply-To: <ea-mime-60c1088c-1e3c-3c783bd9@www-7.mailo.com>
Currently I have set the following
(setq company-backends '(company-dabbrev-code company-dabbrev))
(setq company-dabbrev-code-everywhere t)
(setq company-dabbrev-code-ignore-case t)
(setq company-dabbrev-code-other-buffers t)
(setq company-dabbrev-code-everywhere t)
(setq company-dabbrev-ignore-case t)
(setq company-dabbrev-other-buffers t)
Does the company-backends sequence matter. Would like to complete for both text files
and code (including from comments). I could also make a keybind to complete from code only
or from everything. What can one do for such keybind case?
From: martin-kemp@brusseler.com
To: Dmitry Gutov <dgutov@yandex.ru>;
help-gnu-emacs@gnu.org
Subject: complete from words in all opened buffers, not just code parts.
Date: 09/06/2021 20:29:32 Europe/Paris
Have set up things as follows ta allow completion from code buffers, everywhere, ignoring letter case,
and using all opened buffers.
(setq company-dabbrev-code-everywhere t)
(setq company-dabbrev-code-ignore-case)
(setq company-dabbrev-code-other-buffers t)
I also want to complete from texinfo (.texi) files. Last time you had mentioned
(setq company-backends '(company-dabbrev-code company-dabbrev))
There are a loads of options and getting hesitant to what to keep and which ones to discard.
From: Dmitry Gutov <dgutov@yandex.ru>
To: martin-kemp@brusseler.com;
help-gnu-emacs@gnu.org
Subject: Re: complete from words in all opened buffers, not just code parts.
Date: 09/06/2021 18:51:46 Europe/Paris
On 09.06.2021 19:47, martin-kemp@brusseler.com wrote:
> But, in programming languages I cannot complete from all buffers including from comments in
>
> opened code files.
Try
(setq company-dabbrev-code-everywhere t)
In general, you can view the available options across the package using
'M-x customize-group company'.
prev parent reply other threads:[~2021-06-09 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 16:47 complete from words in all opened buffers, not just code parts martin-kemp
2021-06-09 16:51 ` Dmitry Gutov
2021-06-09 18:29 ` martin-kemp
2021-06-09 23:13 ` martin-kemp [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
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=ea-mime-60c14b19-52c2-625a6e67@www-7.mailo.com \
--to=martin-kemp@brusseler.com \
--cc=dgutov@yandex.ru \
--cc=help-gnu-emacs@gnu.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.
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).