unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>,
	Gabriele Nicolardi <gabriele@medialab.sissa.it>
Cc: 67124@debbugs.gnu.org
Subject: bug#67124: 26.3; query-replace Arg out of range with comma option (at end-buffer)
Date: Mon, 13 Nov 2023 16:21:43 +0200	[thread overview]
Message-ID: <03fc7766-3d3a-394b-e08c-53eb136d40a6@gutov.dev> (raw)
In-Reply-To: <83r0ktu4s7.fsf@gnu.org>

On 13/11/2023 16:06, Eli Zaretskii wrote:
> [Please use Reply All to reply, so that the bug tracker is CC'ed.]
>> Date: Sun, 12 Nov 2023 23:44:43 +0100
>> From: Gabriele Nicolardi<gabriele@medialab.sissa.it>
>>
>> I tested the patch on the MWE I sent to you. Thanks!
>>
>> Now I'm not sure what I should do. I write elisp code used by a production team. We use Emacs to
>> format LaTeX documents of scientific papers. I don't control which version of Emacs my
>> collaborators use. Do you have any suggestions?
> I guess either wait for the next Emacs release or build your own
> Emacs?

I haven't examined the exact problem, but in such cases some people also 
either have workarounds in their own code, or supply "advices" for the 
core functions that work around the problem there.

This kind of solution requires a certain level of understanding of the 
code in question, and might be quite brittle otherwise (breaking other 
features for the same users). Not for the faint of heart, I'd say.





  reply	other threads:[~2023-11-13 14:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-11 19:40 bug#67124: 26.3; query-replace Arg out of range with comma option (at end-buffer) Gabriele Nicolardi
2023-11-12  9:48 ` Eli Zaretskii
2023-11-13  3:56   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-13 14:17     ` Eli Zaretskii
2023-11-16 14:29       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-16 14:55         ` Eli Zaretskii
2023-11-16 16:15           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-16 16:56             ` Eli Zaretskii
2023-11-16 18:01               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-16 18:34                 ` Eli Zaretskii
2023-11-16 15:35     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-16 16:51       ` Eli Zaretskii
2023-11-16 18:23         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-18 10:18           ` Eli Zaretskii
2023-11-18 16:44             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-18 21:35               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <ed11baa2-cf89-4a72-91d0-8f26c0af4126@medialab.sissa.it>
2023-11-13 14:06     ` Eli Zaretskii
2023-11-13 14:21       ` Dmitry Gutov [this message]
2023-11-13 14:38         ` Eli Zaretskii
2023-11-13 14:45           ` Dmitry Gutov
2023-11-13 15:39             ` Gabriele Nicolardi
2023-11-16 14:45               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-16 16:27                 ` Gabriele Nicolardi
2023-11-15 13:18   ` 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=03fc7766-3d3a-394b-e08c-53eb136d40a6@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=67124@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gabriele@medialab.sissa.it \
    /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).