unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Yuriy Pitometsu <pitometsu@gmail.com>
Cc: 18263@debbugs.gnu.org
Subject: bug#18263: occur-edit-mode can lose its text properties
Date: Thu, 19 Aug 2021 17:41:31 +0200	[thread overview]
Message-ID: <87o89t4f2s.fsf@gnus.org> (raw)
In-Reply-To: <CAHL3MAW-x4T9TWwRKMJs+Br_7HusO1-Dv5O2+8m1KYULT-5rqQ@mail.gmail.com> (Yuriy Pitometsu's message of "Thu, 14 Aug 2014 00:28:57 +0300")

Yuriy Pitometsu <pitometsu@gmail.com> writes:

> On pure Emacs:
> open some buffer M-s-o for occur
> then e for occur-edit-mode, then M-x replace-regexp [ ^I]+ RET SPC RET
> ;; try to replace excess spaces or tabs by just one space symbol in matched
> strings
>
> Error in minibuffer => Wrong type argument: markerp, nil

Glenn Morris <rgm@gnu.org> writes:

> I guess no-one expected you to edit the start of the line (the line
> number prefix that is not part of the actual source buffer).
> Maybe it should be read-only like the header line is
> (though then you would still get an error trying to replace-regexp).
> Or displayed using an overlay?

In Emacs 28, the stuff at the start of the line (that shouldn't be
removed) has been made read-only, so it looks like somebody fixed this
in the years since it was reported, so I'm closing this bug report.  If
there's still issues in this area, please respond to the debbugs address
and we'll reopen.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2021-08-19 15:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13 21:28 bug#18263: Wrong type argument: markerp, nil Yuriy Pitometsu
2014-08-14  1:22 ` Glenn Morris
2014-08-14  1:29   ` Glenn Morris
2021-08-19 15:41 ` Lars Ingebrigtsen [this message]

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=87o89t4f2s.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=18263@debbugs.gnu.org \
    --cc=pitometsu@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 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).