all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 67870@debbugs.gnu.org, 67870-done@debbugs.gnu.org
Subject: bug#67870: 29.1; Eglot missing or un-findable advertised feature
Date: Tue, 19 Dec 2023 00:15:19 -0800	[thread overview]
Message-ID: <72A920F6-B1E8-4F00-B72B-DD05F808BA19@boostpro.com> (raw)
In-Reply-To: <CALDnm52v9Mh2eGGopxEi=cyV23Nmc2Njrjns7AvGB9Bk-noXTQ@mail.gmail.com>

You’re missing my point. In that bulletin there was nothing that could have prompted me to search for “action”.

Sent from my iPad

> On Dec 18, 2023, at 12:00 PM, João Távora <joaotavora@gmail.com> wrote:
> 
> No need to justify yourself so much, but I find this odd.
> For example, a simple text search within the Eglot manual for
> "action" yields this as the second result in the end of the
> very section you were reading.





  reply	other threads:[~2023-12-19  8:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17 19:38 bug#67870: 29.1; Eglot missing or un-findable advertised feature Dave Abrahams
     [not found] ` <handler.67870.B.17028419482015.ack@debbugs.gnu.org>
2023-12-17 20:23   ` bug#67870: Acknowledgement (29.1; Eglot missing or un-findable advertised feature) Dave Abrahams
2023-12-18 17:07     ` João Távora
2023-12-18 17:00 ` bug#67870: 29.1; Eglot missing or un-findable advertised feature João Távora
2023-12-18 19:10   ` Dave Abrahams
2023-12-18 19:59     ` João Távora
2023-12-19  8:15       ` Dave Abrahams [this message]
2023-12-19  8:51         ` João Távora
2023-12-22  3:14           ` Richard Stallman
2023-12-22  9:29             ` João Távora
2023-12-22  9:41               ` João Távora
2023-12-22 17:47               ` Dave Abrahams
2023-12-24 20:27                 ` Stefan Kangas

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=72A920F6-B1E8-4F00-B72B-DD05F808BA19@boostpro.com \
    --to=dave@boostpro.com \
    --cc=67870-done@debbugs.gnu.org \
    --cc=67870@debbugs.gnu.org \
    --cc=joaotavora@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 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.