From: Matt Armstrong <matt@rfc20.org>
To: uzibalqa <uzibalqa@proton.me>
Cc: 56870@debbugs.gnu.org
Subject: bug#56870: company-dabbrev variable documentation
Date: Mon, 01 Aug 2022 14:24:14 -0700 [thread overview]
Message-ID: <878ro74pz5.fsf@rfc20.org> (raw)
In-Reply-To: <Rq85DC335cV_zFPETrg2PvpWlTKMYrEKbJXC2Br0KjJQh9vXvvYb-MecQi_aBPpnUkYWIXIBdj24zyoriRAdZzdr36aFtKQ6a12fSDsbjqM=@proton.me> (uzibalqa@proton.me's message of "Mon, 01 Aug 2022 03:54:04 +0000")
uzibalqa <uzibalqa@proton.me> writes:
> I am setting company-dabbrev variables
>
> (setq company-dabbrev-other-buffers 'all)
> (setq company-dabbrev-ignore-case 'keep-prefix)
>
> The documentation for the variables, says
>
> If ‘all’, search all other buffers, except the ignored ones.
>
> I find the documentation confusing because nowhere does it say that on
> should use 'all rather than all or "all".
I can understand your confusion.
When working at the level of Emacs Lisp, keep a few things in mind:
a) Generally, in Emacs Lisp help, if you see something like ‘all’ it
means a lisp level symbol. This could be a function name, variable, or
some other symbol. This is part of the project's conventions, described
here:
https://www.gnu.org/software/emacs/manual/html_node/elisp/Documentation-Tips.html
b) When lisp level interfaces expect strings they generally say so, and
the examples use quotes like "this".
c) A bare all (without any quotes at all), is just a word, and not
a Lisp level function or variable.
Hope that helps!
next prev parent reply other threads:[~2022-08-01 21:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 3:54 bug#56870: company-dabbrev variable documentation uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-01 21:24 ` Matt Armstrong [this message]
2022-08-01 21:32 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-01 21:49 ` Matt Armstrong
2022-08-01 21:55 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-01 21:49 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-02 10:20 ` Lars Ingebrigtsen
2022-08-02 10:34 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-03 10:07 ` YE via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-03 18:41 ` Matt Armstrong
2022-08-03 18:50 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 17:09 ` Matt Armstrong
[not found] ` <878ro4rl4l.fsf@rfc20.org-N8dpYwc----2>
2022-08-04 21:59 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 16:06 ` bug#56870: [PATCH] " YE via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 16:41 ` Eli Zaretskii
2022-08-04 17:48 ` Matt Armstrong
2022-08-04 18:25 ` Eli Zaretskii
2022-08-05 9:10 ` YE via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 11:09 ` Eli Zaretskii
2022-08-05 11:36 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-06 12:42 ` YE via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-06 13:19 ` Eli Zaretskii
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=878ro74pz5.fsf@rfc20.org \
--to=matt@rfc20.org \
--cc=56870@debbugs.gnu.org \
--cc=uzibalqa@proton.me \
/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).