all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Bob Floyd" <bobfloyd@comcast.net>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: gregory@heytings.org, 48107@debbugs.gnu.org
Subject: bug#48107: 27.2; tags-quiery-replace fails to find occurences
Date: Fri, 30 Apr 2021 10:59:41 -0700	[thread overview]
Message-ID: <000001d73dea$9954c4b0$cbfe4e10$@net> (raw)
In-Reply-To: <83eeerbwl0.fsf@gnu.org>

That's a long time to wait using an editor that fails to find strings - both
`tags-query-replace` and `tags-search` exhibit the brokenness. How about
considering a 27.3 released soon?

-----Original Message-----
From: Eli Zaretskii [mailto:eliz@gnu.org] 
Sent: Friday, April 30, 2021 8:51 AM
To: Bob Floyd
Cc: gregory@heytings.org; 48107@debbugs.gnu.org
Subject: Re: bug#48107: 27.2; tags-quiery-replace fails to find occurences

> From: "Bob Floyd" <bobfloyd@comcast.net>
> Cc: <48107@debbugs.gnu.org>
> Date: Fri, 30 Apr 2021 08:34:29 -0700
> 
> How stable is the development version? Or, will I be disappointed if I use
> it for work?

I suggest to try.  there's no simple answer, because no one knows your
use patterns and workflows, nor your sensitivity to "stability"
problems.

> Or, how soon will the development version become 27.3?

It will become Emacs 28.1, and that is still far away.






  reply	other threads:[~2021-04-30 17:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 20:14 bug#48107: 27.2; tags-quiery-replace fails to find occurences Bob Floyd
2021-04-29 22:27 ` Gregory Heytings
2021-04-30  7:46   ` Eli Zaretskii
2021-04-30  8:59     ` Gregory Heytings
2021-04-30 15:34       ` Bob Floyd
2021-04-30 15:50         ` Eli Zaretskii
2021-04-30 17:59           ` Bob Floyd [this message]
2021-04-30 18:07             ` Eli Zaretskii
2021-04-30 20:16             ` Gregory Heytings
2021-05-01  0:08               ` Bob Floyd
2021-04-30 15:54         ` Gregory Heytings
2021-04-30 17:39     ` Stefan Kangas
2021-04-30 18:00       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000001d73dea$9954c4b0$cbfe4e10$@net' \
    --to=bobfloyd@comcast.net \
    --cc=48107@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gregory@heytings.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.
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.