From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Tab completion doesn't work.
Date: Tue, 16 May 2023 14:18:13 +0800 [thread overview]
Message-ID: <CAGP6PO+0FFoQSdO8fvjrS2XMf3wHEUB=tQK-VYmwijfvVU0=Gg@mail.gmail.com> (raw)
In-Reply-To: <87sfbwc39g.fsf@web.de>
On Tue, May 16, 2023 at 12:25 PM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > > See the attached screenshot for the completion results, which include
> > > `bibtex-completion-cite-commands`.
> >
> > And this also fixed the Tab completion problem discussed in this
> > thread, aka, `bib <Tab>` will give the desired completion, as shown in
> > the screenshot.
>
> Ok - good!
>
> I think you would benefit from enabling `debug-on-error' temporarily
> when your init file is loaded, and/or, even better, start to compile
> your init file regularly, since it will catch a lot of errors and
> problems like this.
>
> This will require some small changes (loading some stuff when compiling
> etc.), but if you try to get rid of any warnings you will avoid most of
> such surprises.
But I also noticed the following description here [1]:
Byte-compiling your init file is not recommended (see Byte Compilation
in the Emacs Lisp Reference Manual). It generally does not speed up
startup very much, and often leads to problems when you forget to
recompile the file. A better solution is to use the Emacs server to
reduce the number of times you have to start Emacs (see Using Emacs as
a Server). If your init file defines many functions, consider moving
them to a separate (byte-compiled) file that you load in your init
file.
[1] https://www.gnu.org/software/emacs/manual/html_node/emacs/Init-File.html
> Michael.
Regards,
Zhao
next prev parent reply other threads:[~2023-05-16 6:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 14:28 Tab completion doesn't work Hongyi Zhao
2023-05-15 0:04 ` Michael Heerdegen
2023-05-15 0:27 ` Hongyi Zhao
2023-05-15 0:35 ` Michael Heerdegen
2023-05-15 0:46 ` Hongyi Zhao
2023-05-15 1:22 ` Michael Heerdegen
2023-05-15 1:29 ` Hongyi Zhao
2023-05-15 1:58 ` Michael Heerdegen
2023-05-15 3:24 ` Hongyi Zhao
2023-05-15 3:36 ` Michael Heerdegen
2023-05-15 3:58 ` Hongyi Zhao
2023-05-15 4:20 ` Michael Heerdegen
2023-05-15 4:48 ` Hongyi Zhao
2023-05-15 5:35 ` Michael Heerdegen
2023-05-15 6:21 ` Hongyi Zhao
2023-05-15 22:56 ` Michael Heerdegen
2023-05-16 0:14 ` Hongyi Zhao
2023-05-16 1:31 ` Michael Heerdegen
2023-05-16 1:50 ` Hongyi Zhao
2023-05-16 2:11 ` Michael Heerdegen
2023-05-16 2:55 ` Hongyi Zhao
2023-05-16 3:21 ` Michael Heerdegen
2023-05-16 3:44 ` Hongyi Zhao
2023-05-16 3:53 ` Hongyi Zhao
2023-05-16 4:24 ` Michael Heerdegen
2023-05-16 6:18 ` Hongyi Zhao [this message]
2023-05-16 20:01 ` Michael Heerdegen
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='CAGP6PO+0FFoQSdO8fvjrS2XMf3wHEUB=tQK-VYmwijfvVU0=Gg@mail.gmail.com' \
--to=hongyi.zhao@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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).